DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev]  Running Qemu manually for vswitch
@ 2014-06-05  1:52 Srikanth Akula
  0 siblings, 0 replies; only message in thread
From: Srikanth Akula @ 2014-06-05  1:52 UTC (permalink / raw)
  To: dev

Hi ,

I am currently working to install & run dpdk vswitch for our custom guest
operating system .

I have followed the steps mentioned in the docs section of the git dpdk-ovs
page.

1. I am trying to run Qemu by building an xml file and creating a domain by
using virsh. But it fails with the following error .

error : virCommandWait:2188 : internal error Child process (LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
/usr/local/bin/qemu-system-x86_64 -help) status unexpected: exit status 1

2. Qemu which is customized for dpdk , is overriding the existing help
strings , which i feel is causing the problems when i use virsh to
build/run guest OS.

Can anybody suggest me the configuration/steps i should use for the
following topology.

                        VM1   < -------> VM2  <-----------> VM3
                            |
                    |
                         -----------------------------------------------
                                                   Host machine
                         ----------------------------------------------
                            |                                |
                            |                                |
                          ixia                           ixia


Thanks & Regards,
Srikanth

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2014-06-05  1:52 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-05  1:52 [dpdk-dev] Running Qemu manually for vswitch Srikanth Akula

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).