From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E6hAR-0004bd-9j for qemu-devel@nongnu.org; Sun, 21 Aug 2005 00:10:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E6hAG-0004Wm-Pt for qemu-devel@nongnu.org; Sun, 21 Aug 2005 00:10:39 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E6hAF-0004H1-2T for qemu-devel@nongnu.org; Sun, 21 Aug 2005 00:10:31 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E6h6q-0002Wb-RL for qemu-devel@nongnu.org; Sun, 21 Aug 2005 00:07:00 -0400 Date: Sun, 21 Aug 2005 00:06:36 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] patch: allow defining MAC address etc Message-ID: <20050821040636.GA13280@jbrown.mylinuxbox.org> References: <1124584572.6521.38.camel@localhost.localdomain> <200508210204.32388.paul@codesourcery.com> <1124589394.6521.51.camel@localhost.localdomain> <200508210322.36010.paul@codesourcery.com> <1124592406.6521.59.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1124592406.6521.59.camel@localhost.localdomain> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: hadi@cyberus.ca, qemu-devel@nongnu.org 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.