DPDK patches and discussions
 help / color / mirror / Atom feed
From: wang.yong19@zte.com.cn
To: dev@dpdk.org
Subject: [dpdk-dev] examples/vhost: how to use vhost-switch between VMs? Anybody who can help?
Date: Tue, 27 Dec 2016 13:33:14 +0800	[thread overview]
Message-ID: <OFD1256FEB.A164AEF1-ON48258096.001DA07F-48258096.001E7E6E@zte.com.cn> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="GB2312", Size: 1677 bytes --]

  There are some descriptions in 
dpdk-16.11\doc\guides\sample_app_ug\vhost.rst,
"The sample application performs simple packet switching between virtual 
machines based on Media Access Control (MAC) address or Virtual Local Area 

Network (VLAN) tag." So, we want to use vhost-switch between two VMs, one 
work as server and another as client.
  We runned the vhost-switch sample in a VM with three virtio ports. 
First, we 
binded one virtio port to igb_uio. Then we runned the command
"./vhost-switch -c f -n 4 --socket-mem 1024 -- --socket-file /tmp/sock0 
¨C-vm2vm 1 ¨C-dequeue-zero-copy"
And then error occured. We found that the 'dev_info.max_vmdq_pools' of the 
virtio
port was 0, and division by zero error occured at the statement 
'queues_per_pool = dev_info.vmdq_queue_num / dev_info.max_vmdq_pools;'
We fixed this by assigning 'queues_per_pool' to 0 if 
'dev_info.max_vmdq_pools'
was 0, but there were still other errors when running vhost-switch. 
  After we fixed all the errors while running vhost-switch as server, we 
didn't
know how to run the vhost-switch as client in another VM, how could the 
client 
get the socket, the netdev and the virtio port that the server 
vhost-switch 
created?
  So, we doubted whether we use the vhost-switch in a wrong way. Could you
please give us some advice that how to use the vhost-switch between two or 
more
 VMs?
  Anybody who can help us with this?

\x16º&Ê槅©åŠébžìbž×¥r‰“¹àÞsnôëŸ9Ûm5é\x17­º¹ÏjØr¹©ájybºX§»\x18§µé\¢d^qè¯y×ë¢i kNâž×¥r‰¦­;Š{^•Ê&×~5ߍwë]4o'ivJ+€ú,µø±Â+a\x11#\x13>'{\f\x106Ø\x1fu~ŠÝz÷ivJ+;žÛ°Þsm5ëN¹ó¾Ó]4\bDÑyÇ¢½ç_®‰¨®É kM9ø§µé\¢mtïm=ãVò¢»&­tæ7âž×¥r‰°ŠØDHÄÏÛ Þsm5ëmyótóM\x17\x13^[K¢ŠuÕr+¢sè®Ð\x15

                 reply	other threads:[~2016-12-27  5:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OFD1256FEB.A164AEF1-ON48258096.001DA07F-48258096.001E7E6E@zte.com.cn \
    --to=wang.yong19@zte.com.cn \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).