On Tuesday 29 June 2010, 0bo0 wrote:
Beyond that, I'm not at all sure what the value of it "is" or "is not" Linux ... is.
Because Xen is its own kernel that then loads an instance of Linux as its primary O/S it menas that a system that was working correctly with a non-Xen kernel may fail if proprietary graphics drivers are installed. Sure, you don't need that stuff on a production box, but on my dev box I like to do more than just play with virtualization. I found that XEN + nvidia | radeon didn't work. I also recall probs with vnc to a remote XEN box. OTOH, kvm fits snugly into the whole stack. Nothing needs to be changed. If the setup was working before the KVM module was loaded it will continue to work afterwards.
whatever technical advantage it may have had is gone.
Unfortunately, the facts simply don't bear that out ...
That depends - which facts? When I first looked at this seriously a year ago I found facts then that related to early implementations of KVM. Sure, XEN was better/faster/whatever. Since then, KVM has matured and virtio drivers have appeared. Performance wise I am yet to see any problems. It is good enough for me. Paul -- Paul Reeves -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org