From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37853) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VX6bz-000755-9m for qemu-devel@nongnu.org; Fri, 18 Oct 2013 05:45:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VX6bq-0001KV-5w for qemu-devel@nongnu.org; Fri, 18 Oct 2013 05:44:51 -0400 Received: from e23smtp08.au.ibm.com ([202.81.31.141]:42024) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VX6bp-0001Jz-Fg for qemu-devel@nongnu.org; Fri, 18 Oct 2013 05:44:42 -0400 Received: from /spool/local by e23smtp08.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 18 Oct 2013 19:44:34 +1000 Received: from d23relay03.au.ibm.com (d23relay03.au.ibm.com [9.190.235.21]) by d23dlp03.au.ibm.com (Postfix) with ESMTP id 36F173578050 for ; Fri, 18 Oct 2013 20:44:32 +1100 (EST) Received: from d23av02.au.ibm.com (d23av02.au.ibm.com [9.190.235.138]) by d23relay03.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r9I9iJbF60752122 for ; Fri, 18 Oct 2013 20:44:20 +1100 Received: from d23av02.au.ibm.com (localhost [127.0.0.1]) by d23av02.au.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id r9I9iUGT019332 for ; Fri, 18 Oct 2013 20:44:31 +1100 Message-ID: <526102FC.8030709@linux.vnet.ibm.com> Date: Fri, 18 Oct 2013 17:44:28 +0800 From: mike MIME-Version: 1.0 References: <1381810677-4369-1-git-send-email-qiudayu@linux.vnet.ibm.com> <525CCD98.7010707@weilnetz.de> <525D36B1.3050208@redhat.com> <525D4412.2000702@linux.vnet.ibm.com> <20131017123014.GG10774@stefanha-thinkpad.redhat.com> <5260A2D5.5000506@linux.vnet.ibm.com> <20131018090044.GI9292@stefanha-thinkpad.redhat.com> In-Reply-To: <20131018090044.GI9292@stefanha-thinkpad.redhat.com> Content-Type: multipart/alternative; boundary="------------090002080607070303090804" Subject: Re: [Qemu-devel] [PATCH v2] net/net: Change the default mac address of nic List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Stefan Hajnoczi , qemu-devel@nongnu.org, aliguori@amazon.com, Stefan Weil This is a multi-part message in MIME format. --------------090002080607070303090804 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 10/18/2013 05:00 PM, Stefan Hajnoczi wrote: > On Fri, Oct 18, 2013 at 10:54:13AM +0800, mike wrote: >>> NACK >>> >>> I'm not going to merge this patch: >>> >>> If you terminate QEMU and launch it again the NIC gets a different MAC >>> address. Some guest operating systems are sensitive to this - under >> For these users must use -device ,mac=XX:XX:XX:XX:XX:XX. >> I think no body will boot up the guest, which sensitive to this, >> without mac address. >> >> Actually, people use the command line without mac address, mean they mainly >> don't care about mac address, so give them random mac address is reasonable >> I think. >> >> In my opinion, if we fix this, for qemu side no any issue, we both support >> mac address set or unset correctly. >> >> What am I confuse is, *qemu supports mac address unset, why we force >> users must set the address when more than one guests*? >> This is unreasonable. >> >>> many Linux distros the network interfaces names change due to the MAC >>> address change. As a result firewall configuration will break and other >>> services may fail to start because they cannot find the interface. >> Agree, so this mac address should set in qemu command line as >> libvirt does :) >>> If you have multiple guests or want control over the MAC address, set it >>> explicitly using -device ,mac=XX:XX:XX:XX:XX:XX. >> Currently, especially for developers, people mainly use qemu >> command line directly, and as qemu supports mac address >> unset, they may try the simplest command line to boot up >> lots of guests, they will confuse about why all this guest use >> the same mac address. > Your argument is weak: *you* want to avoid specifying the MAC address so > in exchange you want to *break* existing configurations and force other > people to start specifying a MAC address. OK, I do not want to break the existing configurations. I'm fine if you do not want to merge this patch. But I think this should be an issue of qemu, and need to do something on it, so I make this patch. Can we try other solutions to solve this issue? (if you agree this should be an issue) Also this potential issue can happens if the user set the same mac address with more than one guest on one host. Can we avoid this ? Thanks Mike > This doesn't improve anything, it will just annoy users and cause bug > reports. > > Sorry that there isn't a solution that satisfies everyone, you'll have > to add a MAC address to your command-line. > > Stefan > > > --------------090002080607070303090804 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 10/18/2013 05:00 PM, Stefan Hajnoczi wrote:
On Fri, Oct 18, 2013 at 10:54:13AM +0800, mike wrote:
NACK

I'm not going to merge this patch:

If you terminate QEMU and launch it again the NIC gets a different MAC
address.  Some guest operating systems are sensitive to this - under
For these users must use -device <nic-model>,mac=XX:XX:XX:XX:XX:XX.
I think no body will boot up the guest, which sensitive to this,
without mac address.

Actually, people use the command line without mac address, mean they mainly
don't care about mac address, so give them random mac address is reasonable
I think.

In my opinion, if we fix this, for qemu side no any issue, we both support
mac address set or unset correctly.

What am I confuse is, *qemu supports mac address unset, why we force
users must set the address when more than one guests*?
This is unreasonable.

many Linux distros the network interfaces names change due to the MAC
address change.  As a result firewall configuration will break and other
services may fail to start because they cannot find the interface.
Agree, so this mac address should set in qemu command line as
libvirt does :)
If you have multiple guests or want control over the MAC address, set it
explicitly using -device <nic-model>,mac=XX:XX:XX:XX:XX:XX.
Currently, especially for developers, people mainly use qemu
command line directly, and as qemu supports mac address
unset, they may try the simplest command line to boot up
lots of guests, they will confuse about why all this guest use
the same mac address.
Your argument is weak: *you* want to avoid specifying the MAC address so
in exchange you want to *break* existing configurations and force other
people to start specifying a MAC address.
OK, I do not want to break the existing configurations.

I'm fine if you do not want to merge this patch.

But I think this should be an issue of qemu, and need to
do something on it, so I make this patch.

Can we try other solutions to solve this issue?
(if you agree this should be an issue)

Also this potential issue can happens if the user set the same mac address
with more than one guest on one host.

Can we avoid this ?

Thanks
Mike
This doesn't improve anything, it will just annoy users and cause bug
reports.

Sorry that there isn't a solution that satisfies everyone, you'll have
to add a MAC address to your command-line.

Stefan




--------------090002080607070303090804--