Bug#525588: bridged network stop working with kvm 84

2009-05-29 Thread Daniel Dehennin
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

Bug#525588: bridged network stop working with kvm 84

2009-05-19 Thread Paul Collins
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

Bug#525588: bridged network stop working with kvm 84

2009-05-01 Thread Daniel Dehennin
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

Bug#525588: bridged network stop working with kvm 84

2009-04-27 Thread Guido Günther
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

Bug#525588: bridged network stop working with kvm 84

2009-04-27 Thread Paul Collins
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

Bug#525588: bridged network stop working with kvm 84

2009-04-27 Thread Daniel Dehennin
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

Bug#525588: bridged network stop working with kvm 84

2009-04-26 Thread Guido Günther
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:

Bug#525588: bridged network stop working with kvm 84

2009-04-26 Thread Daniel Dehennin
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 [

Bug#525588: bridged network stop working with kvm 84

2009-04-26 Thread Paul Collins
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

Bug#525588: bridged network stop working with kvm 84

2009-04-25 Thread Daniel Dehennin
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: