This bug is considered fixed for me. Not a single network glitch since
installing the package from PPA. Many thanks to the development team!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997978
Title:
Installed yesterday and rebooted the dom0 machine and thus all virtual
machines. Will report back if there are any problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997978
Title:
KVM images lo
Another update: multiple KVM VM failures over the past couple of days,
the lxc-container is working without issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997978
Title:
KVM images lose connect
An update: had a different KVM VM die today (same symptoms/resolution as
previously); the LXC instance remains working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997978
Title:
KVM images lose co
Hey,
There is no DHCP server for that network, which is why I set up the
static IPs.
The cgroup-bin package wasn't installed, I installed that and then grep
showed some output:
root:~# grep cgroup /proc/self/mounts
cgroups /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
cgroup /sys/fs/cgroup/cpu c
It took a few days, but we've finally had a failure of VM instance 2.
It died 2.5 hours ago. Logging into the dom0 host shows the arp table
dead for that host:
mailer02..com (incomplete)
br0
Logging into the machine itself via console:
root:~# ifconfig
eth0 Link encap:Ethe
I tried building the container this morning using both your file above, and the
following:
lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.network.ipv4=212.XX.239.103/28
lxc.network.name=eth0
# lxc-create -t ubuntu -f lxc.conf -n lxc1
debootstrap is /usr/sbin/debootstrap
Chec
This happens to one of the VMs at any one time (on Wednesday two failed,
about 2 hours apart). There's no discernible pattern in terms of time of
day or length of a VMs uptime.
The next time one fails (they've been stable today), I'll do a route -n
and post the output. For record, currently (with
Public bug reported:
System:
---
Dell R410 Dual processor 2.4Ghz w/16G RAM
Distributor ID: Ubuntu
Description:Ubuntu 12.04 LTS
Release:12.04
Codename: precise
Setup:
-
We're running 3 KVM guests, all Ubuntu 12.04 LTS using bridged networking.
>From the host:
#
