From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>,
stefanha@redhat.com, lprosek@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 10:30:14 +0000 [thread overview]
Message-ID: <20161115103014.GE2038@work-vm> (raw)
In-Reply-To: <e2cee722-9d53-7589-ad68-e2662ca38138@profihost.ag>
* 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.
Dave
>
> Greets,
> Stefan
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-11-15 10:30 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 [this message]
2016-11-15 10:37 ` Stefan Priebe - Profihost AG
2016-11-15 11:07 ` Ladi Prosek
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=20161115103014.GE2038@work-vm \
--to=dgilbert@redhat.com \
--cc=lprosek@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.