This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH] libxl: enabling upstream qemu as pure pv bac

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] libxl: enabling upstream qemu as pure pv backend.
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Wed, 8 Jun 2011 17:09:10 +0100
Cc: Wei Liu <liuw@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 08 Jun 2011 09:06:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1307548380.775.744.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1307503152.31359.2.camel@limbo> <alpine.DEB.2.00.1106081222390.12963@kaball-desktop> <1307536033.775.732.camel@xxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1106081358210.12963@kaball-desktop> <1307538807.775.737.camel@xxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1106081435470.12963@kaball-desktop> <1307541074.775.739.camel@xxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1106081501020.12963@kaball-desktop> <1307548380.775.744.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Wed, 8 Jun 2011, Ian Campbell wrote:
> > > > But if we do this we have to be careful because in the stubdom case the
> > > > libxl_device_model_info that we pass to libxl__create_xenpv_qemu is NOT
> > > > the same used to build the stubdom.
> > > > The info parameter passed to libxl__create_stubdom is the
> > > > libxl_device_model_info that describes the stub qemu-for-FV.
> > > > While the info parameter that we pass to libxl__create_xenpv_qemu is the
> > > > libxl_device_model_info that describes the qemu-for-PV in dom0.
> > > 
> > > Right, my suggestion was that they potentially _could_ be the same, with
> > > the two functions doinging the right thing internally. This would avoid
> > > the need to figure out which params need to be copied from the user
> > > supplied struct to the xenpv one -- they would simply be the same.
> > > 
> > 
> > Ideally the vnc and sdl proprieties of a vfb should be moved into
> > the corresponding fields of device_model_info, because they are not
> > specific to the vfb protocol, rather a configuration of the backend
> > (qemu).
> > This way we wouldn't need libxl__build_xenpv_qemu_args anymore.
> > 
> > I wouldn't use the same device_model_info instance for both qemu-FV and
> > qemu-PV in the stubdom case, I would rather keep them separate.
> OK, then we either need a way to configure both (dupping the options) or
> one needs to be derived from the other in some useful way...

First the vfb configuration is derived from the xenfv configuration by
Then from the vfb we build xenpv in libxl__create_xenpv_qemu.


If we move the sdl and vnc options away from vfb we could derive both
the xenpv configuration and the vfb configuration in
libxl__vfb_and_vkb_from_device_model_info, that would need to be
libxl__create_stubdom would just add the vfb to xenstore and call
libxl__create_xenpv_qemu that doesn't need to do any "translation"
anymore. So I guess it would simplify the code a bit.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>