From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KXzva-0005hW-W6 for qemu-devel@nongnu.org; Tue, 26 Aug 2008 10:53:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KXzvZ-0005gU-U5 for qemu-devel@nongnu.org; Tue, 26 Aug 2008 10:53:50 -0400 Received: from [199.232.76.173] (port=38983 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KXzvZ-0005gN-IS for qemu-devel@nongnu.org; Tue, 26 Aug 2008 10:53:49 -0400 Received: from mx1.redhat.com ([66.187.233.31]:48462) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KXzvZ-00072Q-3P for qemu-devel@nongnu.org; Tue, 26 Aug 2008 10:53:49 -0400 Date: Tue, 26 Aug 2008 15:53:42 +0100 From: "Daniel P. Berrange" Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen support Message-ID: <20080826145342.GH19615@redhat.com> References: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48B417E1.6090709@redhat.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: Gerd Hoffmann Cc: xen-devel@lists.xensource.com, Ian Jackson , qemu-devel@nongnu.org On Tue, Aug 26, 2008 at 04:49:05PM +0200, Gerd Hoffmann wrote: > Daniel P. Berrange wrote: > > On Tue, Aug 26, 2008 at 04:31:49PM +0200, Gerd Hoffmann wrote: > >> Daniel P. Berrange wrote: > >>> I'll try to enumerate the scenarios here... > >>> > >>> On KVM, using Xenner + shell : No special args > >>> On KVM, using Xenner + libvirtd : -xen-create > >> This is "xen emulation" and (according to long term plan plan) doesn't > >> require kvm but should work with qemu emulating things too. This means > >> it doesn't depend on kvm, you can do that with xen underneath too. This > >> is what the -xen-emulate switch is good for. > > > > Wouldn't the non-KVM case already be dealt with by the -no-kvm command > > line arg to QEMU ? > > 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. Oh, i see what you mean. Existing naming practice would suggest naming it -no-xenhv or just -no-xen All these '-no-XXX' args are getting a little silly though. I'd rather tell QEMU what I *do* want, than what I don't want. A generic arg '-accelerator none|xen|kvm|kqemu' might be worth considering in the future. That can be a separate discussion from these patches though - we should just follow the -no-XXX naming for now to minimize diffs 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 :|