From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, Kevin Wolf <kwolf@suse.de>,
kvm@vger.kernel.org
Subject: Re: Linux in VirtualPC in KVM fails
Date: Fri, 09 Jan 2009 14:10:57 -0600 [thread overview]
Message-ID: <4967AF51.6060400@codemonkey.ws> (raw)
In-Reply-To: <4967A64C.7070702@redhat.com>
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
next prev parent reply other threads:[~2009-01-09 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 15:43 Linux in VirtualPC in KVM fails Kevin Wolf
2009-01-09 17:50 ` Avi Kivity
2009-01-09 19:00 ` Alexander Graf
2009-01-09 19:04 ` Anthony Liguori
2009-01-09 19:32 ` Avi Kivity
2009-01-09 20:10 ` Anthony Liguori [this message]
2009-01-11 7:16 ` Avi Kivity
2009-01-09 19:34 ` Avi Kivity
2009-01-09 19:05 ` Anthony Liguori
2009-01-09 19:24 ` Alexander Graf
2009-01-09 20:09 ` Anthony Liguori
2009-01-11 7:17 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4967AF51.6060400@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.