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] qemu and xl semantics

To: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: Re: [Xen-devel] qemu and xl semantics
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Fri, 17 Dec 2010 09:15:14 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 17 Dec 2010 01:15:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201012171000.38220.Christoph.Egger@xxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <201012171000.38220.Christoph.Egger@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2010-12-17 at 09:00 +0000, Christoph Egger wrote:
> Hi!
> 
> When I start a guest with xm  the disk startup script assigns a loopback 
> device for qemu to open it.
> 
> Now it seems that qemu opens the disk image directly. Then when
> the loopback device wants to open the disk image then that fails
> with EBUSY.

By "Now..." you mean "With xl..." ?

> How is the disk startup script supposed to work with the new
> semantic for
> a) HVM guests
> b) PV guests
> ?

I think this is all very specific to the precise disk type you have in
your config, i.e. tap: vs file: vs phy: etc. Which are you using?

> 
> The network startup script adds the tap device to the bridge
> or assigns an ip address.
> With xl neither the disk nor the network script runs.
> So when I start the guest with xl then I have
> the tap device assigned to the guest but the
> tap device is not configured in the dom0.
> 
> How does the 'xl' way work in respect to the network script
> used with 'xm' ?

On Linux these are run from the hotplug event, via the udev rules. I
presume you are talking about on NetBSD though?

Under Linux I think it was always the same under xm too although there
have been some tweaks recently, e.g. the vif script is now always
/etc/xen/scripts/vif-setup which handles the indirection to the script
in the domain config or the default. Previously xend the hotplug rules
called the configured script directly. This change was
21549:8bcaec29574e and was common to xm and xl I think.

Ian.


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