On 07/05/2011 02:07 PM, Sasha Levin wrote:
>
>  - was a BIOS update attempted?  at least VMware uses the same check as
>  kvm, and probably virtualbox as well, so this problem should have been
>  seen before.

We didn't update the BIOS.

virtualbox was installed previously and didn't work properly either -
thats why he tried kvm afaik.

That's a good data point.

>  - was this after a reset or cold boot?

This was a reset, we didn't try a cold boot.

Unlikely to help, since it was a preexisting problem.

>  - maybe a stealth rootkit is involved?
>

A rootkit that messed up the MSRs or runs a hidden guest sounds like a
possibility too.

Alexander Graf suggested it's a simple case of a BIOS vendor not
implementing specs properly as he has seen a similar case of BIOS only
allowing to start virtualization on the first CPU.

I agree.  But let's try a BIOS update first, if possible.

If that fails, please repost the patches, but for svm only, since we haven't seen these issues on Intel.

--
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to