openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #21164
Re: LXC on Folsom
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
References