Hongjun,
VPP only implements the device side for vhost user. You need the driver side.
It looks like you are trying to run vhost user in the host as a device and
vhost user in the container also as a device. They don’t work that way. Both
qemu and dpdk implement driver side that you can use to communicate with VPP on
the device side.
Steven
From: <vpp-dev-boun...@lists.fd.io> on behalf of "Ni, Hongjun"
<hongjun...@intel.com>
Date: Friday, January 12, 2018 at 3:45 AM
To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Cc: "Ramakrishnan, Kuralamudhan" <kuralamudhan.ramakrish...@intel.com>
Subject: [vpp-dev] VPP native vhost-user issue on stable/1710
Hi all,
I am trying to use VPP native vhost-user to communicate between Host and
Containers.
But I met an issue, Could you help to give some advice on it? Thanks a lot.
My setup is as bellows:
Inside Host:
vppctl create vhost socket /tmp/sock0 server
vppctl set int state VirtualEthernet0/0/0 up
Then run docker:
docker run -itd --privileged \
-v /tmp/sock0:/tmp/sock0 \
--name=vpp0 hongjunni/vpp_1710 /bin/bash
docker attach vpp0
Inside docker vpp0:
1). Run VPP:
sudo vpp unix {log /tmp/vpp.log cli-listen /run/vpp/cli.sock} api-trace { on } \
dpdk {coremask 0x2 no-multi-seg } cpu {skip-cores 1}
2). Creat vhost-user client:
vppctl create vhost-user socket /tmp/sock0
vppctl set int state VirtualEthernet0/0/0 up
Here is the issue:
Inside container vpp0:
VirtualEthernet0/0/0’s admin and link status are both up.
Inside Host:
VirtualEthernet0/0/0’s admin status is up, but its link status is down.
Is there any configuration wrong in my setup?
How can I fix this issue?
Thanks a lot,
Hongjun
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
