From: Paolo Bonzini <pbonzini@redhat.com>
To: Cole Robinson <crobinso@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>, Laine Stump <laine@laine.org>
Subject: Re: [Qemu-devel] When should management tools use q35?
Date: Sun, 01 Jun 2014 20:14:40 +0200 [thread overview]
Message-ID: <538B6D90.70202@redhat.com> (raw)
In-Reply-To: <538A806D.7010300@redhat.com>
Il 01/06/2014 03:22, Cole Robinson ha scritto:
> Hi all,
>
> There was a bit of discussion recently about exposing q35 in virt-manager:
>
> http://www.redhat.com/archives/virt-tools-list/2014-May/msg00001.html
>
> In that thread, Gerd suggested a 'rule of thumb' to use q35 for any guest OS
> released in 2010 or later. Sounds reasonable to me, but I'm curious if anyone
> else wants to weigh in.
>
> Is q35 in 'good enough' shape to turn on a default like that? Does it still
> block migration? (pretty sure that was fixed, but I haven't confirmed)
AHCI migration still does not work reliably. I think that we could
change it to block migration only if you have IDE drives, but still
means that exposing q35 in virt-manager might be problematic.
Paolo
parent reply other threads:[~2014-06-01 18:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <538A806D.7010300@redhat.com>]
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=538B6D90.70202@redhat.com \
--to=pbonzini@redhat.com \
--cc=crobinso@redhat.com \
--cc=kraxel@redhat.com \
--cc=laine@laine.org \
--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).