VMware to OpenStack Migration using virt-v2v
This document describes the path to migrate a virtual machine from VMware to OpenStack using virt-v2v vpx. You should use vddk plugins to make this process fast for which link is mentioned in the doc.
I used OpenStack volume on the destination cloud however one can select glance or local basis upon their used cases.
Pre-requisite
- *Port
5000should connect from v2v appliance to OpenStack keystone endpoint. - *Ports
443,5480should connect from v2v appliance to VMware vCenter and Esxi hosts. - *DNS should resolve the VMware
hostnamesFQDN inside v2v virtual appliance.
Additional Pre-requisite for Windows VMs
For windows VM migration we need to complete one time additional pre-requites on v2v virtual appliance mentioned on the below link.
Windows VM migration pre-requisite
Enable vddk plugins
vddk plugins uses VMware sdk which enables addtional functionalities to be used for the migration. You are required to enable vddk plugins to use them explicitly using link mentioned below.
Environment
Kindly refer below details which is used in this documentation. These IPs, FQDN and Openstack properties can be different in your environment.
- *VMware Cloud -
demo-vmware-cloud.com - *OpenStack Cloud keystone public endpoint -
192.168.10.11 - *virt-v2v Virtual appliance -
192.168.11.11
Steps
Create v2v appliance
Run below command on destination OpenStack cloud. Make sure that you have already created the required tenant network, image, flavor, security-group and keypair. Your tenant network must reach out to VMware cloud on the ports mentioned above.
On Controller node
openstack server create --network NET01 \
--image ubuntu24 \
--flavor mig-testing \
--security-group mig-testing \
--key-name key01 virt-v2v-appl
Check if appliance instance has been created and in ACTIVE state.
Install required package on appliance
Login to the appliance creted. You will require key associated with keypair used to create the appliance. Here I am using key01 to login which is saved under my home directory.
On Controller node
Execute below commands to install the required packages.
On virt-v2v Appliance
sudo -i
apt-get update
apt-get upgrade
reboot
ssh -i .ssh/key01ubuntu@192.168.11.11
apt-get install virt-v2v -y
apt-get install python3-openstackclient -y
apt install libvirt-clients -y
Verify required ports are opened
Make sure that you can reach on the specified ports from appliance to VMware and OpenStack cloud.
On virt-v2v Appliance
Copy ca certificate
You must need to copy ca certificate from controller to appliance.
On Controller node
scp -i ~/.ssh/key01 /etc/ssl/certs/ca-certificates.crt ubuntu@192.168.11.11:/tmp/
ssh -i ~/.ssh/key01 ubuntu@192.168.11.11
Move ca certificate
Move ca certificate from /tmp directory to /etc/ssl/certs
On virt-v2v Appliance
Create bashrc on appliance
Create bashrc file on virtual appliance to update common OpenStack env variables to connect to destination OpenStack Cloud. You can take reference of your exisitng openrc file from OpenStack cloud.
On virt-v2v Appliance
vim /root/.bashrc
# COMMON OPENSTACK ENVS
export OS_USERNAME=admin
export OS_PASSWORD='xxxxxxxxxxxxxxxxxxxxxxxxxxx'
export OS_PROJECT_NAME=admin
export OS_TENANT_NAME=admin
export OS_AUTH_TYPE=password
export OS_AUTH_URL=https://192.168.10.11:5000/v3
export OS_NO_CACHE=1
export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_DOMAIN_NAME=Default
export OS_REGION_NAME=RegionOne
# For openstackclient
export OS_IDENTITY_API_VERSION=3
export OS_AUTH_VERSION=3
export OS_CACERT=/etc/ssl/certs/ca-certificates.crt
Source .bashrc file created and run OpenStack command to check if appliance can talk to OpenStack apis.
List hosted virtual machines
Run below command to list guests from source VMware cloud. VPX link can be created using below settings.
vpx://vcenter.fqdn/datacentername/clustername/hypervisorname?no_verify=1
no_verify value could be 0 or 1. If value is 1 it means that SSL verification would be disabled.
On virt-v2v Appliance
virsh -c 'vpx://demo-vmware-cloud.com/DC1/DC1-Cluster-02/demo-hyp1-cloud.com?no_verify=1' list --all
Provide existing VMware username and password
Enter username for demo-vmware-cloud.com [administrator@vsphere.local]: domain\user-id
Enter Domain\user-id's password for demo-vmware-cloud.com:
The command should return hosted vitual machine on particular VMware hypervisor mentioned in vpx link.
Example output:
Id Name State
-----------------------------------------------------------------
22 abc1 running
43 abc2 running
1190 xyz1 running
2142 xyz2 running
2144 demo1 running
7018 demo2 running
Migrate disk
Run below command to move disk from source cloud and upload to OpenStack volume. Before executing the command make sure guest VM is in shutdown state on VMware.
In the command
ubuntu20-mig- Guest VM name on VMware cloud to be migratedpassword.txt- Password file created for the VMware domain user on v2v virtual applianceverify-server-certificate=falseserver-id- virt-v2v virtual appliance id running on OpenStack
On virt-v2v Appliance
virt-v2v -ic 'vpx://user-id@demo-vmware-cloud.com/DC1/DC1-Cluster-02/demo-hyp1-cloud.com?no_verify=1' \
ubuntu20-mig \
-o openstack -ip password.txt \
-oo verify-server-certificate=false \
-oo server-id='45dgftbbfddr6784fhskkei8v8483k'
Once the command is executed it will capture the snapshot of the Virtual Machine and followed by data copy from VMware Datastore to Openstack Volume. The number of the OpenStack Volume created on the destination would be propotional to the number of disks attached on the Virtual Machine on source while performing migration.
output
[ 0.0] Setting up the source: -i libvirt -ic vpx://user-id@demo-vmware-cloud.com/DC1/DC1-Cluster-02/demo-hyp1-cloud.com?no_verify=1 ubuntu20-mig
[ 6.5] Opening the source
[ 89.0] Inspecting the source
[ 561.5] Checking for sufficient free disk space in the guest
[ 561.5] Converting Ubuntu20-mig to run on KVM
virt-v2v: The QEMU Guest Agent will be installed for this guest at first
boot.
virt-v2v: This guest has virtio drivers installed.
[1885.9] Mapping filesystem data to avoid copying unused and blank areas
[1987.6] Closing the overlay
[1987.8] Assigning disks to buses
[1987.8] Checking if the guest needs BIOS or UEFI to boot
virt-v2v: This guest requires UEFI on the target to boot.
[1987.8] Setting up the destination: -o openstack -oo server-id=kk57djj4yuu589037fkkhe5ii3jk
[2004.1] Copying disk 1/1
█ 100% [****************************************]
[3468.5] Creating output metadata
[3475.6] Finishing off
If you want to use vddk plugins then execute the steps mentioned in below link and come back here for further steps to be executed.
Verify migrated disk
Once disk migration is successful, you will see OpenStack volume created on destination.
On virt-v2v Appliance
Example output
+--------------------------------+----------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+--------------------------------+----------------------------------------------------------------------------------------------------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | true |
| consistencygroup_id | None |
| created_at | 2024-11-22T09:31:02.000000 |
| description | ubuntu20-mig disk 1/1 converted by virt-v2v |
| encrypted | False |
| id | rfhyr4565-jj8884j-46d9vj-jjkkrmmchd |
| migration_status | None |
| multiattach | False |
| name | ubuntu20-mig |
| os-vol-host-attr:host | compute02.openstack.cloud.com@ceph#ceph |
| os-vol-mig-status-attr:migstat | None |
| os-vol-mig-status-attr:name_id | None |
| os-vol-tenant-attr:tenant_id | rfhyr4565-jj8884j-46d9vj-jjkkrmmchd |
| properties | virt_v2v_conversion_date='2024/11/22 08:57:51', virt_v2v_disk_index='1/1', virt_v2v_guest_name='ubuntu20-mig', |
| | virt_v2v_version='2.4.0' |
| replication_status | None |
| size | 12 |
| snapshot_id | None |
| source_volid | None |
| status | available |
| type | __DEFAULT__ |
| updated_at | 2024-11-22T09:55:50.000000 |
| user_id | hhfh4i892hjhh5824dkjhaafop49999845jhddg |
| volume_image_metadata | {'architecture': 'x86_64', 'hypervisor_type': 'kvm', 'vm_mode': 'hvm', 'hw_disk_bus': 'virtio', 'hw_vif_model': 'virtio', |
| | 'hw_video_model': 'vga', 'hw_machine_type': 'q35', 'os_type': 'linux', 'os_distro': 'ubuntu', 'hw_cpu_sockets': '1', |
| | 'hw_cpu_cores': '2', 'os_version': '20.04', 'hw_rng_model': 'virtio', 'hw_firmware_type': 'uefi'} |
+--------------------------------+----------------------------------------------------------------------------------------------------------------------------------+
Set additional flags on Volume
If source VM has uefi firmware set with secure boot enabled then you need to set boot flag on OpenStack volume additionally.
On virt-v2v Appliance
Check if flag is set on the volume.
The volume property should show 'os_secure_boot=required' flag on it.
Example output
+--------------------------------+------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+--------------------------------+------------------------------------------------------------------------------------------------------------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | true |
| consistencygroup_id | None |
| created_at | 2024-11-22T09:31:02.000000 |
| description | ubuntu20-mig disk 1/1 converted by virt-v2v |
| encrypted | False |
| id | rfhyr4565-jj8884j-46d9vj-jjkkrmmchd |
| migration_status | None |
| multiattach | False |
| name | ubuntu20-mig-sda |
| os-vol-host-attr:host | compute02.openstack.cloud.com@ceph#ceph |
| os-vol-mig-status-attr:migstat | None |
| os-vol-mig-status-attr:name_id | None |
| os-vol-tenant-attr:tenant_id | rfhyr4565-jj8884j-46d9vj-jjkkrmmchd |
| properties | os_secure_boot='required', virt_v2v_conversion_date='2024/11/22 08:57:51', virt_v2v_disk_index='1/1', virt_v2v_guest_name='ubuntu20-mig' |
| | ubuntu20-mig', virt_v2v_version='2.4.0' |
| replication_status | None |
| size | 12 |
| snapshot_id | None |
| source_volid | None |
| status | available |
| type | __DEFAULT__ |
| updated_at | 2024-11-22T10:23:39.000000 |
| user_id | hhfh4i892hjhh5824dkjhaafop49999845jhddg |
| volume_image_metadata | {'architecture': 'x86_64', 'hypervisor_type': 'kvm', 'vm_mode': 'hvm', 'hw_disk_bus': 'virtio', 'hw_vif_model': 'virtio', |
| | 'hw_video_model': 'vga', 'hw_machine_type': 'q35', 'os_type': 'linux', 'os_distro': 'ubuntu', 'hw_cpu_sockets': '1', |
| | 'hw_cpu_cores': '2', 'os_version': '20.04', 'hw_rng_model': 'virtio', 'hw_firmware_type': 'uefi'} |
+--------------------------------+------------------------------------------------------------------------------------------------------------------------------------------+
Create instance with volume
Create new instance using migrated volume. I used NET02 as a production tenant network. You can choose flavor, security-group, keypair and network basis upon your environment. volume must the name/id of the migrated volume created.
On virt-v2v Appliance
openstack server create --network NET02 \
--flavor m1.small \
--security-group mig-testing \
--key-name key01 \
--volume rfhyr4565-jj8884j-46d9vj-jjkkrmmchd \
ubuntu20-mig
output
+--------------------------------------+---------------------------------------------------+
| Field | Value |
+--------------------------------------+---------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | |
| OS-EXT-SRV-ATTR:host | None |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None |
| OS-EXT-SRV-ATTR:instance_name | |
| OS-EXT-STS:power_state | NOSTATE |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | None |
| OS-SRV-USG:terminated_at | None |
| accessIPv4 | |
| accessIPv6 | |
| addresses | |
| adminPass | Ggdder5632hy |
| config_drive | |
| created | 2024-11-22T10:25:01Z |
| flavor | m1.small (oowuc9995mmchelkjf098345jkjhhj3) |
| hostId | |
| id | 55357fdr-7543-3224-84g3-kkjf677493kkhd |
| image | N/A (booted from volume) |
| key_name | key01 |
| name | ubuntu20-mig |
| os-extended-volumes:volumes_attached | [] |
| progress | 0 |
| project_id | rfhyr4565-jj8884j-46d9vj-jjkkrmmchd |
| properties | |
| security_groups | name=499385-hhfu389-9994-2ff4-dj5lxhj49973jjvnbd' |
| status | BUILD |
| updated | 2024-11-22T10:25:01Z |
| user_id | hhfh4i892hjhh5824dkjhaafop49999845jhddg |
+--------------------------------------+---------------------------------------------------+
Check if instance is created successfully.
You should see instance created and in ACTIVE/RUNNING state.
output
+--------------------------------------+-----------------------+--------+---------------------------+---------------------------------+-------------+
| ID | Name | Status | Networks | Image | Flavor |
+--------------------------------------+-----------------------+--------+---------------------------+---------------------------------+-------------+
| 55357fdr-7543-3224-84g3-kkjf677493kkhd | ubuntu20-mig | ACTIVE | NET02=10.240.20.24 | N/A (booted from volume) | m1.small |
+--------------------------------------+-----------------------+--------+---------------------------+---------------------------------+-------------+
Capture instance IP and see if you can reach to it.
output
PING 10.240.20.24 (10.240.20.24) 56(84) bytes of data.
64 bytes from 10.240.20.24: icmp_seq=1 ttl=64 time=3.59 ms
64 bytes from 10.240.20.24: icmp_seq=2 ttl=64 time=1.08 ms
^C
--- 10.240.20.24 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 1.079/2.334/3.590/1.255 ms
Login to instance
Login to the instance with existing username created on source cloud. Move 99-installer.cfg to allow cloud-init to update config and ssh keys.
On virt-v2v Appliance
user-id: existing VM username on the source cloud
On migrated Instance
Login using default user
Now you will be able to login using default cloud username ubuntu and ssh keys.
On virt-v2v Appliance
Uninstall VMware residuals
Execute below command to remove VMware Tools from the migrated instance.
On migrated Instance