[Qemu-devel] [Bug 590552] [NEW] New default network card doesn't work with tap networking

[Gabriele Tozzi]

Public bug reported:

Unfortunately, I can provide very little information.

Hope this will be useful anyway.

I've upgraded qemu using debian apt to lastest unstable (QEMU PC
emulator version 0.12.4 (Debian 0.12.4+dfsg-2), Copyright (c) 2003-2008
Fabrice Bellard): looks like at some point the default network card for
-net nic option was switched to intel gigabit instead of the good old
ne2k_pci.

I was using -net tap -net nic options and my network stopped working.
When not working,
- tcpdump on the host shows me taht all packets are sent and received fine from 
guest
- tcpdump on guest shows that packets from host are NOT received

obviously, both host tap interface and guest eth0 interfaces, routing
tables, dns, firewall, etc... are well configured.

Having banged my head for a while, I finally stopped the host and
started it again using -net nic,model=ne2k_pci option, then my network
magically started working again.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
New default network card doesn't work with tap networking
https://bugs.launchpad.net/bugs/590552
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
Unfortunately, I can provide very little information.

Hope this will be useful anyway.

I've upgraded qemu using debian apt to lastest unstable (QEMU PC emulator 
version 0.12.4 (Debian 0.12.4+dfsg-2), Copyright (c) 2003-2008 Fabrice 
Bellard): looks like at some point the default network card for -net nic option 
was switched to intel gigabit instead of the good old ne2k_pci.

I was using -net tap -net nic options and my network stopped working.
When not working,
- tcpdump on the host shows me taht all packets are sent and received fine from 
guest
- tcpdump on guest shows that packets from host are NOT received

obviously, both host tap interface and guest eth0 interfaces, routing tables, 
dns, firewall, etc... are well configured.

Having banged my head for a while, I finally stopped the host and started it 
again using -net nic,model=ne2k_pci option, then my network magically started 
working again.