On Wed, 2011-12-07 at 16:23 +0200, Avi Kivity wrote: > On 12/07/2011 04:18 PM, Sasha Levin wrote: > > On Wed, 2011-12-07 at 16:17 +0200, Avi Kivity wrote: > > > On 12/01/2011 08:30 PM, Sasha Levin wrote: > > > > Currently we silently fail if VMX is already in use by a different > > > > virtualization technology. > > > > > > > > This is bad since it's non-obvious for the user, and its not too uncommon > > > > for users to have several of these installed on same host. > > > > > > > > This patch adds a message to notify the user of the problem. > > > > > > > > > > Does this actually happen? With which hypervisor? > > > > vbox > > > > It turns VMX/SVM on when it loads, regardless of whether it's running a > > guest or not. > > That's odd. IIRC when we discussed this with them, they were executing > VMXON/VMXOFF dynamically. Looks like they changed this. > > Anyway, please adjust according to Joerg's comment (and add the word > "using"), and I'll apply. I've seen it the day before I've sent those patches. vbox driver loaded, kvm silently failed and rdmsr showed SVME turned on. Will resend. -- Sasha. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
