Bugs item #2817367, was opened at 2009-07-06 07:33 Message generated for change (Comment added) made by djgera You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2817367&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Luigi Salvatore Elton Palese (quadword) Assigned to: Nobody/Anonymous (nobody) Summary: Network doesn't work anymore switching from kvm-86 to kvm-87 Initial Comment: After switching from kvm-86 to kvm-87 network interface doesn't work anymore. KVM is running on 2.6.28-13-server ubuntu jauty on 32-bit arch and guest WinXp 32-bit and network driver either rtl8139 or e1000. I have a dhcp server and I see DHCP Request from Guest OS to reach DHCP server, I see the DHCP Reply packet on the physical interface and the bridge, but I don't see it on the virtual device (tap). The same with arp packets, arping some address in my network from within Guest OS. I can see arp request but the arp reply doesn't reach Guest OS. With kvm-86 all works ok. ---------------------------------------------------------------------- Comment By: Gerardo Exequiel Pozzi (djgera) Date: 2009-07-07 02:59 Message: Yes kvm-87 don't work. kvm-86 works fine. My config is with kernel 2.6.30.1 (Both host and guest are Arch Linux ) in AMD 64 machine running in 32 bits mode My network setup is tap0 interface in bridge with eth0 via br0. brctl showmacs br0 in host shows activity in the mac addr from guest, but no network. Tried with 8139, ne2k_pci, both have the same issue. Network with -net user works fine, also with socket. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2817367&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
