[Bug 1189909] Re: dhcp-agent does always provide IP address for instances with re-cycled IP addresses.

i think neutron did not delete the port asap，maybe we can set dnsmasq lease time 3600 and wait for neutron deleting the port！ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189909 Title:

[Bug 1189909] Re: dhcp-agent does always provide IP address for instances with re-cycled IP addresses.

The same problems， who can reproduce the problem！ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189909 Title: dhcp-agent does always provide IP address for instances with re-cycled IP addresses.

[Bug 1088295] Re: lxc container can control other container's cpu share, memory limit, or access of block and character devices

thanks Serge，i’ll try -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088295 Title: lxc container can control other container's cpu share,memory limit,or access of block and character devices

[Bug 645625] Re: lxc container can power-off host machine

thanks for your infomation,Serge -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/645625 Title: lxc container can power-off host machine To manage notifications about this bug go to:

[Bug 645625] Re: lxc container can power-off host machine

thanks for your infomation,Serge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645625 Title: lxc container can power-off host machine To manage notifications about this bug go to:

[Bug 1088295] Re: lxc container can control other container's cpu share, memory limit, or access of block and character devices

thanks for your rapid reply. sorry, i'm newbie to appamor 1. what i should do is to create a appamor policy for /usr/lib/libvirt/libvirt_lxc or anything else? 2. how can i do per-container apparmor policies 3. could i refer below appamor policy for lxc root@superstack:~# cat

[Bug 645625] Re: lxc container can power-off host machine

can somebody show we how to solve this problem with appamor, i install openstack with lxc installed, and i can use echo b /proc/sysrq-trigger to power-off host. sorry,i'am newbie to appamor... thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which

[Bug 861504] Re: nova-compute-lxc limited by available nbd devices to 16 instances

i solve the problem by “modprobe nbd nbds_max=30” and vi /usr/lib/python2.7/dist-packages/nova/virt/disk/nbd.py ... cfg.IntOpt('max_nbd_devices', default=30, ##check it here help='maximum number of possible nbd devices') .. -- You

[Bug 645625] Re: lxc container can power-off host machine

can somebody show we how to solve this problem with appamor, i install openstack with lxc installed, and i can use echo b /proc/sysrq-trigger to power-off host. sorry,i'am newbie to appamor... thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 861504] Re: nova-compute-lxc limited by available nbd devices to 16 instances

i solve the problem by “modprobe nbd nbds_max=30” and vi /usr/lib/python2.7/dist-packages/nova/virt/disk/nbd.py ... cfg.IntOpt('max_nbd_devices', default=30, ##check it here help='maximum number of possible nbd devices') .. -- You