Hi, all:
The patch which is used to fix the Qemu bug has been accepted in qemu
community.
http://patchwork.ozlabs.org/patch/760118/
Thanks
Zhiyong
> -Original Message-
> From: Yuanhan Liu [mailto:yuanhan@linux.intel.com]
> Sent: Friday, April 28, 2017 12:29 PM
> To: Maxime C
On Thu, Apr 27, 2017 at 12:00:52PM +0200, Maxime Coquelin wrote:
>
>
> On 04/27/2017 11:41 AM, Zhiyong Yang wrote:
> > vhost since dpdk17.02 + qemu2.7 and above will cause failures of
> >new connection when negotiating to set MQ. (one queue pair works
> >well).
> >Because there exist some b
On 04/27/2017 11:41 AM, Zhiyong Yang wrote:
vhost since dpdk17.02 + qemu2.7 and above will cause failures of
new connection when negotiating to set MQ. (one queue pair works
well).
Because there exist some bugs in qemu code when introducing
VHOST_USER_PROTOCOL_F_REPLY_ACK to qemu. when d
vhost since dpdk17.02 + qemu2.7 and above will cause failures of
new connection when negotiating to set MQ. (one queue pair works
well).
Because there exist some bugs in qemu code when introducing
VHOST_USER_PROTOCOL_F_REPLY_ACK to qemu. when dealing with the vhost
message VHOST_USER_SET_MEM_T
4 matches
Mail list logo