From: Serge Hallyn <serge.hallyn@canonical.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: kvm <kvm@vger.kernel.org>, "Scott Moser" <smoser@ubuntu.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Cole Robinson" <crobinso@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] qemu-kvm: remove "boot=on|off" drive parameter compatibility (fwd)
Date: Mon, 1 Oct 2012 11:50:42 -0500 [thread overview]
Message-ID: <20121001165042.GA4255@sergelap> (raw)
In-Reply-To: <CAFEAcA9GBwHmeTrHDtYDzt-PF0G0crQq4jAViXmpYqabEF4jfg@mail.gmail.com>
Quoting Peter Maydell (peter.maydell@linaro.org):
> On 1 October 2012 15:15, Serge Hallyn <serge.hallyn@canonical.com> wrote:
> > We (Ubuntu) plan to switch to qemu in the next release which opens in
> > November. I suppose there's likely to be a hiccough or two, but I can't
> > think of any offhand.
>
> Are you planning to do that for all CPU target architectures, or
> to maintain the current split between x86 and everything-else ?
>
> -- PMM
I'll have to talk to qemu-linaro folks about that. I don't mind carrying
patchsets (that are headed upstream) to enable some chipsets if that's
what's needed to consolidate the source trees. The bigger question
relates to main vs universe. For instance qemu-system is built against
vde2, and qemu-kvm-spice against spice, both of which are in universe.
I understand the distinction may change or disappear soon, so this may
not be an issue.
I intend to schedule a session on this at UDS.
-serge
prev parent reply other threads:[~2012-10-01 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1210010924390.4846@brickies>
2012-10-01 14:15 ` [Qemu-devel] qemu-kvm: remove "boot=on|off" drive parameter compatibility (fwd) Serge Hallyn
2012-10-01 14:26 ` Peter Maydell
2012-10-01 16:50 ` Serge Hallyn [this message]
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=20121001165042.GA4255@sergelap \
--to=serge.hallyn@canonical.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=crobinso@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=smoser@ubuntu.com \
/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).