I'm looking over the history of this particular bug, and there at least
3 or 4 different bugs represented here. We should have been stricter
from the start about filing separate bugs.
@Billy Charlton
Can you tell us whether you are still having a problem? Yours appears
likely to be a bug in the bridge driver, so if you are, then I'd like
to have you test the pre-preposed kernel packages from https://launchpad.net/~kernel-ppa/+archive/pre-proposed).
@Andrew
thanks for testing. I'd like to try a few things, but I need your bug
kept separate from the others. Can you please file a *new* bug (refuse
any suggestions at duplicates for now)? Please re-attach your
/etc/network/interfaces, output of 'iptabes -L' and 'netstat -nr',
'brctl show', 'ifconfig -a' (with a VM up), 'qemu --version', 'libvirtd
--version', 'uname -a', the contents of /etc/libvirt/qemu/network/*, and
the xml of a sample VM that fails? If any VM does not lose
connectivity, then include that too, but I don't think any is. (I
have specific questions I had started to write out, but will reserve them
for the new bug) I really am eager to look into this one, but need
the information segragated. Thanks!
@angriukas
Near as I can tell, the fix I've committed is actually for *your* bug
(which is still separate from Frank's, Billy's, Andrew's, and Santi's).
Ideally you would (a) open a new bug, specify that you lose connectivity
on guest shutdown, and comment on whether the proposed fix works for
you.
(Note to self - I suspect Jurgen's is the same as Frank's)
The status of THIS bug is to be set only based on feedback from Billy.
Setting to incomplete for now.
I'm looking over the history of this particular bug, and there at least
3 or 4 different bugs represented here. We should have been stricter
from the start about filing separate bugs.
@Billy Charlton
Can you tell us whether you are still having a problem? Yours appears /launchpad. net/~kernel- ppa/+archive/ pre-proposed).
likely to be a bug in the bridge driver, so if you are, then I'd like
to have you test the pre-preposed kernel packages from
https:/
@Andrew
thanks for testing. I'd like to try a few things, but I need your bug interfaces, output of 'iptabes -L' and 'netstat -nr', qemu/network/ *, and
kept separate from the others. Can you please file a *new* bug (refuse
any suggestions at duplicates for now)? Please re-attach your
/etc/network/
'brctl show', 'ifconfig -a' (with a VM up), 'qemu --version', 'libvirtd
--version', 'uname -a', the contents of /etc/libvirt/
the xml of a sample VM that fails? If any VM does not lose
connectivity, then include that too, but I don't think any is. (I
have specific questions I had started to write out, but will reserve them
for the new bug) I really am eager to look into this one, but need
the information segragated. Thanks!
@angriukas
Near as I can tell, the fix I've committed is actually for *your* bug
(which is still separate from Frank's, Billy's, Andrew's, and Santi's).
Ideally you would (a) open a new bug, specify that you lose connectivity
on guest shutdown, and comment on whether the proposed fix works for
you.
(Note to self - I suspect Jurgen's is the same as Frank's)
The status of THIS bug is to be set only based on feedback from Billy.
Setting to incomplete for now.