Alexander Graf wrote:
When using nested SVM we usually want the guest to see the exact
CPUID values
we gave it and not some mangled ones.
That would triggered by -cpu host, not nesting.
Oh we have -cpu host already?
No, we don't :)
hm - treating the hypervisor bit like any other cpuid bit sounds like
a good idea. I'm wondering though which way should be preferred. I
usually don't want to have the hypervisor bit set - but maybe I'm the
minority.
Windows requires the hypervisor bit to set in order to pass some testing
program.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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
