From: Ladi Prosek <lprosek@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Qemu 2.6 => Qemu 2.7 migration: error while loading state for instance 0x0 of device '0000:00:03.0/virtio-balloon'
Date: Tue, 15 Nov 2016 12:07:38 +0100 [thread overview]
Message-ID: <CABdb7359Bc3fnCeWRD4pecpGY3q8v3Ks+0SumPC3r38_wJwdkQ@mail.gmail.com> (raw)
In-Reply-To: <cd334140-3936-a084-e067-216c85f18a19@profihost.ag>
Hi,
On Tue, Nov 15, 2016 at 11:37 AM, Stefan Priebe - Profihost AG
<s.priebe@profihost.ag> wrote:
> Hello,
>
> Am 15.11.2016 um 11:30 schrieb Dr. David Alan Gilbert:
>> * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote:
>>> Hello,
>>>
>>> today i did a first live migration from Qemu 2.6.2 to Qemu 2.7.0. The VM
>>> is running windows and virtio-balloon and with machine type pc-i440fx-2.5.
>>>
>>> The output of the target qemu process was:
>>> kvm_apic_post_load: Yeh
>>> kvm_apic_post_load: Yeh
>>> kvm_apic_post_load: Yeh
>>> kvm_apic_post_load: Yeh
>>> kvm: VQ 2 size 0x80 < last_avail_idx 0x1 - used_idx 0x4
>>> kvm: error while loading state for instance 0x0 of device
>>> '0000:00:03.0/virtio-balloon'
>>> kvm: load of migration failed: Operation not permitted
>>
>> Yes that's a known bug; only seems to affect windows guests, and I believe
>> doesn't even need to cross versions.
>>
>> There's a bunch of fixes that Stefan applied to virtio code
>> that I think fix this; I see that he cc'd qemu-stable.
>> I think it's 4b7f91ed, but I'm not sure if there are others needed.
>
> thanks for pointing to that commit.
>
> Stefan can you tell me whether it's enough to cherry-pick 4b7f91ed into
> 2.7.0 ?
I don't believe that 4b7f91ed will help here (no device reset on
migration). We've seen this error with QEMU running without:
commit 4eae2a657d1ff5ada56eb9b4966eae0eff333b0b
Author: Ladi Prosek <lprosek@redhat.com>
Date: Tue Mar 1 12:14:03 2016 +0100
balloon: fix segfault and harden the stats queue
Is it possible that the VM has run on such a QEMU, then was
live-migrated to 2.6.2, and then to 2.7.0?
Thanks,
Ladi
> Greets,
> Stefan
>
>>
>> Dave
>>>
>>> Greets,
>>> Stefan
>>>
>> --
>> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>>
>
next prev parent reply other threads:[~2016-11-15 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 18:57 [Qemu-devel] Qemu 2.6 => Qemu 2.7 migration: error while loading state for instance 0x0 of device '0000:00:03.0/virtio-balloon' Stefan Priebe - Profihost AG
2016-11-15 10:30 ` Dr. David Alan Gilbert
2016-11-15 10:37 ` Stefan Priebe - Profihost AG
2016-11-15 11:07 ` Ladi Prosek [this message]
2016-11-15 11:19 ` Stefan Priebe - Profihost AG
2016-11-15 12:48 ` Ladi Prosek
2016-11-15 11:01 ` Stefan Hajnoczi
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=CABdb7359Bc3fnCeWRD4pecpGY3q8v3Ks+0SumPC3r38_wJwdkQ@mail.gmail.com \
--to=lprosek@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=s.priebe@profihost.ag \
--cc=stefanha@redhat.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.