From: Srikanth Akula <srikanth044@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Running Qemu manually for vswitch
Date: Wed, 4 Jun 2014 18:52:43 -0700 [thread overview]
Message-ID: <CA+8eA5nkAViSKqSZ=HtbeF9O+fs1xrOVUaCmOC6__-8z5Me1EQ@mail.gmail.com> (raw)
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
reply other threads:[~2014-06-05 1:52 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='CA+8eA5nkAViSKqSZ=HtbeF9O+fs1xrOVUaCmOC6__-8z5Me1EQ@mail.gmail.com' \
--to=srikanth044@gmail.com \
--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).