From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] live migration fails after host kernel upgrade (3.12 => 3.18)
Date: Mon, 23 Mar 2015 13:16:44 +0100 [thread overview]
Message-ID: <5510042C.9080106@profihost.ag> (raw)
In-Reply-To: <20150323115430.GB9268@stefanha-thinkpad.redhat.com>
Hi,
Thanks.
I fixed it - there is already a patchseries in 4.0 to fix this. It will
be backported in 3.18.10 or 3.18.11.
Stefan
Am 23.03.2015 um 12:54 schrieb Stefan Hajnoczi:
> On Sun, Mar 15, 2015 at 09:59:25AM +0100, Stefan Priebe wrote:
>> after upgrading the host kernel from 3.12 to 3.18 live migration fails with
>> the following qemu output (guest running on a host with 3.12 => host with
>> 3.18):
>>
>> kvm: Features 0x30afffe3 unsupported. Allowed features: 0x79bfbbe7
>> qemu: warning: error while loading state for instance 0x0 of device
>> '0000:00:12.0/virtio-net'
>> kvm: load of migration failed: Operation not permitted
>>
>> But i can't
>
> Hi Stefan,
> I haven't checked the exact feature bits but it might be the UFO feature
> problem. The tun driver was changed to drop a feature, this broke live
> migration.
>
> Take a look at
> https://lists.linuxfoundation.org/pipermail/virtualization/2015-February/029217.html
>
> Stefan
>
prev parent reply other threads:[~2015-03-23 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 8:59 [Qemu-devel] live migration fails after host kernel upgrade (3.12 => 3.18) Stefan Priebe
2015-03-23 11:54 ` Stefan Hajnoczi
2015-03-23 12:16 ` Stefan Priebe - Profihost AG [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=5510042C.9080106@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.