From: Eric Blake <eblake@redhat.com>
To: jbaron@redhat.com, QEMU Developers <qemu-devel@nongnu.org>
Cc: David Allan <dallan@redhat.com>
Subject: [Qemu-devel] q35 and ahci
Date: Tue, 17 Jul 2012 09:31:46 -0600 [thread overview]
Message-ID: <50058562.8000108@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
> Update on q35 testing with various os's.
>
> Linux
> -----
> -RHEL6.3 installs + runs
> -Fedora 16 install + runs
> -Fedora 17 - squashfs errors
> running on already installed f17 seems ok.
Pardon my high-level question (I haven't been following q35 threads
closely), but I just looked at http://wiki.qemu.org/Features/Q35 for the
first time. Am I correct that all we are doing is adding a new machine
model, but that it will still be possible to select the older machine
model for migration compatibility when migrating a guest in from an
older qemu? Does libvirt need to do anything special to its generated
command line to specify the old vs. the new machine model?
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next reply other threads:[~2012-07-17 15:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 15:31 Eric Blake [this message]
2012-07-17 15:47 ` [Qemu-devel] q35 and ahci Jason Baron
2012-07-17 15:50 ` Daniel P. Berrange
2012-07-18 13:34 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2012-07-03 16:16 Jason Baron
2012-07-03 18:25 ` Alexander Graf
2012-07-03 18:38 ` Jason Baron
2012-07-03 18:41 ` Alexander Graf
2012-07-03 18:46 ` Jason Baron
2012-07-03 18:52 ` Alexander Graf
2012-07-03 20:37 ` Jason Baron
2012-07-03 20:54 ` Alexander Graf
2012-07-04 1:29 ` Jason Baron
2012-07-04 8:33 ` Alexander Graf
2012-07-05 14:06 ` Jason Baron
2012-07-05 15:07 ` Alexander Graf
2012-07-20 15:27 ` Jason Baron
2012-07-22 6:48 ` Gleb Natapov
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=50058562.8000108@redhat.com \
--to=eblake@redhat.com \
--cc=dallan@redhat.com \
--cc=jbaron@redhat.com \
--cc=qemu-devel@nongnu.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).