Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
	virtio-comment@lists.oasis-open.org, jasowang@redhat.com,
	eperezma@redhat.com, aadam@redhat.com, oren@nvidia.com,
	shahafs@nvidia.com, parav@nvidia.com, bodong@nvidia.com,
	amikheev@nvidia.com, stefanha@redhat.com
Subject: Re: [virtio-comment] [PATCH 1/1] live_migration: initial support for migrating virtio devices
Date: Wed, 7 Jul 2021 17:15:55 +0300	[thread overview]
Message-ID: <58a279bd-57c9-3db8-9809-e56da6e7bf5e@nvidia.com> (raw)
In-Reply-To: <20210707100658-mutt-send-email-mst@kernel.org>


On 7/7/2021 5:09 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 07, 2021 at 03:51:25PM +0300, Max Gurtovoy wrote:
>>>> +This document will describe the needed updates to the virtio
>>>> specification for adding live migration support for various
>>>> devices. Live migration is one of the most important features of
>>>> virtualization and virtio devices are oftenly found in virtual
>>>> environments so setting a standard mechanism for this feature will
>>>> allow virtio providers to develop compliant devices that will use
>>>> standard drivers for that matter.
>>> Is this supposed to happen on the device side? Do drivers need to get
>>> involved, or is it transparent to them?
>> Guest drivers should be involved.
> Hmm that's a big drawback of this design then.

sorry it was a typo :)

Guest drivers *shouldn't* be involved.

of course.


> If nothing else, it should be possible to get state from device and
> replace it with an emulated software implementation
> for duration of migration, transparently to guest drivers.
>
>


  reply	other threads:[~2021-07-07 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24  8:20 [virtio-comment] [RFC PATCH v2 0/1] Live migration for VIRTIO Max Gurtovoy
2021-06-24  8:20 ` [virtio-comment] [PATCH 1/1] live_migration: initial support for migrating virtio devices Max Gurtovoy
2021-06-28 15:22   ` Cornelia Huck
2021-07-07 12:51     ` Max Gurtovoy
2021-07-07 14:08       ` Jason Wang
2021-07-07 14:09       ` Michael S. Tsirkin
2021-07-07 14:15         ` Max Gurtovoy [this message]
2021-07-07 17:01       ` Cornelia Huck
2021-07-05 15:45   ` Stefan Hajnoczi
2021-07-06  2:45     ` Jason Wang

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=58a279bd-57c9-3db8-9809-e56da6e7bf5e@nvidia.com \
    --to=mgurtovoy@nvidia.com \
    --cc=aadam@redhat.com \
    --cc=amikheev@nvidia.com \
    --cc=bodong@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=oren@nvidia.com \
    --cc=parav@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-comment@lists.oasis-open.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