From: Paolo Bonzini <pbonzini@redhat.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Paul Durrant" <Paul.Durrant@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"Andreas Färber" <afaerber@suse.de>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] Remove hardcoded xen-platform device initialization
Date: Wed, 19 Jun 2013 14:51:24 +0200 [thread overview]
Message-ID: <51C1A94C.2090704@redhat.com> (raw)
In-Reply-To: <1371632169.22783.81.camel@zakaz.uk.xensource.com>
Il 19/06/2013 10:56, Ian Campbell ha scritto:
> The case with xl is more like your example 5:
Ok, that's what I remembered. :)
> > Example 5: you use "virsh create" to start a VM based on an XML file,
> > rather than "virsh define"+"virsh start" as in examples 1-2. You lose
> > any guarantee that hardware does not change. Not frowned upon as much
> > as example 4, since the VM is supposed to be transient.
>
> For something like xapi we'd likely want to support some sort of model
> similar to libvirt, so whatever we do at the libxl layer needs to
> consider both approaches.
I think xapi can itself query qemu if this is the case (in this respect,
libvirt is somewhat in the middle between xl and xapi, depending on
whether you use transient or persistent domains). Or perhaps you can
add an xl command to query qemu and provide capabilities.
xl can default to some "blessed" old-enough machine if it is available
or just the newest "pc" if the blessed machine is unavailable. And of
course it can be overridden by the guest config.
Paolo
next prev parent reply other threads:[~2013-06-19 12:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 9:50 [Qemu-devel] [PATCH] Remove hardcoded xen-platform device initialization Paul Durrant
2013-06-13 17:33 ` Stefano Stabellini
2013-06-13 17:44 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2013-06-13 18:02 ` Paolo Bonzini
2013-06-14 9:00 ` Paul Durrant
2013-06-14 10:38 ` Paul Durrant
2013-06-14 13:50 ` Paolo Bonzini
2013-06-14 14:11 ` Paul Durrant
2013-06-14 14:57 ` Paolo Bonzini
2013-06-14 15:10 ` Paul Durrant
2013-06-18 18:56 ` Stefano Stabellini
2013-06-18 19:12 ` Paolo Bonzini
2013-06-18 19:35 ` Stefano Stabellini
2013-06-18 21:38 ` Andreas Färber
2013-06-19 8:29 ` Ian Campbell
2013-06-19 8:37 ` Paul Durrant
2013-06-19 8:41 ` Paolo Bonzini
2013-06-19 8:56 ` Ian Campbell
2013-06-19 9:11 ` Paul Durrant
2013-06-19 12:51 ` Paolo Bonzini [this message]
2013-06-19 13:47 ` Stefano Stabellini
2013-06-19 8:27 ` Paul Durrant
2013-06-19 13:55 ` Stefano Stabellini
2013-06-19 15:09 ` Ian Campbell
2013-06-19 8:11 ` Ian Campbell
2013-06-19 13:53 ` Stefano Stabellini
2013-06-19 14:00 ` Paul Durrant
2013-06-19 16:27 ` Stefano Stabellini
2013-06-20 7:32 ` Paul Durrant
2013-06-14 8:56 ` Paul Durrant
2013-06-14 8:50 ` [Qemu-devel] " Paul Durrant
2013-06-14 13:52 ` Paolo Bonzini
2013-06-14 13:57 ` Paul Durrant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51C1A94C.2090704@redhat.com \
--to=pbonzini@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).