From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] Remove hardcoded xen-platform device initialization
Date: Tue, 18 Jun 2013 21:12:25 +0200 [thread overview]
Message-ID: <51C0B119.8070704@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306181951450.4548@kaball.uk.xensource.com>
Il 18/06/2013 20:56, Stefano Stabellini ha scritto:
>> >
>> > Ok. I guess we can have the ability to override the machine type in the VM config, so you could still kick off an older qemu with a newer libxl - but it sounds like the auto-discovery idea is a no-go then.
> xenfv-2.0 is a bad idea, like Paolo wrote, it should be possible to just
> use -M pc for HVM guests and retain -M xenpv for pv guests.
>
> However it seems to me that we also need a way in libxl to find out
> whether QEMU is new enough for us to be able to use -M pc.
> We can't just assume that users will be able to figure out the magic
> rune they need to write in the VM config file to solve their VM crash at
> boot problem.
>
> We could spawn an instance of QEMU just to figure out the QEMU version
> but we certainly cannot do that every time we start a new VM.
> Once we figure out the QEMU version the first time we could write it to
> xenstore so that the next time we don't have to go through the same
> process again.
Can you just assume that 4.4 requires QEMU 1.6 or newer?
Paolo
next prev parent reply other threads:[~2013-06-18 19:12 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 [this message]
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
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=51C0B119.8070704@redhat.com \
--to=pbonzini@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=Paul.Durrant@citrix.com \
--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).