qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>, 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 11:01:09 +0000	[thread overview]
Message-ID: <20161115110109.GE4836@stefanha-x1.localdomain> (raw)
In-Reply-To: <e2cee722-9d53-7589-ad68-e2662ca38138@profihost.ag>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

On Mon, Nov 14, 2016 at 07:57:47PM +0100, Stefan Priebe - Profihost AG wrote:
> 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

Ladi: I don't remember this.  Does it ring a bell for you?

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      parent reply	other threads:[~2016-11-15 11:01 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
2016-11-15 11:19       ` Stefan Priebe - Profihost AG
2016-11-15 12:48         ` Ladi Prosek
2016-11-15 11:01 ` Stefan Hajnoczi [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=20161115110109.GE4836@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=lprosek@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=s.priebe@profihost.ag \
    /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).