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 -- Kind regards / mit freundlichen Gruessen / Met vriendelijke groet Sander van Leeuwen innoTek GmbH http://www.innotek.de Germany ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
