Bug#525588: bridged network stop working with kvm 84
Le 5739 Septembre 1993, Paul Collins a envoyé: It works fine again here with kvm-85. Works here too on amd64 host. Thanks. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
Daniel Dehennin daniel.dehen...@baby-gnu.org writes: Le 5717 Septembre 1993, Paul Collins a envoyé: I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. One one host system I use a bridge and on the other a private network with NAT, so it seems to be a more general problem. Switching my VMs to use emulated hardware NICs instead of virtio worked around the problem. I test with 2.6.28.1: - on both host and guest - only on host, - only on guest With kvm 72-dfsg-5 it's ok, with kvm-84 it does not work. It works fine again here with kvm-85. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
Le 5717 Septembre 1993, Paul Collins a envoyé: I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. One one host system I use a bridge and on the other a private network with NAT, so it seems to be a more general problem. Switching my VMs to use emulated hardware NICs instead of virtio worked around the problem. I test with 2.6.28.1: - on both host and guest - only on host, - only on guest With kvm 72-dfsg-5 it's ok, with kvm-84 it does not work. Regards -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1 pgp5pTprkvUnn.pgp Description: PGP signature
Bug#525588: bridged network stop working with kvm 84
Hi Paul, this answers most of my questions I was just about to ask ;) On Mon, Apr 27, 2009 at 10:50:09AM +1200, Paul Collins wrote: I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. But you do use the kvm-84 modules or are you using the in kernel kvm modules? One one host system I use a bridge and on the other a private network with NAT, so it seems to be a more general problem. Good to now. Switching my VMs to use emulated hardware NICs instead of virtio worked around the problem. Suspected that from googling around, thanks for the heads up! Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
Guido Günther a...@sigxcpu.org writes: On Mon, Apr 27, 2009 at 10:50:09AM +1200, Paul Collins wrote: I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. But you do use the kvm-84 modules or are you using the in kernel kvm modules? I use the kernel's kvm modules. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
Le 5717 Septembre 1993, Paul Collins a envoyé: I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. Interesting, 2.6.29.1 with kvm 72+dfsg-5 works fine with the in kernel kvm module. One one host system I use a bridge and on the other a private network with NAT, so it seems to be a more general problem. I have a default libvirt setup, an internal bridge (192.168.122.0/24) and everything is masqueraded when outputed on eth0. Switching my VMs to use emulated hardware NICs instead of virtio worked around the problem. I'll try to give it a try, need to build a new kernel with some nic hardware support ;-) Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
On Sat, Apr 25, 2009 at 09:16:42PM +0200, Daniel Dehennin wrote: [ 1402.084830] device nfs entered promiscuous mode [ 1402.085292] virbr0: topology change detected, propagating [ 1402.085294] virbr0: port 1(nfs) entering forwarding state [ 1402.119980] kvm: 5000: cpu0 unhandled wrmsr: 0xc0010117 data 0 [ 1402.129303] kvm: 5000: cpu0 unhandled rdmsr: 0xc0010117 [ 1402.129325] kvm: 5000: cpu0 unhandled rdmsr: 0xc0010117 [ 1410.090645] bad partial csum: csum=21586/20992 len=80 [ 1411.546680] bad partial csum: csum=21586/20992 len=60 [ 1413.023197] nfs: no IPv6 routers present [ 1414.918662] bad partial csum: csum=21586/20992 len=80 [ 1415.546653] bad partial csum: csum=21586/20992 len=60 [ 1419.546659] bad partial csum: csum=21586/20992 len=60 --8---cut here---end---8--- Could you try to turn of checksuming using ethtool? -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
Le 5716 Septembre 1993, Guido Günther a envoyé: On Sat, Apr 25, 2009 at 09:16:42PM +0200, Daniel Dehennin wrote: [ 1402.084830] device nfs entered promiscuous mode [ 1402.085292] virbr0: topology change detected, propagating [ 1402.085294] virbr0: port 1(nfs) entering forwarding state [ 1402.119980] kvm: 5000: cpu0 unhandled wrmsr: 0xc0010117 data 0 [ 1402.129303] kvm: 5000: cpu0 unhandled rdmsr: 0xc0010117 [ 1402.129325] kvm: 5000: cpu0 unhandled rdmsr: 0xc0010117 [ 1410.090645] bad partial csum: csum=21586/20992 len=80 [ 1411.546680] bad partial csum: csum=21586/20992 len=60 [ 1413.023197] nfs: no IPv6 routers present [ 1414.918662] bad partial csum: csum=21586/20992 len=80 [ 1415.546653] bad partial csum: csum=21586/20992 len=60 [ 1419.546659] bad partial csum: csum=21586/20992 len=60 --8---cut here---end---8--- Could you try to turn of checksuming using ethtool? This does not work. --8---cut here---start-8--- r...@host: ~# ethtool --set-ring virbr0 rx off Cannot get device ring settings: Operation not supported r...@host: ~# ethtool --set-ring virbr0 tx off Cannot get device ring settings: Operation not supported r...@host: ~# ethtool --set-ring nfs tx off Cannot get device ring settings: Operation not supported r...@host: ~# ethtool --set-ring nfs rx off Cannot get device ring settings: Operation not supported --8---cut here---end---8--- Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. One one host system I use a bridge and on the other a private network with NAT, so it seems to be a more general problem. Switching my VMs to use emulated hardware NICs instead of virtio worked around the problem. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
Package: kvm Version: 84+dfsg-2 Severity: normal Hello, Testing kvm84 from experimental (I use libvirt) I have problems with my bridged network. With kvm 72+dfsg-5 everything is fine, I can ping host from the guest and vice-versa. Just upgrading kvm to version 84 makes it not working: --8---cut here---start-8--- d...@host: ~$ dmesg [...] [ 1402.084830] device nfs entered promiscuous mode [ 1402.085292] virbr0: topology change detected, propagating [ 1402.085294] virbr0: port 1(nfs) entering forwarding state [ 1402.119980] kvm: 5000: cpu0 unhandled wrmsr: 0xc0010117 data 0 [ 1402.129303] kvm: 5000: cpu0 unhandled rdmsr: 0xc0010117 [ 1402.129325] kvm: 5000: cpu0 unhandled rdmsr: 0xc0010117 [ 1410.090645] bad partial csum: csum=21586/20992 len=80 [ 1411.546680] bad partial csum: csum=21586/20992 len=60 [ 1413.023197] nfs: no IPv6 routers present [ 1414.918662] bad partial csum: csum=21586/20992 len=80 [ 1415.546653] bad partial csum: csum=21586/20992 len=60 [ 1419.546659] bad partial csum: csum=21586/20992 len=60 --8---cut here---end---8--- When I ping the guest from the host here is what tcpdump in the guest show: --8---cut here---start-8--- 21:10:50.660488 00:00:00:00:ff:ff (oui Ethernet) 00:00:00:00:00:00 (oui Ethernet), ethertype Unknown (0x), length 52: 0x: 063a 33fc 73d6 0806 0001 0800 0604 ...:3.s. 0x0010: 0001 063a 33fc 73d6 c0a8 7a01 ...:3.s...z. 0x0020: c0a8 7a04 z. --8---cut here---end---8--- Some informations: --8---cut here---start-8--- d...@host: ~$ ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1b:fc:d8:2c:02 brd ff:ff:ff:ff:ff:ff inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0 inet6 fe80::21b:fcff:fed8:2c02/64 scope link valid_lft forever preferred_lft forever 3: virbr0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fe:83:cb:6b:81:ea brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 inet6 fe80::a42a:c0ff:fe25:b1b0/64 scope link valid_lft forever preferred_lft forever 10: nfs: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500 link/ether fe:83:cb:6b:81:ea brd ff:ff:ff:ff:ff:ff inet6 fe80::fc83:cbff:fe6b:81ea/64 scope link valid_lft forever preferred_lft forever --8---cut here---end---8--- --8---cut here---start-8--- d...@guest: ~$ ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 52:54:00:52:a5:e0 brd ff:ff:ff:ff:ff:ff inet 192.168.122.4/24 brd 192.168.122.255 scope global eth0 inet6 fe80::5054:ff:fe52:a5e0/64 scope link valid_lft forever preferred_lft forever --8---cut here---end---8--- Regards. -- Package-specific info: selected information from lshal(1): /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping: 11 cpu MHz : 2664.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 5345.80 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping: 11 cpu MHz : 2664.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid
