From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E6gGx-0005TR-3m for qemu-devel@nongnu.org; Sat, 20 Aug 2005 23:13:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E6gGv-0005Su-Ly for qemu-devel@nongnu.org; Sat, 20 Aug 2005 23:13:22 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E6gEZ-0004Q7-HN for qemu-devel@nongnu.org; Sat, 20 Aug 2005 23:10:55 -0400 Received: from [209.197.145.106] (helo=mx03.cybersurf.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1E6frY-0007VQ-C3 for qemu-devel@nongnu.org; Sat, 20 Aug 2005 22:47:08 -0400 Received: from mail.cyberus.ca ([209.197.145.21]) by mx03.cybersurf.com with esmtp (Exim 4.30) id 1E6frN-0003Ql-DF for qemu-devel@nongnu.org; Sat, 20 Aug 2005 22:46:57 -0400 Subject: Re: [Qemu-devel] patch: allow defining MAC address etc From: jamal In-Reply-To: <200508210322.36010.paul@codesourcery.com> References: <1124584572.6521.38.camel@localhost.localdomain> <200508210204.32388.paul@codesourcery.com> <1124589394.6521.51.camel@localhost.localdomain> <200508210322.36010.paul@codesourcery.com> Content-Type: text/plain Date: Sat, 20 Aug 2005 22:46:46 -0400 Message-Id: <1124592406.6521.59.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: hadi@cyberus.ca, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org On Sun, 2005-21-08 at 03:22 +0100, Paul Brook wrote: > On Sunday 21 August 2005 02:56, jamal wrote: > > i could do this; macaddr is already being used to imply the start > > macaddr. Does macaddrs sound better? > > Part of the reason I suggested this was because it is an extension of the > existing option. A user can either specifies a single address and have qemu > assign sequential addresses (the current behaviour), or they can specify a > list of addresses, one for each NIC. > it may be easier parsing to avoid having optional fields. Is there any other parameter that has optional fields? > 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. Note the Ids syntax would also be comma separated. cheers, jamal