[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Right, that does seem to improve things immensly. I'm still seeing a
'disconnected' alerm from network manager, but it does not *actually*
seems to be disconnecting eth0.
I'm still seeing a process appearing:
root 26471 0.0 0.0 10232 2412 ?Ss 13:04 0:00
dhclient -1 -v -pf
I'm still seeing a process appearing:
root 26471 0.0 0.0 10232 2412 ?Ss 13:04 0:00
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
so we still seem to be messing with eth0.
Assuming that dhclient is running in the container, it
Please try adding the following to your network device definition:
target dev='veth0'/
For instance my full definition looked like:
interface type='network'
mac address='52:54:00:67:86:cf'/
source network='default'/
target dev='veth0'/
/interface
--
You received this
It has occurred to me that I have not rebooted since installing
lxc...I'll try that just in case it makes a difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331276
Title:
Starting lxc
You did not indicate whether
virsh -c lxc:/// destroy lxc1
gives you any error messages. Assuming it gives you an error about
not being able to kill dhclient, then please add the line
signal (receive) peer=/usr/sbin/libvirtd,
to the /sbin/dhclient section of
Sorry - I should have been clearer that the 'permission denied' errors
where from 'destroy lxc1' and the process concerned was dhcp. Yeah,
amending apparmor as indicated sorts that problem out.
Rebooting made no difference (worth checking I guess).
With respect to the eth0 business, I note a lot
** Attachment added: Syslog activity when the domain is started from virsh
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1331276/+attachment/4135213/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Some more info:
Before I do virsh -c lxc:/// start lxc1 here are running dhcp processes:
root 1707 0.0 0.0 10232 3696 ?S10:04 0:00
/sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf
/run/sendsigs.omit.d/network-manager.dhclient-eth0.pid -lf
How I created the container:
(root) $ apt-get install lxc
(root) $ lxc-create -t ubuntu -n lxc1
(root) $ /etc/libvirt/lxc/lxc1.xml # see above
(root) $ virsh -c lxc:///
start lxc1
Host net config
$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
11 matches
Mail list logo
