Anthony Liguori wrote:
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?
Anthony Liguori wrote:
Alexander Graf wrote:
Isn't one of the great things about virtualization the fact that you
can do things you can on real hardware in the virtual machine? While
I'm not exactly a fan of VirtualPC, I would still like it to work in
KVM, as that's what real hardware is
On 09.01.2009, at 18:50, Avi Kivity wrote:
Kevin Wolf wrote:
Hi,
let's start with the scenario I tried to use: I have two levels of
virtualization. On the physical hardware I run a Linux with KVM.
The KVM
guest is a Win2k3 VM which runs VirtualPC. In VirtualPC I try to
run a
Linux again
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
Avi Kivity wrote:
Kevin Wolf wrote:
Hi,
let's start with the scenario I tried to use: I have two levels of
virtualization. On the physical hardware I run a Linux with KVM. The KVM
guest is a Win2k3 VM which runs VirtualPC. In VirtualPC I try to run a
Linux again (openSUSE 11.1 to be specific,
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),
Alexander Graf wrote:
We're in a nice compatibility mess. We can't just switch paravirt
detection methods since that will break older guests _and_ older
hosts on non-nested virtualization (which is the common case).
Shouldn't it be ok to push patches to linux-stable to use the CPUID
and MSR
Alexander Graf wrote:
Isn't one of the great things about virtualization the fact that you
can do things you can on real hardware in the virtual machine? While
I'm not exactly a fan of VirtualPC, I would still like it to work in
KVM, as that's what real hardware is capable of.
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
