On Wed, Oct 06, 2010 at 12:13:35PM -0500, Anthony Liguori wrote:
> On 10/06/2010 11:58 AM, Michael S. Tsirkin wrote:
> >On Wed, Oct 06, 2010 at 11:35:08AM -0500, Anthony Liguori wrote:
> >>On 10/06/2010 11:04 AM, Michael S. Tsirkin wrote:
> >>>With -netdev, virtio devices present offload
> >>>featu
On 10/06/2010 11:58 AM, Michael S. Tsirkin wrote:
On Wed, Oct 06, 2010 at 11:35:08AM -0500, Anthony Liguori wrote:
On 10/06/2010 11:04 AM, Michael S. Tsirkin wrote:
With -netdev, virtio devices present offload
features to guest, depending on the backend used.
Thus, removing host netde
On Wed, Oct 06, 2010 at 11:35:08AM -0500, Anthony Liguori wrote:
> On 10/06/2010 11:04 AM, Michael S. Tsirkin wrote:
> >With -netdev, virtio devices present offload
> >features to guest, depending on the backend used.
> >Thus, removing host netdev peer while guest is
> >active leads to guest-visibl
On 10/06/2010 11:04 AM, Michael S. Tsirkin wrote:
With -netdev, virtio devices present offload
features to guest, depending on the backend used.
Thus, removing host netdev peer while guest is
active leads to guest-visible inconsistency and/or crashes.
As a solution, while guest (NIC) peer device
With -netdev, virtio devices present offload
features to guest, depending on the backend used.
Thus, removing host netdev peer while guest is
active leads to guest-visible inconsistency and/or crashes.
As a solution, while guest (NIC) peer device exists,
we prevent the host peer from being deleted
