Avi Kivity wrote:
Anthony Liguori wrote:
Alexander Graf wrote:
Shouldn't it be ok to push patches to linux-stable to use the CPUID
and MSR information and simply not expose the CPUID identification
in newer KVM versions? That way older guests on newer KVM don't use
KVM paravirt (which should still be ok), but everything else runs as
smoothly as possible.
I'd say that VirtualPC is broken and leave it at that.
All modern hypervisors use CPUID to expose themselves to the guests.
VirtualPC is totally capable of rewriting CPUID instructions.
Apparently it isn't. I know of one other fullvirt product that does
not jit kernel code. Or maybe they wanted to preserve consistency
between kernel cpuid and host cpuid.
How can you get away with not jitting kernel code?
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
