Failed to migrate VM with error : failed to execute vgs

Vasu Vishal

Updated October 14, 2026 10:55

Applicable to:

SolusVM 2

Symptoms

Failed to migrate a VPS with error:

PRODUCT_ERROR: failed to execute vgs.

The exact text of the error could be different:

Error example 1

PRODUCT_ERROR: Cannot migrate VM "3fd03178-03e2-4f37-bc56-046dc09e51c0": validate migration disks: check whether disk "/var/lib/libvirt/images/5355/0" was actually migrated: determine whether "/var/lib/libvirt/images/5355/0" is on shared storage: get vg_shared for volume group "": failed to execute vgs --reportformat json -o vg_shared : stdout [ { "report": [ { "vg": [ ] } ] , "log": [ {"log_seq_num":"1", "log_type":"error", "log_context":"processing", "log_object_type":"vg", "log_object_name":"", "log_object_id":"", "log_object_group":"", "log_object_group_id":"", "log_message":"Volume group name \"\" has invalid characters.", "log_errno":"-1", "log_ret_code":"0"}, {"log_seq_num":"2", "log_type":"error", "log_context":"processing", "log_object_type":"vg", "log_object_name":"", "log_object_id":"", "log_object_group":"", "log_object_group_id":"", "log_message":"Cannot process volume group ", "log_errno":"-1", "log_ret_code":"0"}, {"log_seq_num":"3", "log_type":"status", "log_context":"processing", "log_object_type":"vg", "log_object_name":"", "log_object_id":"", "log_object_group":"", "log_object_group_id":"", "log_message":"failure", "log_errno":"-1", "log_ret_code":"5"} ] }]: exit status 5

Error example 2

PRODUCT_ERROR: Cannot migrate VM "16b5f0b8-a24c-4d69-87a9-03d89471648f": validate migration disks: check whether disk "/var/lib/libvirt/images/5082/0" was actually migrated: determine whether "/var/lib/libvirt/images/5082/0" is on shared storage: get vg_shared for volume group "": failed to execute vgs --reportformat json -o vg_shared : stdout [ { "report": [ Volume group name "" has invalid characters. Cannot process volume group "vg": [ ] } ] }]: exit status 5

Cause

The case has been submitted as a product issue with the internal ID SVM2-7581

Resolution

The fix will be included in one of the next updates.

A temporary workaround is to downgrade the SolusVM version by executing the command below:

# /usr/local/solus/bin/installer -revert -to 2.0.0-43929

And perform another upgrade attempt.

Note: This action does NOT guarantee resolution of the migration errors. If the issue still persists - contact SolusVM Technical Support for assistance.