@scottalanmiller said in AVImark support has stated that running virtual servers can result in a 40-50% data loss or complete destruction of your server.:

and we just left that as it was (having learned about it), that's establishing that that is official.

Bolded bit is the thing you are glossing over.

This entire thing is a rant by @CCWTech

No where in here is there proof that anyone, above the support tech at the vendor, has been made aware of anything.

At this point there is nothing but an unsubstantiated claim by @CCWTech the vendor knows what the support tech said. Yes, absolutely, if it is known and not corrected, this would be shit, but no one, in this thread, knows this.

Is this a shit ass vendor with a bad product? Maybe, hell probably even. But I won't take the word of anyone the just comes on here and rants without any proof.

@FATeknollogee said in Hypervisors: revisit your choices!:

One downside to KVM (in virt-manager) is lack of snapshots for UEFI VMs.

yes it is.

/proc doesn't differ too much with LXC.

[root@acl-jira ~]# ls /proc 1 24924 24951 25368 275 322 bus diskstats interrupts key-users locks net slabinfo thread-self zoneinfo 12471 24925 24952 25369 295 323 cgroups dma iomem kmsg mdstat pagetypeinfo softirqs timer_list 12581 24926 24953 25370 316 54 cmdline driver ioports kpagecgroup meminfo partitions stat tty 24897 24937 24955 25381 318 56 consoles execdomains irq kpagecount misc sched_debug swaps uptime 24908 24938 25157 25382 319 69 cpuinfo fb kallsyms kpageflags modules schedstat sys version 24909 24939 25258 25383 32 acpi crypto filesystems kcore latency_stats mounts scsi sysrq-trigger vmallocinfo 24910 24950 25286 25386 320 buddyinfo devices fs keys loadavg mtrr self sysvipc vmstat [scott@lax-lnx-jump proc]$ ls /proc 1 112 2 24453 24612 31 38 427 532 644 674 759 acpi diskstats ioports kpageflags mtrr softirqs uptime 10 12 20 24455 24613 32 39 428 557 645 676 8 buddyinfo dma irq latency_stats net stat version 100 13 21 24460 24621 326 393 429 598 646 677 9 bus driver kallsyms loadavg pagetypeinfo swaps vmallocinfo 101 13532 21810 24461 2599 33 4 43 599 647 681 9133 cgroups execdomains kcore locks partitions sys vmstat 102 14 22 24510 27 332 403 430 6 648 682 9214 cmdline fb keys mdstat sched_debug sysrq-trigger zoneinfo 103 15 23 24512 28 34 421 431 612 654 683 968 consoles filesystems key-users meminfo schedstat sysvipc 105 16 23974 24520 29 35 424 432 613 659 684 969 cpuinfo fs kmsg misc scsi thread-self 106 17 24 24562 3 36 425 44 615 662 694 98 crypto interrupts kpagecgroup modules self timer_list 11 18 24449 24568 30 37 426 517 643 664 752 99 devices iomem kpagecount mounts slabinfo tty

Container on top. KVM on bottom.

Registered.

Quite a while means several months, not years.

http://www.xenserver.org/