From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KNpJn-0001Kl-MH for qemu-devel@nongnu.org; Tue, 29 Jul 2008 09:32:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KNpJm-0001J1-IN for qemu-devel@nongnu.org; Tue, 29 Jul 2008 09:32:46 -0400 Received: from [199.232.76.173] (port=35653 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KNpJm-0001Ik-Di for qemu-devel@nongnu.org; Tue, 29 Jul 2008 09:32:46 -0400 Received: from an-out-0708.google.com ([209.85.132.243]:46012) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KNpJm-0007wv-6B for qemu-devel@nongnu.org; Tue, 29 Jul 2008 09:32:46 -0400 Received: by an-out-0708.google.com with SMTP id d18so1827829and.130 for ; Tue, 29 Jul 2008 06:32:45 -0700 (PDT) Message-ID: <488F1BDB.90702@codemonkey.ws> Date: Tue, 29 Jul 2008 08:32:11 -0500 From: Anthony Liguori 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> <488DDD2C.10308@redhat.com> <20080729081034.GG32498@redhat.com> In-Reply-To: <20080729081034.GG32498@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: xen-devel@lists.xensource.com, Gerd Hoffmann , qemu-devel@nongnu.org Daniel P. Berrange wrote: > On Mon, Jul 28, 2008 at 04:52:28PM +0200, Gerd Hoffmann wrote: > >>>> +/* xen_machine.c */ >>>> +extern QEMUMachine xenpv_machine; >>>> +extern QEMUMachine xenfv_machine; >>>> >>> Why does xenfv need its own machine type? >>> >> This is how xen's qemu-dm handles it at the moment and I've decided to >> do it the same way for simplicity. I think qemu could also figure it >> using a hypercall. >> > > This is something I originally added to QEMU in Xen's tree. The basic > idea is that the 'xenpv' macjine is a machine which /only/ provides the > paravirtualized Xen backends drivers. The 'xenfv' machine type is just > the same as the 'pc' machine type, but with the /addition/ of the Xen > paravirtualized backends. Perhaps the latter could be thought of as > more of a 'xenpc' (cf 'pc' and 'isapc') becasue its a variation on the > regular PC machine type. Annoying that all the acronyms I come up with > only differ by one letter :-) > Why wouldn't the Xen backends be added by appropriate -net or -drive options? For instance, qemu -drive file=foo.img,if=xen -net nic,model=xen Regards, Anthony Liguori > Daniel >