qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Beth Kon <eak@us.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] accidental mistyping of command line kills networking
Date: Tue, 27 Oct 2009 16:44:03 -0500	[thread overview]
Message-ID: <4AE769A3.9080205@codemonkey.ws> (raw)
In-Reply-To: <4AE761D9.7040401@us.ibm.com>

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

  reply	other threads:[~2009-10-27 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 19:12 [Qemu-devel] accidental mistyping of command line kills networking Beth Kon
2009-10-27 21:10 ` Beth Kon
2009-10-27 21:44   ` Anthony Liguori [this message]
2009-10-28  6:29     ` Avi Kivity
2009-10-28  8:34       ` Gleb Natapov
2009-10-28  8:55         ` Avi Kivity
2009-10-28  9:07           ` Gleb Natapov

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=4AE769A3.9080205@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=eak@us.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).