From: Avi K. <av...@qu...> - 2007-09-04 13:57:48
|
Sander van Leeuwen wrote: > Avi Kivity wrote: >>> I think it's a bit risky to use somebody else's vmxon pointer. >>> >>> You have a point with the msr updates though. >> I think the easiest way forward is for you to unload kvm-intel (or >> kvm-amd) when you load, and to reload it when you unload. >> > You may want to reconsider as KVM breaks VMWare server 1.3 on 64 bits > linux hosts as well. In exactly the same way > as it breaks VirtualBox. > > We have tried this ourselves and others have reported the same: > - http://www.vmware.com/community/message.jspa?messageID=718184 > - http://www.redhat.com/archives/rhl-list/2007-June/msg02501.html > This is unsurprising. But I believe the same solution (rmmod kvm-intel) will work for VMware as well as for VirtualBox, or anything else that wants to use VT. Can you explain what is wrong with it? It is simple, requires no kernel changes, and has no present and potential future performance impact. It will work on all kernel versions, unlike any change you may wish us to make. -- Any sufficiently difficult bug is indistinguishable from a feature. |