From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N2tpu-0006oZ-Uy
	for qemu-devel@nongnu.org; Tue, 27 Oct 2009 17:44:14 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N2tpq-0006nz-82
	for qemu-devel@nongnu.org; Tue, 27 Oct 2009 17:44:14 -0400
Received: from [199.232.76.173] (port=50146 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N2tpq-0006nw-3U
	for qemu-devel@nongnu.org; Tue, 27 Oct 2009 17:44:10 -0400
Received: from mail-ew0-f206.google.com ([209.85.219.206]:36554)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1N2tpp-00088E-Mz
	for qemu-devel@nongnu.org; Tue, 27 Oct 2009 17:44:09 -0400
Received: by ewy2 with SMTP id 2so174326ewy.34
	for <qemu-devel@nongnu.org>; Tue, 27 Oct 2009 14:44:08 -0700 (PDT)
Message-ID: <4AE769A3.9080205@codemonkey.ws>
Date: Tue, 27 Oct 2009 16:44:03 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] accidental mistyping of command line kills networking
References: <4AE7460D.7050807@us.ibm.com> <4AE761D9.7040401@us.ibm.com>
In-Reply-To: <4AE761D9.7040401@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Beth Kon <eak@us.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>

Beth Kon wrote:
> Beth Kon wrote:
>> I accidentally entered a command line as follows:
>>
>> /usr/bin/qemu-kvm -drive 
>> file=/scratch/images/beth/windows/win2k3_32_R2.dat.10G.img,if=ide -m 
>> 2048 -boot cd -net nic,model=rtl8139 -net tap,script=/etc/qemu-ifup 
>> -vnc :12 -usbdevice tablet -monitor stdio -net nic,model=e1000 -net 
>> tap,script=/etc/qemu-ifup
>>
>> and the machine's networking broke, requiring a network restart to 
>> get it back in order. The second -net tap,script=/etc/qemu-ifup 
>> causes the problem.
>>
>> /var/log/messages shows
>> tap0: received packet with  own address as source address
>>
>> I don't have time at the moment to look into what's going wrong.  
>> Just wanted to make people aware.
>>
>> Beth Kon
> A clarification... this command line is ok. But as it happens, windows 
> datacenter does not have a driver for rtl8139. So somehow, this 
> driverless adapter in windows is effectively causing an "extra" tap 
> device to be specified on the qemu command line, wreaking havoc with 
> the networking on the host.

It's actually not okay.  You're creating a bridge with two tap devices 
on the bridge that happen to be connected in qemu by a vlan.  If one tap 
device receives a packet, qemu is going to forward that packet to the 
other tap device, which will in turn send the packet to the bridge which 
in turn sends it to the first tap device.

Resulting in an infinite networking loop.

Regards,

Anthony Liguori