I'm seeing very similar behavior to the OP on 14.04.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/633392
Title:
Bridged Guests los
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/633392
Ti
** Changed in: linux (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/633392
Title:
Bridged Guests losing network connectivity
To ma
@Serge:
New bug posted:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/728519
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/633392
Title:
Bridged Guests losing network connectivity
--
ubunt
Serge,
We've since moved on to Proxmox, but here's the description:
eth0 was the external interface, connected to an interface on an OpenBSD
firewall (with a switch in between).
eth1 was the bridged interface, connected directly to a separate
interface on the firewall with a crossover cable.
@Andrew,
Could you describe the network which sits (or sat) behind eth0 and eth1?
Both basic topology (I assume eth1 was on a private network separate
from eth1?) and hardware and any possible settings?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Quoting Jesse Newland (je...@jnewland.com):
> without a fix. Please let me know if I should file a new bug, or if any
Hi,
please do file a new bug. Please include the following information for
all hosts before upgrade, after upgrade, and after a reinstall:
Detailed steps followed when you updat
We're also seeing interfaces dropping after upgrading bridged 8.10
guests to 10.04 on the same Xen host (Centos 5.5). This is the most
similar bug report I can find at the moment, so I'm describing our
experiences here.
Our guests have two interfaces on the guest connected to the same bridge
on th
One correction on our setup -- our guests are 10.04 LTS (Lucid), not
9.04. Hosts are, indeed 10.10 Maverick.
--
Bridged Guests losing network connectivity
https://bugs.launchpad.net/bugs/633392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
One other salient point to our bug report above... we had two hosts with
the exact same setup described above. Guests on *both* hosts lost
networking within a few hours of each other. Hosts also retained full
network access to both public & other devices on private during whole
guest outage (which
I believe we've hit the same issue as others above.
System:
Host - 10.10 ubuntu running the "2.6.35-22-server" kernel
Guest(s) - 9.4 ubuntu running "2.6.32-25-server" kernel
virsh version:
Compiled against library: libvir 0.8.3
Using library: libvir 0.8.3
Using API: QEMU 0.8.3
Running hypervisor:
@Serge: New deb works. Guests start nicely again. Doesn't fix the
problem though.
With regards to the newer kernel, it also doesn't fix the problem for
me.
I've used parts of the test you linked to in comment #6 and can confirm
this is completely reproducible in the host without any guests runnin
Quoting Tais Plougmann Hansen (633...@bugs.launchpad.net):
> @Serge May have something to do with /usr/lib/libvirt/virt-aa-helper
> missing?
Thanks for noticing that. I don't know why I had to copy that over manually,
but I did. The updated .deb has it.
--
Bridged Guests losing network connect
@Tais: Gah, I'll have to look into it, thanks. As for my request to try the
dailies, I was
once again confusing bugs, and forgot that this bug is actually a kernel bug.
(If you
suspect yours is actually due to libvirt/qemu, then that'll require a new bug,
but I don't
think you do - you just m
@Serge May have something to do with /usr/lib/libvirt/virt-aa-helper
missing?
Nov 16 20:42:32 kvm8 libvirtd: 20:42:32.563: error : qemudReadLogOutput:2164 :
internal error Process exited while reading console log output: libvir:
Security Labeling error : internal error error calling aa_change_pr
@Andrew I tend to avoid bridging physical interfaces. My current setup
used to work (Ubuntu Lucid, Gentoo etc).
@Serge Tried upgrading the packages and now I can't start the guest:
error: Failed to start domain osddev1
error: internal error Process exited while reading console log output: libvir:
@Tais,
If you could try to reproduce with the daily builds, then we can confirm
whether this
is still present in upstream. They are at:
https://launchpad.net/~ubuntu-server-edgers/+archive/server-edgers-qemu-kvm
and
https://launchpad.net/~ubuntu-server-edgers/+archive/server-edgers-libvirt
--
Tais -- we had similar problems to what you describe when trying to
share a bonded channel between a host and 1+ guests. Random delays, lost
packets, nasty low-level things like MAC addresses appearing for the
wrong machine in other hosts' ARP tables.
In the end, we only made it work properly by u
I can now reproduce the behavior on demand.
I'll try to explain my setup:
A: Router.
B: KVM guest on a Maverick Host.
C: Other Host.
A, B and C are all in the same subnet. I boot B and ssh from outside to
B.
While in B I ping C. C initially doesn't respond and the arp cache shows
C as failed. A
My setup (Ubuntu Maverick 10.10, kernel 2.6.35-22-server) is this:
- eth0, eth1 bonded as bond0, active-backup.
- vlan1000 on top of bond0 as bond0.1000.
- br1000 bridge with bond0.1000 as interface.
- vnet0 guest in br1000 bridge as well.
Looking at arp traffic outside and inside the guest:
br1
Hi!
I have the same problem with a Ubuntu 10.04 LTS server currently. I have a
minimum install of lucid on the physical machine with kvm and the network
interface is a bridge. All machines were set up using virt-manager. From time
to time the network connection to the machines gets lost. No pin
Leann,
I have the following in dmesg, but I believe all came before the ssh
sessions were established and failed:
[ 235.700268] lo: Disabled Privacy Extensions
[ 254.123755] ADDRCONF(NETDEV_UP): veth0: link is not ready
[ 268.992077] device veth0 entered promiscuous mode
[ 268.992104] br0: ne
Hi Andrew,
Just curious if any interesting error messages (a kernel oops for ex)
show up in dmesg output after the ssh session fails?
--
Bridged Guests losing network connectivity
https://bugs.launchpad.net/bugs/633392
You received this bug notification because you are a member of Ubuntu
Bugs, w
Leann,
Still no luck, the exact same issue persists. When I SSH into the
server, invoking a loop that echos "test" onto the screen, eventually
the SSH session breaks:
Write failed: Broken pipe
I can SSH right back into the IP, but the session will always fail
eventually. I can't keep an SSH ses
Leann,
I'm testing the kernel you suggested with the bridging setup described
by Serge in comment #6
I'll let you know what the results are.
--
Bridged Guests losing network connectivity
https://bugs.launchpad.net/bugs/633392
You received this bug notification because you are a member of Ubuntu
I see mention that testing has been done on the Lucid released kernel as
well as the Lucid pre-proposed kernels. Just curious if any testing has
been done on the Maverick kernel? There should be a Maverick LTS
backports kernel provided in the kernel-ppa (https://edge.launchpad.net
/~kernel-ppa/+a
Soren:
See this bug for more info from me on this:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/584048
a) I'll need to find time to set up this test, I'm working with you guys on
this while I also have internal issues here at work, so bear with me.
b) No, when I SSH to the VM from my
A couple of things would be helpful:
a) Have you tried this with multiple VM's at the same time? If so, do they both
stop working at the same time? If so, can they still reach each other?
b) Can you still reach the bridge itself when this problem happens? I.e. can
you access 192.168.8.166 from t
** Package changed: qemu-kvm (Ubuntu) => linux (Ubuntu)
--
Bridged Guests losing network connectivity
https://bugs.launchpad.net/bugs/633392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
> You think this is an issue with the kernel?
Did you get a chance to run this test with libvirt shut down? If so,
then the kernel and hardware are the only thing left in the equation.
If not, then it's not inconceivable, but unlikely, that libvirt is
periodically doing something nefarious. Is t
Serge,
It takes anywhere from maybe 10-30 minutes during the tests I ran, but
it always happens.
You think this is an issue with the kernel?
--
Bridged Guests losing network connectivity
https://bugs.launchpad.net/bugs/633392
You received this bug notification because you are a member of Ubuntu
Quoting Andrew Klettke (633...@bugs.launchpad.net):
> Serge,
>
> Something different happens with this. Now, I get the network
> instability that I saw before with SSH sessions exiting with "Broken
> Pipe", and the netcat session you showed in the link just hangs.
How quickly does it do that? I
Serge,
Something different happens with this. Now, I get the network
instability that I saw before with SSH sessions exiting with "Broken
Pipe", and the netcat session you showed in the link just hangs.
If I try to re-SSH into the box, however, it works again. It looks like
the same thing that wa
Hi,
I want to see if we can prove that this is purely a bridging problem. Could
you follow
the recipe at
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/616064/comments/33
(but attaching veth0 to br0 instead of virbr0)?
If this also loses connectivity, then we can pin it down to either
Serge,
No luck, still having the same issues with the new kernel.
--
Bridged Guests losing network connectivity
https://bugs.launchpad.net/bugs/633392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I'd try the pre-proposed lucid kernels, see:
https://launchpad.net/~kernel-ppa/+archive/pre-proposed
--
Bridged Guests losing network connectivity
https://bugs.launchpad.net/bugs/633392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Serge,
Yes, I want to be able to lock down guests to a specific NIC, this is
needed for VLAN segregation, as well as physical diversity.
Turning on STP makes no difference, the bug occurs regardless.
Which kernel should I try to install and run first?
--
Bridged Guests losing network connecti
Here is the netstart script:
#!/bin/sh -
#
# $OpenBSD: netstart,v 1.129 2010/01/12 07:43:41 henning Exp $
# Strip comments (and leading/trailing whitespace if IFS is set)
# from a file and spew to stdout
stripcom() {
local _l
[[ -f $1 ]] || return
while read _l; do
Thanks very much for opening this bug.
Can you append the /etc/netstart script from openbsd here?
I notice that while you have the libvirt-defined virbr0, your VM is using
a hand-build br0 (which has stp off). Is there any particular reason for
this? It looks like you want the guests locked in
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => High
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
--
Bridged Guests losing network connectivity
https://bugs.launchpad.net/bugs/633392
You received this bug notification because you are a
40 matches
Mail list logo
