From: "Jim C. Brown" <jma5@umd.edu>
To: hadi@cyberus.ca, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] patch: allow defining MAC address etc
Date: Sun, 21 Aug 2005 00:06:36 -0400 [thread overview]
Message-ID: <20050821040636.GA13280@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1124592406.6521.59.camel@localhost.localdomain>
On Sat, Aug 20, 2005 at 10:46:46PM -0400, jamal wrote:
> > Your script should be able to get all the information it needs from the MAC
> > address. You can either hardcode addresses or do pattern matching.
> > The guest MAC address is arbitrary, so you can choose whatever numbering is
> > convenient. For example you could use the last digit of the address to
> > encode your ID field.
>
> The only problem is that would tie the two things (MAC + ID) together.
> i.e it would not be possible to just pass the ids without specifying
> macs.
>
As it should be. A macaddr identified each NIC in the virtual computer uniquely.
Both within the guest and across guests (if you are running multiple qemu VMs
with tuntap networking).
A discussion on IRC before lead to the idea that, if a script should handle
multiple guests, qemu should pass the macaddr in $2 to allow the script to
identify the guest NIC. That is the only thing needed to uniquely identify
a guest, there should be no need for a separate ID.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-08-21 4:10 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 [this message]
2005-08-21 17:03 ` Fabrice Bellard
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=20050821040636.GA13280@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=hadi@cyberus.ca \
--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.