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: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen s

To: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 26 Aug 2008 14:23:09 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, qemu-devel@xxxxxxxxxx
Delivery-date: Tue, 26 Aug 2008 06:23:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48B40306.2080104@xxxxxxxxxx>
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: <1219336054-15919-1-git-send-email-kraxel@xxxxxxxxxx> <m2n.s.1KWDD7-002TB9@xxxxxxxxxxxxxxxxxxxxxx> <18611.56211.660082.627144@xxxxxxxxxxxxxxxxxxxxxxxx> <20080826125742.GB19615@xxxxxxxxxx> <48B40306.2080104@xxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, Aug 26, 2008 at 03:20:06PM +0200, Gerd Hoffmann wrote:
> Daniel P. Berrange wrote:
> > Probing for whether a domain ID exists in the hypervisor, and if not, then
> > creating it, has a nasty race condition, where XenD could launch QEMU
> > and then (for whatever reason) decide to kill off the domain, but QEMU
> > then re-creates it during its startup procedure.
> Oops.  Yes, that needs to be addressed.
> > If we want QEMU to explicitly created Xen domains from scratch, rather than
> > attaching to an existing one, then there needs to be a way to reliably 
> > specify this behaviour via the CLI.
> So we are scoring at three options for xen now:
>   -xen-domid <nr>  specify xen domain id.
>   -xen-create      ask qemu to create the domain.

Actually I'd invert that, eg   -xen-attach  since common QEMU semantics
are that it is completely in charge of creation. Attaching to an externally
created VM is the xen additional semantics.

|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

Xen-devel mailing list

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