From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] patch: allow defining MAC address etc
Date: Sun, 21 Aug 2005 19:03:56 +0200 [thread overview]
Message-ID: <4308B3FC.4000505@bellard.org> (raw)
In-Reply-To: <200508210204.32388.paul@codesourcery.com>
Paul Brook wrote:
> On Sunday 21 August 2005 01:36, jamal wrote:
>
>>This attached patch is intended for allowing automated clever scripting
>>for networking (tuntap only). Please read and apply if possible.
>>
>>It does the following:
>>a) allow for specifying the guest netdevice interface MAC address
>>(in addition to keeping the old functionality of specifying just
>>the first one and letting qemu decide what subsequent ones should be)
>>So now you can say something along the lines of:
>>"-nics 2 -macaddr0 00:11:a:0:2:19 -macaddr1 00:11:a:0:1:19"
>>We allow upto 6 such MAC addresses to be specified. Maybe theres
>>a more clever way to achieve this.
>
>
> Maybe a comma separated list of MAC addresses. e.g.
> "-nics 2 macaddr 00:11:a:0:2:19,00:11:a:0:1:19"
I propose:
-nics 2 -macaddr 00:11:a:0:2:19 -macaddr 00:11:a:0:1:19
For the future, I would like to change the networks options to have
something like:
-net usernet,macaddr=00:11:a:0:2:19 -net tunfd=10,macaddr=00:11:a:0:1:19
to be consistent with the character devices.
Fabrice.
next prev parent reply other threads:[~2005-08-21 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 0:36 [Qemu-devel] patch: allow defining MAC address etc jamal
2005-08-21 1:04 ` Paul Brook
2005-08-21 1:56 ` jamal
2005-08-21 2:22 ` Paul Brook
2005-08-21 2:46 ` jamal
2005-08-21 3:18 ` jamal
2005-08-21 4:30 ` Jim C. Brown
2005-08-21 15:51 ` jamal
2005-08-21 4:06 ` Jim C. Brown
2005-08-21 17:03 ` Fabrice Bellard [this message]
2005-08-26 11:43 ` Henrik Nordstrom
-- strict thread matches above, loose matches on Subject: below --
2005-08-22 1:44 [Qemu-devel] PATCH: " jamal
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=4308B3FC.4000505@bellard.org \
--to=fabrice@bellard.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.