All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>,
	QEMU devel <qemu-devel@nongnu.org>,
	KVM mailing list <kvm@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>, Ademar Reis <areis@redhat.com>,
	Cleber Rosa <crosa@redhat.com>
Subject: Re: qemu.git/qemu-kvm.git bugs during migrate + reboot
Date: Tue, 25 Sep 2012 07:59:34 -0500	[thread overview]
Message-ID: <87lifycl6x.fsf@codemonkey.ws> (raw)
In-Reply-To: <505B49A1.5080608@redhat.com>

Lucas Meneghel Rodrigues <lmr@redhat.com> writes:

> Hi guys,
>
> We're seeing the following problem during upstream testing:
>
> qemu: VQ 0 size 0x80 Guest index 0x2d6
>      inconsistent with Host index 0x18: delta 0x2be
>      qemu: warning:  error while loading state for
>      instance 0x0 of device '0000:00:04.0/virtio-blk'
>      load of migration failed
>
> This is happening consistently with qemu and qemu-kvm. Test case is 
> simple, while the vm goes through a reboot loop, a parallel ping-pong 
> migration loop happens.
>
> I'm happy to provide more details and logs.

Can you provide the full command line?

Regards,

Anthony Liguori

>
> Lucas
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>,
	QEMU devel <qemu-devel@nongnu.org>,
	KVM mailing list <kvm@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>, Ademar Reis <areis@redhat.com>,
	Cleber Rosa <crosa@redhat.com>
Subject: Re: [Qemu-devel] qemu.git/qemu-kvm.git bugs during migrate + reboot
Date: Tue, 25 Sep 2012 07:59:34 -0500	[thread overview]
Message-ID: <87lifycl6x.fsf@codemonkey.ws> (raw)
In-Reply-To: <505B49A1.5080608@redhat.com>

Lucas Meneghel Rodrigues <lmr@redhat.com> writes:

> Hi guys,
>
> We're seeing the following problem during upstream testing:
>
> qemu: VQ 0 size 0x80 Guest index 0x2d6
>      inconsistent with Host index 0x18: delta 0x2be
>      qemu: warning:  error while loading state for
>      instance 0x0 of device '0000:00:04.0/virtio-blk'
>      load of migration failed
>
> This is happening consistently with qemu and qemu-kvm. Test case is 
> simple, while the vm goes through a reboot loop, a parallel ping-pong 
> migration loop happens.
>
> I'm happy to provide more details and logs.

Can you provide the full command line?

Regards,

Anthony Liguori

>
> Lucas
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-09-25 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 16:51 qemu.git/qemu-kvm.git bugs during migrate + reboot Lucas Meneghel Rodrigues
2012-09-20 16:51 ` [Qemu-devel] " Lucas Meneghel Rodrigues
2012-09-25 12:59 ` Anthony Liguori [this message]
2012-09-25 12:59   ` Anthony Liguori
2012-09-25 13:17   ` Lucas Meneghel Rodrigues
2012-09-25 13:17     ` [Qemu-devel] " Lucas Meneghel Rodrigues

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=87lifycl6x.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=areis@redhat.com \
    --cc=avi@redhat.com \
    --cc=crosa@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.