Moving VMs from vSphere to Openstack to be still used in VMDK format

asked 2014-09-09 05:57:09 -0600

caddo gravatar image

Hi everyone,

basically i have a template of CentOS 6.4 x32 in my vSphere environment and i am running a small Openstack POC using the same vSphere environment.

As far as i can tell i can't use vSphere templates (yet) to start new instances so i figured i would import a template from vSphere to Openstack keeping the VMDK format to use it in Openstack but still using vSphere

Here's what i did: - i exported the template in OVF - i imported the VMDK file in glance - i started an instance with this image i just created

THe instance actually starts but no operating system is found; if i use the same OVF say in Fusion it starts correctly.

What am i missing? Maybe strage drivers or something similar? How do i get around it?

Thank you!

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted

answered 2014-09-12 12:54:05 -0600

caddo gravatar image

updated 2014-09-17 02:07:59 -0600

My problem is that all guides talk about converting formats but this is not my case.

This VM was built with VMware and needs to run on VMware... i just need to put them into Glance so that users can start spinning up instances with that image.

Is there a straightforward way to archieve this?

----------------- UPDATE-----------------

I found that the problem is due to the lack of support of thin provisioned VMDK.

If i use a thik provisioned VMDK i can upload it to glance as is and it just works.

I hope this help others to save some time.

edit flag offensive delete link more

answered 2014-09-10 02:34:24 -0600

SGPJ gravatar image

I agree with mpetason, adding to it after manually configuring vmdk convert it to qcow2 format for working with KVM (Openstack).


edit flag offensive delete link more

answered 2014-09-09 15:25:15 -0600

mpetason gravatar image

updated 2014-09-09 15:25:30 -0600

You have to modify the VMDK file if you want to do it manually. The VMDK file probably specifies sda as the disk where you actually need vda, or this was the issue when I was messing with VMware a while back ~Folsom/Grizzly.

I would suggest downloading the provided images instead of using your own unless you look at the documentation about how to build images. You need to configure more than the expected virtualized hardware types. You'll need to install cloud-init and a bunch of stuff.

However, there are guides that can help you with this:

How to build images -
Importing VMDK to OpenStack through conversion -
VMware info -

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-09-09 05:57:09 -0600

Seen: 3,227 times

Last updated: Sep 17 '14