[dpdk-dev] [RFC 0/5] virtio support for container

[Tan, Jianfeng]

Hi Fedin,

First of all, when you say openvswitch, are you referring to ovs-dpdk?

And can you detail your test case? Like, how do you want ovs_on_host and ovs_in_container to be connected?
Through two-direct-connected physical NICs, or one vhost port in ovs_on_host and one virtio port in ovs_in_container?

Thanks,
Jianfeng

> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pavel Fedin
> Sent: Wednesday, December 30, 2015 5:47 PM
> To: dev at dpdk.org
> Subject: Re: [dpdk-dev] [RFC 0/5] virtio support for container
> 
>  Hello everybody!
> 
>  I am currently working on improved version of this patchset, and i am testing
> it with openvswitch. I run two openvswitch instances:
> on host and in container. Both ovs instances forward packets between its
> LOCAL port and vhost/virtio port. This way i can
> comfortably run PING between my host and container.
>  The problem is that the patchset seems to be broken somehow. ovs-
> vswitchd fails to open dpdk0 device, and if i set --log-level=9
> for DPDK, i see this in the console:
> --- cut ---
> Broadcast message from systemd-journald at localhost.localdomain (Wed
> 2015-12-30 11:13:00 MSK):
> 
> ovs-vswitchd[557]: EAL: TSC frequency is ~3400032 KHz
> 
> 
> Broadcast message from systemd-journald at localhost.localdomain (Wed
> 2015-12-30 11:13:00 MSK):
> 
> ovs-vswitchd[560]: EAL: memzone_reserve_aligned_thread_unsafe():
> memzone <RG_MP_ovs_mp_1500_0_262144> already exists
> 
> 
> Broadcast message from systemd-journald at localhost.localdomain (Wed
> 2015-12-30 11:13:00 MSK):
> 
> ovs-vswitchd[560]: RING: Cannot reserve memory
> --- cut ---
> 
>  How can i debug this?
> 
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
> 
>