Hi Stefan,
On Wed, 2 Sep 2015 14:48:57 +0100 Stefan Hajnoczi wrote:
> On Thu, Aug 20, 2015 at 02:45:47AM +0800, Fam Zheng wrote:
> > Looks like the previous patch to fix this fell between the cracks and never
> > made it to qemu.git?
> >
> > http://patchwork.ozlabs.org/patch/489847/
> >
> > Ste
On Thu, Aug 20, 2015 at 02:45:47AM +0800, Fam Zheng wrote:
> On Tue, 08/18 14:25, Shmulik Ladkani wrote:
> > As of a90a7425cf592a3afeff3eaf32f543b83050ee5c 'tap: Drop tap_can_send'
> > vmxnet3 (with tap networking) can no longer receive once device is
> > deactivated.
> > Alas, as the device is ini
On Tue, 08/18 14:25, Shmulik Ladkani wrote:
> As of a90a7425cf592a3afeff3eaf32f543b83050ee5c 'tap: Drop tap_can_send'
> vmxnet3 (with tap networking) can no longer receive once device is
> deactivated.
> Alas, as the device is initially "inactive", this brakes vmxnet3
> receive functionality.
>
>
ACK.
> On Aug 18, 2015, at 04:25 AM, Shmulik Ladkani
> wrote:
>
> As of a90a7425cf592a3afeff3eaf32f543b83050ee5c 'tap: Drop tap_can_send'
> vmxnet3 (with tap networking) can no longer receive once device is
> deactivated.
> Alas, as the device is initially "inactive", this brakes vmxnet3
> rece
As of a90a7425cf592a3afeff3eaf32f543b83050ee5c 'tap: Drop tap_can_send'
vmxnet3 (with tap networking) can no longer receive once device is
deactivated.
Alas, as the device is initially "inactive", this brakes vmxnet3
receive functionality.
vmxnet3_can_receive() checks its internal 'device_active'
