This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [Qemu-devel] [PATCH 05/13] xen: groundwork for xen s

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 <domid> 
> >> 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

|: 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 :|

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>