From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Linux in VirtualPC in KVM fails Date: Sun, 11 Jan 2009 09:17:26 +0200 Message-ID: <49699D06.4040304@redhat.com> References: <4967708E.2060907@suse.de> <49678E6E.4020306@redhat.com> <49679FEB.6040208@codemonkey.ws> <4967AEEC.9060107@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , Kevin Wolf , kvm@vger.kernel.org To: Anthony Liguori Return-path: Received: from mx2.redhat.com ([66.187.237.31]:34752 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750895AbZAKHRd (ORCPT ); Sun, 11 Jan 2009 02:17:33 -0500 In-Reply-To: <4967AEEC.9060107@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: 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