On Sun, Feb 24, 2008 at 05:25:09PM -0600, Les Mikesell wrote: > The Xen concept of the virtualized guest needing to know it is virtualized > is flawed anyway. You'd have to expect problems from that. Handling it > correctly on the host side should make it equivalent to the vmware module > that doesn't need any specific management in terms of the rest of the > kernel. (Getting slight OT but ...) the Xen problem is not "the virtualized guest needing to know it is virtualized" (ie. paravirtualization). Paravirtualization is important for performance, and any virt technology worth its salt can benefit from at least PV drivers. VMWare ship enhancements which run inside the guest and provide faster I/O and other features, and have done since the very first releases of VMWare. The Xen problem is that they duplicate functionality of the Linux kernel in their hypervisor. See: http://udrepper.livejournal.com/17577.html Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
