Re: [dpdk-dev] [PATCH v4 0/4] Vhost: fix mq=on but VIRTIO_NET_F_MQ not negotiated

e_vhost/vhost.c | 22 -- > lib/librte_vhost/vhost.h | 3 +++ > lib/librte_vhost/vhost_user.c | 39 +-- > 3 files changed, 52 insertions(+), 12 deletions(-) Tested v4 with iPXE and confirming that it still works fine. Tested-by: Ladi Prosek Thank you! Ladi

Re: [dpdk-dev] [PATCH v3 0/4] Vhost: fix mq=on but VIRTIO_NET_F_MQ not negotiated

ions(-) I have verified that it fixes iPXE and that a full-featured virtio-net driver successfully takes over the device using all queues. Haven't tested OVMF but it should be safe to assume that it's fixed as well. Tested-by: Ladi Prosek Thank you! Ladi

Re: [dpdk-dev] [PATCH 0/4] Vhost: fix mq=on but VIRTIO_NET_F_MQ not negotiated

On Mon, Dec 4, 2017 at 3:08 PM, Maxime Coquelin wrote: > Having QEMU started with mq=on but guest driver not negotiating > VIRTIO_NET_F_MQ feature ends up in the vhost device to never > start. Indeed, more queues are created in the vhost backend than > configured. > > Guest drivers known to not ad

Re: [dpdk-dev] [PATCH 1/4] vhost: prevent features to be changed while device is running

On Mon, Dec 4, 2017 at 3:08 PM, Maxime Coquelin wrote: > As section 2.2 of the Virtio spec states about features > negotiation: > "During device initialization, the driver reads this and tells > the device the subset that it accepts. The only way to > renegotiate is to reset the device." > > This