From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-9p: migrate virtio subsections
Date: Thu, 24 Sep 2015 10:00:46 +0200 [thread overview]
Message-ID: <20150924100046.1ea1d136@bahia.local> (raw)
In-Reply-To: <20150921100934.3d2067d4@bahia.local>
On Mon, 21 Sep 2015 10:09:34 +0200
Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
> On Sat, 19 Sep 2015 15:34:02 +0530
> "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
>
> > Greg Kurz <gkurz@linux.vnet.ibm.com> writes:
> >
> > > In a cross-endian setup, the virtio-9p device has state in @device_endian. It
> > > must be migrated.
> > >
> > > Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> >
> > With 9p mounted, we don't support qemu migration. We have
> > migration blocker added in v9fs_attach.
> >
>
> Ok I should have been more precise... If you unmount the 9p share, then
> migrate, then try to remount, you end up with a hung mount command because
> @device_endian has the wrong value...
>
Michael ? Any input ?
> > > ---
> > > hw/9pfs/virtio-9p-device.c | 11 +++++++++++
> > > 1 file changed, 11 insertions(+)
> > >
> > > diff --git a/hw/9pfs/virtio-9p-device.c b/hw/9pfs/virtio-9p-device.c
> > > index 93a407c45926..e3abcfaffb2a 100644
> > > --- a/hw/9pfs/virtio-9p-device.c
> > > +++ b/hw/9pfs/virtio-9p-device.c
> > > @@ -43,6 +43,16 @@ static void virtio_9p_get_config(VirtIODevice *vdev, uint8_t *config)
> > > g_free(cfg);
> > > }
> > >
> > > +static void virtio_9p_save(QEMUFile *f, void *opaque)
> > > +{
> > > + virtio_save(VIRTIO_DEVICE(opaque), f);
> > > +}
> > > +
> > > +static int virtio_9p_load(QEMUFile *f, void *opaque, int version_id)
> > > +{
> > > + return virtio_load(VIRTIO_DEVICE(opaque), f, version_id);
> > > +}
> > > +
> > > static void virtio_9p_device_realize(DeviceState *dev, Error **errp)
> > > {
> > > VirtIODevice *vdev = VIRTIO_DEVICE(dev);
> > > @@ -130,6 +140,7 @@ static void virtio_9p_device_realize(DeviceState *dev, Error **errp)
> > > }
> > > v9fs_path_free(&path);
> > >
> > > + register_savevm(dev, "virtio-9p", -1, 1, virtio_9p_save, virtio_9p_load, s);
> > > return;
> > > out:
> > > g_free(s->ctx.fs_root);
>
>
prev parent reply other threads:[~2015-09-24 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 14:24 [Qemu-devel] [PATCH] virtio-9p: migrate virtio subsections Greg Kurz
2015-09-19 10:02 ` Aneesh Kumar K.V
2015-09-19 10:04 ` Aneesh Kumar K.V
2015-09-21 8:09 ` Greg Kurz
2015-09-24 8:00 ` Greg Kurz [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=20150924100046.1ea1d136@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=mst@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).