From: "Thomas Jung" <Swoop3r@gmx.de>
To: 'Jan Kiszka' <jan.kiszka@siemens.com>,
'Sasha Levin' <levinsasha928@gmail.com>
Cc: 'Anthony Liguori' <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tap: Add optional parameters to up/down script
Date: Thu, 29 Sep 2011 16:40:21 +0200 [thread overview]
Message-ID: <004801cc7eb5$c00c6580$40253080$@de> (raw)
In-Reply-To: <4E847C56.4020701@siemens.com>
On 2011-09-29 16:11 jan kiszka wrote
> What kind of parameters would you want to pass? Something that tells VMs
> apart (which can be solved without these extensions) or more?
>
> Jan
In our Case:
We want to simulate an larger environment with multiple switches realized in
openvswitch.
Openvswitch requires a up- and downscript for each switch. So the idea was,
have a single and variable up- and downscript and feed it with parameters
(like switch to use, vlan id and so on) through the scriptparams.
Greetings
next prev parent reply other threads:[~2011-09-29 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 13:57 [Qemu-devel] [PATCH] tap: Add optional parameters to up/down script Sasha Levin
2011-09-29 14:10 ` Jan Kiszka
2011-09-29 14:40 ` Thomas Jung [this message]
2011-09-29 15:20 ` Jan Kiszka
2011-09-29 15:39 ` Sasha Levin
2011-09-29 14:53 ` Anthony Liguori
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='004801cc7eb5$c00c6580$40253080$@de' \
--to=swoop3r@gmx.de \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=levinsasha928@gmail.com \
--cc=qemu-devel@nongnu.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).