From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KXyVw-0008Ew-4l
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 09:23:16 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KXyVu-0008EM-EJ
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 09:23:15 -0400
Received: from [199.232.76.173] (port=44063 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KXyVu-0008EH-4N
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 09:23:14 -0400
Received: from mx1.redhat.com ([66.187.233.31]:50023)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <berrange@redhat.com>) id 1KXyVu-0006oc-4Y
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 09:23:14 -0400
Date: Tue, 26 Aug 2008 14:23:09 +0100
From: "Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for
	xen support
Message-ID: <20080826132309.GC19615@redhat.com>
References: <1219336054-15919-1-git-send-email-kraxel@redhat.com>
	<m2n.s.1KWDD7-002TB9@chiark.greenend.org.uk>
	<18611.56211.660082.627144@mariner.uk.xensource.com>
	<20080826125742.GB19615@redhat.com> <48B40306.2080104@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48B40306.2080104@redhat.com>
Reply-To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>, qemu-devel@nongnu.org

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.

Regards,
Daniel
-- 
|: 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 :|