From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Sameeh Jubran" <sameeh@daynix.com>,
"Yan Vugenfirer" <yan@daynix.com>,
"Jason Wang" <jasowang@redhat.com>,
qemu-devel@nongnu.org, "Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [RFC 0/2] Attempt to implement the standby feature for assigned network devices
Date: Wed, 5 Dec 2018 15:58:45 -0500 [thread overview]
Message-ID: <20181205155739-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <154404267804.6063.6272296350458255377@sif>
On Wed, Dec 05, 2018 at 02:44:38PM -0600, Michael Roth wrote:
> > So how important is it that setting F_STANDBY cap doesn't break older
> > guests? If the idea is to support live migration with VFs then aren't
> > we still dead in the water if the guest boots okay but doesn't have
> > the requisite functionality to be migrated later? Shouldn't that all
>
> Well, I guess that's not really the scenario with this approach. Instead
> they'd run with degraded network performance but could still at least be
> migrated.
Thanks, that's a good summary. And instead of degraded we call it
un-accelerated.
--
MST
next prev parent reply other threads:[~2018-12-05 20:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 14:06 [Qemu-devel] [RFC 0/2] Attempt to implement the standby feature for assigned network devices Sameeh Jubran
2018-10-25 14:06 ` [Qemu-devel] [RFC 1/2] qdev/qbus: Add hidden device support Sameeh Jubran
2018-10-25 14:06 ` [Qemu-devel] [RFC 2/2] virtio-net: Implement VIRTIO_NET_F_STANDBY feature Sameeh Jubran
2018-10-25 18:01 ` [Qemu-devel] [RFC 0/2] Attempt to implement the standby feature for assigned network devices Sameeh Jubran
2018-12-05 16:18 ` Michael Roth
2018-12-05 17:09 ` [Qemu-devel] [libvirt] " Peter Krempa
2018-12-05 17:22 ` Michael S. Tsirkin
2018-12-05 17:26 ` Daniel P. Berrangé
2018-12-05 17:43 ` Daniel P. Berrangé
2018-10-25 22:17 ` [Qemu-devel] " Michael S. Tsirkin
2018-12-05 17:18 ` Daniel P. Berrangé
2018-12-05 17:26 ` Michael S. Tsirkin
2018-12-05 20:24 ` Michael Roth
2018-12-05 20:44 ` Michael Roth
2018-12-05 20:58 ` Michael S. Tsirkin [this message]
2018-12-05 20:57 ` Michael S. Tsirkin
2018-12-06 10:01 ` Daniel P. Berrangé
2018-12-06 10:06 ` Daniel P. Berrangé
2018-12-07 16:36 ` Eduardo Habkost
2018-12-07 16:46 ` Daniel P. Berrangé
2018-12-07 18:26 ` Michael S. Tsirkin
2018-12-07 17:50 ` Roman Kagan
2018-12-07 18:20 ` Michael S. Tsirkin
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=20181205155739-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jasowang@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=sameeh@daynix.com \
--cc=yan@daynix.com \
/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).