From: Anthony Liguori <anthony@codemonkey.ws>
To: Mark McLoughlin <markmc@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] virtio-net migration fix
Date: Wed, 07 Jan 2009 11:51:04 -0600 [thread overview]
Message-ID: <4964EB88.1010303@codemonkey.ws> (raw)
In-Reply-To: <1231323650.5050.8.camel@localhost.localdomain>
> Thanks, I should have seen that myself ...
>
> Cheers,
> Mark.
>
> From: Mark McLoughlin <markmc@redhat.com>
> Subject: [PATCH] virtio-net migration fix
>
> We are failing to save whether the guest will supply us rx
> buffers using the new mergeable format; this can cause a
> migrated guest to crash with:
>
> virtio-net header not in first element
>
> Bump the savevm version number and refuse to load v1 saves
> just to be on the safe side.
>
> Signed-off-by: Mark McLoughlin <markmc@redhat.com>
>
Applied. Thanks.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-01-07 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 11:44 [Qemu-devel] [PATCH] virtio-net migration fix Mark McLoughlin
2009-01-06 17:26 ` [Qemu-devel] " Anthony Liguori
2009-01-07 10:20 ` Mark McLoughlin
2009-01-07 17:51 ` Anthony Liguori [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=4964EB88.1010303@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=markmc@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 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).