After migration the VMs from the ESX to RHEV3.0, the disks still appear as "locked".
Environment
- Red Hat Enterprise Virtualization 3.0
Issue
- After migration the VMs from the ESX to RHEV3.0, the disks still appear as "locked" even though the VM is 'down'.
Diagnostic Steps
- Following is the Workaround to fix this issue.
* Replace test with name of the VM.
* To listing the status we can use the below syntax in the RHEV-M database,
rhevm=# select imagestatus,image_guid from images where image_guid in (SELECT image_id from image_vm_map where vm_id in (SELECT vm_guid from vm_static where vm_name='test'));
-[ RECORD 1 ]-------------------------------------
imagestatus | 2
image_guid | cda66745-7637-4ab4-b41e-543933610066
-[ RECORD 2 ]-------------------------------------
imagestatus | 2
image_guid | 2505fa0e-206f-4b50-8e88-bfcf332d51c2
* To update the status,
rhevm=# UPDATE images SET imagestatus = '1' where image_guid in (SELECT image_id from image_vm_map where vm_id in (SELECT vm_guid from vm_static where vm_name='test'));
UPDATE 2
rhevm=# select imagestatus,image_guid from images where image_guid in (SELECT image_id from image_vm_map where vm_id in (SELECT vm_guid from vm_static where vm_name='test'));
-[ RECORD 1 ]-------------------------------------
imagestatus | 1
image_guid | cda66745-7637-4ab4-b41e-543933610066
-[ RECORD 2 ]-------------------------------------
imagestatus | 1
image_guid | 2505fa0e-206f-4b50-8e88-bfcf332d51c2
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
