large images handling

asked 2014-08-14 03:45:31 -0600

AlexShumilov
16 ●2 ●3 ●2

Hello! I have an ESXi host (VMware), Openstack compute and controller nodes are deployed as its VM's. I can successfully create VM's with my ubuntu and cirros images.

But the problem is that I can not launch an instance with my manually created Windows image - VMDK file with 40G file size. I can see that the VM is created and resources are allocated in vCenter client, but, I guess, it crushes at importing my image. Openstack dashboard show instance as "spawning", and nova list shows this for 3 hours by now:

 1eaa6d1d-88b2-4986-83d8-18bda1ae43d0 | ws | BUILD | spawning | NOSTATE | geos-net=86.232.26.15

Image was created with following options:

--disk-format=vmdk --property vmware_adaptertype="ide" --property vmware_disktype="sparse" --is-public=True --property vmware_ostype="windows7Server64Guest" --container-format=bare

Is it because of the image size? Logs are clean, so I have no idea why it happens.

edit retag flag offensive close merge delete

add a comment

0

answered 2014-08-27 20:20:18 -0600

AlexShumilov
16 ●2 ●3 ●2

The problem was because of I did not have enough patience - it took so long because of Openstack was copying image back to the ESXi host. Basically, next time when I use this image, it will take a minute to deploy VM insted of 16 hours:) My full story and solution is posted at http://alexshumilov.blogspot.ru/2014/08/deploying-windows-server-2008-r2-on.html (http://alexshumilov.blogspot.ru/2014/...)