Adrian Chadd <adr...@freebsd.org> writes: > I'd suggest "use whatever works". I use Centos 5.x since they use the > latest "stable" xen patched kernel but its quite out of date.
If you want to make FreeBSD also run under the 3.0.3/3.1 hypervisor that CentOS/RHEL use, that's great (I think ec2 uses the RHEL/CentOS foo, but that is hersay.) the newer Xen hypervisors all seem to support DomUs that expect 3.0.3 hypervisors, so we should be good. The RHEL5 installations will be out there for a while, and 'yum install xen' is by far the easiest way to get a working Dom0. Prgmr.com uses a xen.org 220.127.116.11-xen (the one that comes with Xen 3.4) kernel and toolset on top of a CentOS 5 userland right now. I moved off of the CentOS kernel because until recently it did not support paravirt_ops DomUs, and the RHEL Xen kernels are slightly less stable than the xen.org kernels. RedHat has made it quite clear that they intend to replace all instances of xen with KVM. So yeah, for me personally, I see NetBSD 5 as the 'way forward' in terms of Dom0 operating systems, now that RedHat has publically stated that KVM should replace Xen in RedHat products (which is weird, because as far as I can see, while both are fine products, they are not even remotely substitutable. KVM would be a silly idea for prgmr.com to use for hosting, and Xen doesn't make sense if you just need to spin up a dev box every now and then.) Currently NetBSD uses the Xen 3.3 hypervisor, and it supports modern hardware. (really, the 18.104.22.168-xen kernel from xen.org, which I currently use in production is mostly okay, especially as the socket F boards havent changed in some time.) I started with FreeBSD Jails, and moved to NetBSD/xen2, and only left because of the ram limit. Now that NetBSD 5 is out, I think it's time for me to switch back. _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"