WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 4/5] libxl: Makes libxl be able to call Qemu upst

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 4/5] libxl: Makes libxl be able to call Qemu upstream for XenPV guest.
From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date: Fri, 10 Dec 2010 18:14:28 +0000 (GMT)
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 10 Dec 2010 10:16:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.1.10.1012101748200.25952@xxxxxxxxxxxxxxxxxxxxxxx>
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: <1291923777-8712-1-git-send-email-anthony.perard@xxxxxxxxxx> <1291923777-8712-5-git-send-email-anthony.perard@xxxxxxxxxx> <19714.26235.193745.442453@xxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.1.10.1012101748200.25952@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 1.10 (DEB 962 2008-03-14)
On Fri, 10 Dec 2010, Anthony PERARD wrote:

> On Fri, 10 Dec 2010, Ian Jackson wrote:
>
> > anthony.perard@xxxxxxxxxx writes ("[Xen-devel] [PATCH 4/5] libxl: Makes 
> > libxl be able to call Qemu upstream for XenPV guest."):
> > > From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
> > >
> > > In libxl_build_device_model_args_new:
> > >   - Adds -xen-attach options to the list of arguments to Qemu.
> >
> > Is that understood by qemu-xen ?


> Not really, it is understood by Qemu only when we have this:
> #if defined(CONFIG_XEN) && !defined(CONFIG_DM).
>
> And even in this case, it will do nothing because the variable that
> receives the option is write only, it is never read.
>
> So the answer is no, it is not understood by Qemu.

You will read qemux-xen, here ...

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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