public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alexander Graf <agraf@suse.de>, Kevin Wolf <kwolf@suse.de>,
	kvm@vger.kernel.org
Subject: Re: Linux in VirtualPC in KVM fails
Date: Sun, 11 Jan 2009 09:17:26 +0200	[thread overview]
Message-ID: <49699D06.4040304@redhat.com> (raw)
In-Reply-To: <4967AEEC.9060107@codemonkey.ws>

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 capable of.
>
> Paravirtualization support is advertised in userspace, just add a flag 
> to QEMU to disable KVM paravirt support.

That's helpful.  But I would like (in addition) a fix that does not 
require administrative involvement.

The host admin should not need to know anything about what the guest 
runs.  That's not achievable in practice, but where it is, we want it.

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


      reply	other threads:[~2009-01-11  7:17 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
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 [this message]

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=49699D06.4040304@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox