openstack team mailing list archive

Thread
Date
Re: LXC on Folsom

To: Vishvananda Ishaya <vishvananda@xxxxxxxxx>
From: Chuan-Heng Hsiao <hsiao.chuanheng@xxxxxxxxx>
Date: Fri, 22 Feb 2013 11:04:48 +0800
Cc: openstack@xxxxxxxxxxxxxxxxxxx
In-reply-to: <67A71BAB-B71E-4BFA-A4CF-5FD4A5E2FF07@gmail.com>
Hi Vishvananda,

Thank you very much!

I just tried and it launched!

Though I can't access through VNC right now (code: 1006)
I believe it's the problem related to VNC setting and not related to lxc.

Sincerely,
Hsiao

The following is the startup console:

init: Unable to create device: /dev/kmsg
cloud-init start-local running: Fri, 22 Feb 2013 02:26:40 +0000. up
52122.82 seconds
no instance data found in start-local
ci-info: lo    : 1 127.0.0.1       255.0.0.0       .
ci-info: eth0  : 1 .               .               fa:16:3e:74:2f:f5
route_info failed
cloud-init start running: Fri, 22 Feb 2013 02:31:43 +0000. up 52425.78 seconds
2013-02-22 02:31:43,997 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[0/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:44,999 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[1/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:46,000 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[2/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:47,002 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[3/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:48,003 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[4/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:49,004 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[5/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:51,111 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[7/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:53,114 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[9/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:55,116 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[11/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:57,118 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[13/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:31:59,120 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[15/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:02,124 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[18/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:05,127 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[21/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:08,130 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[24/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:11,133 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[27/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:14,137 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[30/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:18,138 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[34/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:22,142 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[38/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:26,147 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[42/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:30,151 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[46/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:34,155 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[50/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:39,161 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[55/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:44,166 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[60/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:49,171 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[65/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:54,172 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[70/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:32:59,178 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[75/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:33:05,184 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[81/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:33:11,191 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[87/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:33:17,197 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[93/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:33:23,200 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[99/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:33:29,207 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[105/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:33:36,215 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[112/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:33:43,222 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[119/120s]: url error [[Errno 101] Network is unreachable]
2013-02-22 02:33:50,226 - DataSourceEc2.py[CRITICAL]: giving up on md
after 126 seconds

no instance data found in start
lxc-libvirt
 * Not starting AppArmor in container       [80G
[74G[ OK ]
landscape-client is not configured, please run landscape-config.
 * Stopping System V initialisation compatibility[74G[ OK ]
 * Starting System V runlevel compatibility[74G[ OK ]
 * Starting save kernel messages[74G[ OK ]
 * Starting automatic crash report generation[74G[[31mfail[39;49m]
 * Starting deferred execution scheduler[74G[ OK ]
 * Starting regular background program processing daemon[74G[ OK ]
 * Starting ACPI daemon[74G[ OK ]
 * Stopping save kernel messages[74G[ OK ]
 * Starting CPU interrupts balancing daemon[74G[ OK ]
 * Stopping System V runlevel compatibility[74G[ OK ]
[r[H[J

 * Starting execute cloud user/final scripts[74G[ OK ]
Ubuntu 12.04.2 LTS ubuntu tty1

ubuntu login:

On Fri, Feb 22, 2013 at 2:16 AM, Vishvananda Ishaya
<vishvananda@xxxxxxxxx> wrote:
> no i wasn't. The link you posted is a tar.gz filesystem, the link i posted is a tar.gz of an ext formatted that contains the filesystem. I believe the one i posted is correct.  Make sure to untargz before uploading to glance.
>
> Vish
>
> On Feb 21, 2013, at 9:47 AM, Chuan-Heng Hsiao <hsiao.chuanheng@xxxxxxxxx> wrote:
>
>> Hi Vishvananda,
>>
>> Thank you very much!
>> Are you actually refering to the following link?
>>
>> http://uec-images.ubuntu.com/releases/precise/release/ubuntu-12.04-server-cloudimg-amd64-root.tar.gz
>>
>> I'll try and do the report when I get to the machine tomorrow.
>>
>> Sincerely,
>> Hsiao
>>
>> On Fri, Feb 22, 2013 at 12:57 AM, Vishvananda Ishaya
>> <vishvananda@xxxxxxxxx> wrote:
>>> I'm pretty sure a whole disk image will fail with lxc. You need just the root filesystem.
>>>
>>> You might have more luck with the unpacked version of:
>>>
>>> http://uec-images.ubuntu.com/releases/precise/release/ubuntu-12.04-server-cloudimg-amd64.tar.gz
>>>
>>> Vish
>>>
>>> On Feb 21, 2013, at 8:34 AM, Chuan-Heng Hsiao <hsiao.chuanheng@xxxxxxxxx> wrote:
>>>
>>>> I also have same problem when trying to get LXC running on Folsom.
>>>>
>>>> Based on the following links:
>>>>
>>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/lxc.html
>>>> https://wiki.openstack.org/wiki/LXC
>>>> http://honeybutcher.de/2012/09/openstack-lxc/
>>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/adding-images.html
>>>>
>>>> I did the following things:
>>>>
>>>> 1. mkdir /cgroup
>>>>   set /etc/fstab with none /cgroup cgroup
>>>> cpuacct,memory,devices,cpu,freezer,blkio   0 0
>>>>   and reboot.
>>>> 2. glance image-create --location
>>>> http://uec-images.ubuntu.com/releases/12.04/release/ubuntu-12.04-server-cloudimg-amd64-disk1.img
>>>>   --is-public true --disk-format raw --container-format bare --name "Ubuntu"
>>>> 3. glance image-update [img-uuid] --property hypervisor_type=lxc
>>>>
>>>> and still no luck.
>>>>
>>>> I got the following error message from nova-compute node (I am not
>>>> quite sure whether there are other error msgs or not):
>>>>
>>>> 2013-02-21 12:46:39 ERROR nova.virt.disk.api
>>>> [req-74b2c194-fb8a-4db8-88b5-dcccf6ec0b97
>>>> 392652962bc64e8fa7bc8882203e2e36 92895e4901154c899fcdd1a348bf5712]
>>>> Failed to mount container filesystem '<nova.virt.disk.api._DiskImage
>>>> object at 0x507ee10>' on
>>>> '/var/lib/nova/instances/instance-00000009/rootfs':
>>>> 2013-02-21 12:46:39 ERROR nova.compute.manager
>>>> [req-74b2c194-fb8a-4db8-88b5-dcccf6ec0b97
>>>> 392652962bc64e8fa7bc8882203e2e36 92895e4901154c899fcdd1a348bf5712]
>>>> [instance: 870d1ee9-a4d3-4424-b41b-369f903553fd] Instance failed to
>>>> spawn
>>>> 2013-02-21 12:46:39 ERROR nova.compute.manager
>>>> [req-74b2c194-fb8a-4db8-88b5-dcccf6ec0b97
>>>> 392652962bc64e8fa7bc8882203e2e36 92895e4901154c899fcdd1a348bf5712]
>>>> [instance: 870d1ee9-a4d3-4424-b41b-369f903553fd] Build error:
>>>> ['Traceback (most recent call last):\n', '  File
>>>> "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 494,
>>>> in _run_instance\n    injected_files, admin_password)\n', '  File
>>>> "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 747,
>>>> in _spawn\n    block_device_info)\n', '  File
>>>> "/usr/lib/python2.7/dist-packages/nova/exception.py", line 117, in
>>>> wrapped\n    temp_level, payload)\n', '  File
>>>> "/usr/lib/python2.7/contextlib.py", line 24, in __exit__\n
>>>> self.gen.next()\n', '  File
>>>> "/usr/lib/python2.7/dist-packages/nova/exception.py", line 92, in
>>>> wrapped\n    return f(*args, **kw)\n', '  File
>>>> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
>>>> 1090, in spawn\n    admin_pass=admin_password)\n', '  File
>>>> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
>>>> 1469, in _create_image\n    use_cow=FLAGS.use_cow_images)\n', '  File
>>>> "/usr/lib/python2.7/dist-packages/nova/virt/disk/api.py", line 326, in
>>>> setup_container\n    raise exception.NovaException(img.errors)\n',
>>>> 'NovaException: \n--\nFailed to mount filesystem: Unexpected error
>>>> while running command.\nCommand: sudo nova-rootwrap
>>>> /etc/nova/rootwrap.conf mount /dev/nbd15
>>>> /var/lib/nova/instances/instance-00000009/rootfs\nExit code:
>>>> 32\nStdout: \'\'\nStderr: \'mount: you must specify the filesystem
>>>> type\\n\'\n--\nFailed to mount filesystem: Unexpected error while
>>>> running command.\nCommand: sudo nova-rootwrap /etc/nova/rootwrap.conf
>>>> guestmount --rw -a /var/lib/nova/instances/instance-00000009/disk -m
>>>> /dev/sda /var/lib/nova/instances/instance-00000009/rootfs\nExit code:
>>>> 1\nStdout: \'\'\nStderr: \'Traceback (most recent call last):\\n  File
>>>> "/usr/bin/nova-rootwrap", line 89, in <module>\\n
>>>> env=filtermatch.get_environment(userargs))\\n  File
>>>> "/usr/lib/python2.7/subprocess.py", line 679, in __init__\\n
>>>> errread, errwrite)\\n  File "/usr/lib/python2.7/subprocess.py", line
>>>> 1249, in _execute_child\\n    raise child_exception\\nOSError: [Errno
>>>> 2] No such file or directory\\n\'\n']
>>>>
>>>> Sincerely,
>>>> Hsiao
>>>>
>>>>
>>>> On Fri, Feb 22, 2013 at 12:17 AM, Konstantin Ivanov <kaivanov@xxxxxxxxx> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I am trying to get LXC running on Folsom with not much luck. Any suggestions on where I can find more documentation that can help me with this ?
>>>>>
>>>>> Thanks a bunch!
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~openstack
>>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>
>
Follow ups

Re: LXC on Folsom
From: Shashank Sahni, 2013-05-09
Re: LXC on Folsom
From: Bernhard M. Wiedemann, 2013-02-22
Re: LXC on Folsom
From: Skible OpenStack, 2013-02-22
References

LXC on Folsom
From: Konstantin Ivanov, 2013-02-21
Re: LXC on Folsom
From: Chuan-Heng Hsiao, 2013-02-21
Re: LXC on Folsom
From: Vishvananda Ishaya, 2013-02-21
Re: LXC on Folsom
From: Chuan-Heng Hsiao, 2013-02-21
Re: LXC on Folsom
From: Vishvananda Ishaya, 2013-02-21