From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KYHlX-00032j-LY for qemu-devel@nongnu.org; Wed, 27 Aug 2008 05:56:39 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KYHlV-000327-Rs for qemu-devel@nongnu.org; Wed, 27 Aug 2008 05:56:39 -0400 Received: from [199.232.76.173] (port=34410 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KYHlV-00031z-JN for qemu-devel@nongnu.org; Wed, 27 Aug 2008 05:56:37 -0400 Received: from mx1.redhat.com ([66.187.233.31]:43864) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KYHlV-0007Wd-5z for qemu-devel@nongnu.org; Wed, 27 Aug 2008 05:56:37 -0400 Date: Wed, 27 Aug 2008 10:56:25 +0100 From: "Daniel P. Berrange" Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support Message-ID: <20080827095625.GD25099@redhat.com> References: <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> <48B51599.7040807@redhat.com> <18613.9249.931147.770220@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18613.9249.931147.770220@mariner.uk.xensource.com> Reply-To: "Daniel P. Berrange" , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ian Jackson Cc: xen-devel@lists.xensource.com, Gerd Hoffmann , qemu-devel@nongnu.org On Wed, Aug 27, 2008 at 10:53:37AM +0100, Ian Jackson wrote: > Gerd Hoffmann writes ("Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support"): > > 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 specify xen domain id. > > -xen-attach attach to specified domain (created by xend). > > -xen-create create the domain directly. > > > > Comments? > > That sounds reasonable. Can we please make sure that the usage > message for -xen-create and -xen-attach makes it clear that a user > should not supply these options on a Xen system using the Xen > management toolstack ? (Which I think includes a system using xm and > also a system using libvirt, although perhaps Daniel Berrange will > correct me.) There's no requirement from libvirt itself - just whatever infrastructure libvirt is using. So just a message about XenD/xm would be sufficient. 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 :|