From: "Thomas Jung" <Swoop3r@gmx.de>
To: 'Sasha Levin' <levinsasha928@gmail.com>, qemu-devel@nongnu.org
Cc: 'Anthony Liguori' <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] tap: Add optional parameters to up/down script
Date: Thu, 6 Oct 2011 12:11:24 +0200 [thread overview]
Message-ID: <004001cc8410$51663e20$f432ba60$@de> (raw)
In-Reply-To: <1317375921-19336-1-git-send-email-levinsasha928@gmail.com>
On 30.09 2011 11:45, Sasha Levin wrote:
> Subject: [PATCH v2] tap: Add optional parameters to up/down script
>
> This allows the user to add custom parameters to the up or down
> scripts.
>
> Extra parameters are useful in more complex networking scenarios
> where we would like to configure network devices when starting
> or stopping the guest.
PATCH v2 isn't working for me. Neither the scriptparams nor the
downscriptparams.
Usage was like:
qemu-system-x86_64 -m 512 -net nic,macaddr=[...] -net
tap,script=/path/to/script,scriptparams="param1",
downscript=/path/to/downscript -drive.......
Greetings
Thomas
prev parent reply other threads:[~2011-10-06 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 9:45 [Qemu-devel] [PATCH v2] tap: Add optional parameters to up/down script Sasha Levin
2011-10-06 10:11 ` Thomas Jung [this message]
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='004001cc8410$51663e20$f432ba60$@de' \
--to=swoop3r@gmx.de \
--cc=aliguori@us.ibm.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).