On Thu, 26 Oct 2017 11:06:08 +0800 徐荣杰 <[email protected]> wrote:
> Hi, > > > > I do have the memAccess property as follows for both VM > > <memoryBacking> > <hugepages> > <page size='1048576' unit='KiB' nodeset='0'/> > </hugepages> > </memoryBacking> > > <cpu mode='host-model'> > <model fallback='allow'/> > <topology sockets='2' cores='1' threads='1'/> > <numa> > <cell id='0' cpus='0-1' memory='2097152' unit='KiB' > memAccess='shared'/> > </numa> > </cpu> OK, then look if the socket path is correct. Also if you don't have apparmor/selinux issues. Look at the OVS logs and EAL initialization messages which might give you a hint. The qemu log is also important. Usually the memory isn't shared or something is wrong that the socket is not opened/functional for one side. -- Flavio _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
