With -netdev, virtio devices present offload
features to guest, depending on the backend used.
Thus, removing host ntedev peer while guest is
active leads to guest-visible inconsistency and/or crashes.
See e.g. https://bugzilla.redhat.com/show_bug.cgi?id=623735
As a solution, while guest (NIC)
On 09/20/2010 11:30 AM, Michael S. Tsirkin wrote:
With -netdev, virtio devices present offload
features to guest, depending on the backend used.
Thus, removing host ntedev peer while guest is
active leads to guest-visible inconsistency and/or crashes.
See e.g.
On Mon, Sep 20, 2010 at 11:41:45AM -0500, Anthony Liguori wrote:
On 09/20/2010 11:30 AM, Michael S. Tsirkin wrote:
With -netdev, virtio devices present offload
features to guest, depending on the backend used.
Thus, removing host ntedev peer while guest is
active leads to guest-visible
On 09/20/2010 11:47 AM, Michael S. Tsirkin wrote:
On Mon, Sep 20, 2010 at 11:41:45AM -0500, Anthony Liguori wrote:
On 09/20/2010 11:30 AM, Michael S. Tsirkin wrote:
With -netdev, virtio devices present offload
features to guest, depending on the backend used.
Thus, removing host
On Mon, Sep 20, 2010 at 11:56:56AM -0500, Anthony Liguori wrote:
On 09/20/2010 11:47 AM, Michael S. Tsirkin wrote:
On Mon, Sep 20, 2010 at 11:41:45AM -0500, Anthony Liguori wrote:
On 09/20/2010 11:30 AM, Michael S. Tsirkin wrote:
With -netdev, virtio devices present offload
features to guest,
On 09/20/2010 12:14 PM, Michael S. Tsirkin wrote:
On Mon, Sep 20, 2010 at 11:56:56AM -0500, Anthony Liguori wrote:
On 09/20/2010 11:47 AM, Michael S. Tsirkin wrote:
On Mon, Sep 20, 2010 at 11:41:45AM -0500, Anthony Liguori wrote:
On 09/20/2010 11:30 AM, Michael S. Tsirkin
On 09/20/2010 01:14 PM, Anthony Liguori wrote:
Here's what makes sense to me:
1) async device remove + poll device status/removal notification +
remove backend
The management tool needs to determine when the device is gone and
remove the backend.
2) sync device remove + remove backend
