From: "Serge E. Hallyn" <serge@hallyn.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: "Ryan Harper" <ryan.harper@canonical.com>,
"Serge Hallyn" <serge.hallyn@canonical.com>,
"quintela@redhat.com" <quintela@redhat.com>,
Libvirt <libvir-list@redhat.com>,
"Serge Hallyn" <serge.hallyn@ubuntu.com>,
"Alexander Graf" <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Cole Robinson" <crobinso@redhat.com>,
"Amit Shah" <amit.shah@redhat.com>,
"Bruce Rogers" <brogers@suse.com>,
"Andreas Färber" <afaerber@suse.de>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm
Date: Thu, 7 Aug 2014 21:26:49 +0200 [thread overview]
Message-ID: <20140807192649.GA10037@mail.hallyn.com> (raw)
In-Reply-To: <6AF1AF51-36D9-4939-9184-AA555A043AFE@alex.org.uk>
Quoting Alex Bligh (alex@alex.org.uk):
> Serge,
>
> On 7 Aug 2014, at 03:50, Serge Hallyn <serge.hallyn@ubuntu.com> wrote:
>
> > This worked for me when migrating by hand. I'm trying to make it work
> > through libvirt, using the following patch. (So whether to have
> > pc-1.0 be treated as qemu's or qemu-kvm's pc-1.0 is specifed using a
> > boolean in /etc/libvirt/qemu.conf) Qemu starts with decent
> > looking args, but for some reason the the migration is failing -
> > still looking through the logfile to figure out why.
>
> Are you using exactly the same arguments by hand and with libvirt?
>
> Also, on reflection, given one of the changes between 1.0 and 2.0
> is ACPI, I should probably have done some testing with an ACPI
> enabled image, rather than just cirros (which not ACPI enabled);
> any chance this is ACPI related?
A-ha, acpi wasn't a problem. I actually had a general migration
problem even when coming from other utopic hosts. With that fixed,
I've got successful migration from qemu-kvm 1.0 in precise to
a utopic host.
-serge
next prev parent reply other threads:[~2014-08-07 19:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 19:12 [Qemu-devel] [PATCH v2 0/2] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm Alex Bligh
2014-08-01 19:12 ` [Qemu-devel] [PATCH v2 1/2] " Alex Bligh
2014-08-01 19:12 ` [Qemu-devel] [PATCH v2 2/2] Add configure option --enable-pc-1-0-qemu-kvm Alex Bligh
2014-08-04 13:35 ` Michael S. Tsirkin
2014-08-04 13:31 ` [Qemu-devel] [PATCH v2 0/2] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm Michael S. Tsirkin
2014-08-04 13:51 ` Alex Bligh
2014-08-04 14:26 ` Michael S. Tsirkin
2014-08-04 16:11 ` Alex Bligh
2014-08-04 16:22 ` Michael S. Tsirkin
2014-08-04 16:46 ` Alex Bligh
2014-08-04 16:59 ` Michael S. Tsirkin
2014-08-04 17:08 ` Alex Bligh
2014-08-04 17:16 ` Michael S. Tsirkin
2014-08-04 15:07 ` Serge Hallyn
2014-08-07 2:50 ` Serge Hallyn
2014-08-07 5:58 ` Alex Bligh
2014-08-07 12:56 ` Serge E. Hallyn
2014-08-07 19:26 ` Serge E. Hallyn [this message]
2014-08-08 7:23 ` Alex Bligh
2014-08-08 20:28 ` Serge E. Hallyn
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=20140807192649.GA10037@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=alex@alex.org.uk \
--cc=amit.shah@redhat.com \
--cc=brogers@suse.com \
--cc=crobinso@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=ryan.harper@canonical.com \
--cc=serge.hallyn@canonical.com \
--cc=serge.hallyn@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).