From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KNjmj-0003ZI-2W
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 03:38:17 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KNjmi-0003Z4-Ow
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 03:38:16 -0400
Received: from [199.232.76.173] (port=45505 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KNjmi-0003Z1-E3
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 03:38:16 -0400
Received: from mx1.redhat.com ([66.187.233.31]:60138)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1KNjmi-00013P-7Z
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 03:38:16 -0400
Message-ID: <488EC8D9.9060705@redhat.com>
Date: Tue, 29 Jul 2008 09:38:01 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 1/7] xen: groundwork for
	xen support
References: <1217251078-6591-1-git-send-email-kraxel@redhat.com>
	<1217251078-6591-2-git-send-email-kraxel@redhat.com>
	<488DD206.8040404@codemonkey.ws>
	<20080728231439.GC11519@implementation>
In-Reply-To: <20080728231439.GC11519@implementation>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Samuel Thibault <samuel.thibault@eu.citrix.com>, qemu-devel@nongnu.org, xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>

Samuel Thibault wrote:
> Anthony Liguori, le Mon 28 Jul 2008 09:04:54 -0500, a =E9crit :
>>> +/* xen_machine.c */
>>> +extern QEMUMachine xenpv_machine;
>>> +extern QEMUMachine xenfv_machine;
>> Why does xenfv need its own machine type?
>=20
> IIRC that's at least because it adds its own Xen platform -specific PCI=
 card.

That is only one tiny bit of the differences between paravirtual and
fully virtualized machines, there is plenty more.  The question is
whenever qemu should try figure itself whenever the virtual machine it
serves is fully virtualized or whenever we'll explicitly tell it qemu.

I think it is better to explicitly tell qemu whenever we want create a
paravirtual or a full virtualized machine.  First, because this is how
it is handled right now in xen (via -M [ xenpv | xenfv ] ), and second,
it leaves the door open to have qemu also create the domain.

cheers,
  Gerd

--=20
http://kraxel.fedorapeople.org/xenner/