From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KXyUj-0006tN-JG
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 09:22:02 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KXyUg-0006pO-AQ
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 09:22:00 -0400
Received: from [199.232.76.173] (port=44016 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KXyUg-0006p9-3I
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 09:21:58 -0400
Received: from mx2.redhat.com ([66.187.237.31]:59156)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1KXyUf-0006Tw-Vi
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 09:21:58 -0400
Message-ID: <48B40306.2080104@redhat.com>
Date: Tue, 26 Aug 2008 15:20:06 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for
	xen support
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>
In-Reply-To: <20080826125742.GB19615@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Reply-To: 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: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>, qemu-devel@nongnu.org

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.
  -xen-emulate     force xen emulation mode.

I'll go add these for the next round.

cheers,
  Gerd