<div dir="ltr">PV drivers were released by Oracle, who run their own virtualization platform based on XenCommunity.<div><br></div><div>KVM is wasteful and requires VT support even for Linux machines. Not only that, but its virtualized hardware is legacy old hardware supplied by QEMU.</div>
<div><br></div><div>The leading virtualization solutions currently in the market are Vmware ESXi, which, for a single server is free and very nice (although you better make sure your hardware is in their support matrix), Microsoft Hyper-V, which is not Linux-friendly, if you care about it, and Citrix XenServer.</div>
<div><br></div><div>You can compare these three on the internet.</div><div><br></div><div>Less common, but aggressively in use (with the same performance profile) are OracleVM, RHEL Xen platform (with Oracle PV drivers for Windows) - Xen Community based.</div>
<div><br></div><div>On the level of the "low performance" you would find Vmware Server, and Sun VirtualBox.</div><div><br></div><div>KVM was designed, and is focused on VDI - desktop virtualization, being the focus of Kumranet in the past. RedHat cannot maintain two virtualization platforms.</div>
<div><br></div><div>Assuming you aim at Windows virtualization, and assuming you want the assurance of enterprise-class solution, I would recommend any of the top three, with my favorite Citrix XenServer (check the pros and cons of each and make your own decisions in that matter). Other solutions are not complete, or will have near-zero support or knowledge base on the net.</div>
<div><br></div><div>To make things clear - I earn my keep by performing various system and IT architecture-related integration operations, amongst are virtualization design and implementations. </div><div>I have several customers with large XenServer farms, running mission-critical, 24/7/365. The longer one has his farm running since about March, containing about 40-50 VMs, including the company's Exchange server (~400 users), several Oracle DB environments, MSSQL, ADS, TS and more. These are memory-hungry applications, and the total memory allocated there (usually memory is the immediate bottleneck, followed by disk IO performance) is about 150GB ram, in total, with shared storage and the entire shabang.</div>
<div><br></div><div>Other customers of mine use smaller environments, running one or two servers, with several tenths of vms on them. They were unable to reach anywhere near this capacity (amount of VMs, performance of every single VM) using VMware Server, of course. </div>
<div><br></div><div>Make your own pick. I can only recommend to use the enterprise class tools, especially if they can come for free, and/or you could buy support.</div><div><br></div><div>Ez<br><br><div class="gmail_quote">
On Tue, Jan 19, 2010 at 10:11 PM, Oleg Goldshmidt <span dir="ltr"><<a href="mailto:pub@goldshmidt.org">pub@goldshmidt.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Jonathan Ben Avraham <<a href="mailto:yba@tkos.co.il">yba@tkos.co.il</a>> writes:<br>
<br>
> Hi Gilad,<br>
> Why do you recommend KVM over XEN? Have you fiddled with both? Are<br>
> there particular problems with XEN?<br>
<br>
</div>Apart from the fact that XEN is paravirtualization technology and<br>
running a mission-critical Windows DomU is possible mostly in theory?<br>
<br>
Disclaimer: I have not touched Xen over a couple of years (when<br>
Windows guests were possible on KVM, at least in principle, and not<br>
possible on Xen). I checked the current docs out of curiousity and<br>
phrases like "PV drivers are being developed" and "you need to disable<br>
driver signature checking on (every!) reboot" [original emphasis]<br>
don't inspire much confidence.<br>
<br>
Other points Gilad made (KVM being much less intrusive and already in<br>
the vanilla kernel and provided by RedHat) are very much valid.<br>
<br>
To the OP: Xen is not for you. I have no first-hand experience (beyond<br>
a tiny bit of tinkering) with KVM. I have quite a bit of production<br>
experience with VMware. I am surprised that most of the postings focus<br>
on the VMware Server (previously known as GSX). IIRC the OP mentioned<br>
"crucial" servers but did *not* say $0 was a requirement. I'd go with<br>
ESX for mission-crtical stuff.<br>
<br>
For a serious installation I would not keep data (or system images,<br>
for that matter, but YMMV) on directly attached disks.<br>
<font color="#888888"><br>
--<br>
Oleg Goldshmidt | <a href="mailto:pub@goldshmidt.org">pub@goldshmidt.org</a><br>
<br>
_______________________________________________<br>
Linux-il mailing list<br>
</font><div class="im"><a href="mailto:Linux-il@cs.huji.ac.il">Linux-il@cs.huji.ac.il</a><br>
</div><div><div></div><div class="h5"><a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
</div></div></blockquote></div><br></div></div>