openstack team mailing list archive

["hzguanqiang"<hzguanqiang@xxxxxxxxxxxxxxxx>]

Hi Pádraig
I think you are right. I met the same probelm just as 念远 did when I tried lxc with openstack folsom.
To solve the problem, I tried to modify the function setup_container, adding a partition argument to _DiskImage(...) just as follow:

 #img = _DiskImage(image=image, use_cow=use_cow, mount_dir=container_dir)                                                                                          
 img = _DiskImage(image=image, partition=FLAGS.libvirt_inject_partition, use_cow=use_cow, mount_dir=container_dir) 

And it works! 

But I still have a little doubt about the lxc image. 
It seems to me that many kvm images can not be used to create lxc while another little few can.
Why does this happen?

thanks,
Guan Qiang.

On 10/21/2012 06:17 PM, Pádraig wrote:
>On 10/19/2012 09:15 PM, 念远 wrote: 
>> Hi,all! 
>> 
>> In my ubuntu server (12.04.1), install openstack folsom, but i can't boot instance,nova-compute.log display blow log ! 
>> 
>> who can help me,thanks! 
>
>> 2012-10-20 08:58:45 TRACE nova.compute.manager [instance: d0a1c023-800c-4f1f-bb27-fb8279c6712e]   File "/usr/lib/python2.7/di 
>> st-packages/nova/virt/disk/api.py", line 326, in setup_container 
>> 2012-10-20 08:58:45 TRACE nova.compute.manager [instance: d0a1c023-800c-4f1f-bb27-fb8279c6712e]     raise exception.NovaExcep 
>> tion(img.errors) 
>> 2012-10-20 08:58:45 TRACE nova.compute.manager [instance: d0a1c023-800c-4f1f-bb27-fb8279c6712e] NovaException: 
>> 2012-10-20 08:58:45 TRACE nova.compute.manager [instance: d0a1c023-800c-4f1f-bb27-fb8279c6712e] -- 
>> 2012-10-20 08:58:45 TRACE nova.compute.manager [instance: d0a1c023-800c-4f1f-bb27-fb8279c6712e] Failed to mount filesystem: U 
>> nexpected error while running command. 
>
>Are you using a partitioned image? 
>LXC doesn't currently support that. 
>You should be able copy out the partition of interest 
>if this is that case, and use that directly image.