From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KYGmQ-00046R-CZ
	for qemu-devel@nongnu.org; Wed, 27 Aug 2008 04:53:30 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KYGmO-00043x-Cy
	for qemu-devel@nongnu.org; Wed, 27 Aug 2008 04:53:29 -0400
Received: from [199.232.76.173] (port=33373 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KYGmO-00043T-7P
	for qemu-devel@nongnu.org; Wed, 27 Aug 2008 04:53:28 -0400
Received: from mx2.redhat.com ([66.187.237.31]:60597)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1KYGmM-0006ST-Ub
	for qemu-devel@nongnu.org; Wed, 27 Aug 2008 04:53:27 -0400
Message-ID: <48B51599.7040807@redhat.com>
Date: Wed, 27 Aug 2008 10:51:37 +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>	<48B40306.2080104@redhat.com>	<20080826132309.GC19615@redhat.com>	<18612.1557.455011.713070@mariner.uk.xensource.com>	<20080826141400.GE19615@redhat.com>	<48B413D5.3080203@redhat.com>	<20080826144056.GG19615@redhat.com>	<48B417E1.6090709@redhat.com>
	<18612.6399.960344.359943@mariner.uk.xensource.com>
In-Reply-To: <18612.6399.960344.359943@mariner.uk.xensource.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: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org

Ian Jackson wrote:
> Gerd Hoffmann writes ("Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support"):
>> But when running on xen we want being able to qemu tell it should *not*
>> use the xen hypervisor but emulate things, thus -xen-emulate.
> 
> That should be the default.  It is not safe to use the Xen hypervisor
> directly if there is a management toolstack which expects to mediate
> domain creation.

Ok.  I think we have three cases then:

  (1) xen emulation using xenner (default, with or without kvm).
  (2) running on xen, with xend creating the domain, and
  (3) running on xen, with qemu creating the domain.

For (2) and (3) we need command line switches to enable these modes.
Specifying a domain ID makes sense in all three cases though.  So I'd
keep the -xen-domid switch, like this:

  -xen-domid <nr>    specify xen domain id.
  -xen-attach        attach to specified domain (created by xend).
  -xen-create        create the domain directly.

Comments?

cheers,
  Gerd