Please, describe the problem here and provide additional information below (if applicable) …
Created new node on clean Debian 10 with all standard options, following the Node install docs as usual. Basic single volume LVM, disk devices are named sdx. However, when i migrade a VM to the new node it fails to boot and shows error in log “error: XML error: Unknown disk name ‘sd’ and no address specified”.
I’ve checked the vm config and it specifies device ‘sd’, and the node reports devices /dev/sdx (i am assumming this is the mapping). I had a few other issues with Deb 10 (due to changes like missing path variables etc). Are there some extra steps i need to take for Deb 10, maybe its permissions or something so i can migrate VM’s? It has happened with 2 VM’s so far (out of 2).
Versions of the related components and OS (frontend, hypervisors, VMs):
Opennebula 5.8.5, Frontend and existing node on Debian 9 (4.9.168-1+deb9u2), new node on deb 10 ( Debian 4.19.118-2). VM is Vyos 1.3 (late Jan rolling).
Steps to reproduce:
Current results:
Goes into FAILED state. Logs:
Fri May 29 05:54:38 2020 [Z0][VM][I]: New LCM state is SAVE_MIGRATE
Fri May 29 05:54:44 2020 [Z0][VMM][I]: /var/tmp/one/vmm/kvm/save: line 58: warning: command substitution: ignored null byte in input
Fri May 29 05:54:44 2020 [Z0][VMM][I]: ExitCode: 0
Fri May 29 05:54:44 2020 [Z0][VMM][I]: Successfully execute virtualization driver operation: save.
Fri May 29 05:54:44 2020 [Z0][VMM][I]: ExitCode: 0
Fri May 29 05:54:44 2020 [Z0][VMM][I]: Successfully execute network driver operation: clean.
Fri May 29 05:54:44 2020 [Z0][VM][I]: New LCM state is PROLOG_MIGRATE
Fri May 29 05:55:11 2020 [Z0][VM][I]: New LCM state is BOOT_MIGRATE
Fri May 29 05:55:12 2020 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Fri May 29 05:55:12 2020 [Z0][VMM][I]: ExitCode: 0
Fri May 29 05:55:12 2020 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Fri May 29 05:55:16 2020 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/restore '/var/lib/one//datastores/0/3/checkpoint' 'server4' 'one-3' 3 server4
Fri May 29 05:55:16 2020 [Z0][VMM][I]: /var/tmp/one/vmm/kvm/restore: line 43: warning: command substitution: ignored null byte in input
Fri May 29 05:55:16 2020 [Z0][VMM][E]: restore: Command "virsh --connect qemu:///system restore /var/lib/one//datastores/0/3/checkpoint --xml /var/lib/one//datastores/0/3/checkpoint.xml" failed: error: Failed to restore domain from /var/lib/one//datastores/0/3/checkpoint
Fri May 29 05:55:16 2020 [Z0][VMM][I]: error: internal error: unsupported disk type 'sd'
Fri May 29 05:55:16 2020 [Z0][VMM][E]: Could not restore from /var/lib/one//datastores/0/3/checkpoint
Fri May 29 05:55:16 2020 [Z0][VMM][E]: restore: Command "virsh --connect qemu:///system restore /var/lib/one//datastores/0/3/checkpoint --xml /var/lib/one//datastores/0/3/checkpoint.xml" failed: error: Failed to restore domain from /var/lib/one//datastores/0/3/checkpoint
Fri May 29 05:55:16 2020 [Z0][VMM][I]: error: internal error: unsupported disk type 'sd'
Fri May 29 05:55:16 2020 [Z0][VMM][E]: Could not restore from /var/lib/one//datastores/0/3/checkpoint
Fri May 29 05:55:16 2020 [Z0][VMM][E]: restore: Command "virsh --connect qemu:///system restore /var/lib/one//datastores/0/3/checkpoint --xml /var/lib/one//datastores/0/3/checkpoint.xml" failed: error: Failed to restore domain from /var/lib/one//datastores/0/3/checkpoint
Fri May 29 05:55:16 2020 [Z0][VMM][I]: error: internal error: unsupported disk type 'sd'
Fri May 29 05:55:16 2020 [Z0][VMM][E]: Could not restore from /var/lib/one//datastores/0/3/checkpoint
Fri May 29 05:55:16 2020 [Z0][VMM][I]: ExitCode: 1
Fri May 29 05:55:16 2020 [Z0][VMM][I]: Failed to execute virtualization driver operation: restore.
Fri May 29 05:55:16 2020 [Z0][VMM][E]: Error restoring VM: Could not restore from /var/lib/one//datastores/0/3/checkpoint
Expected results:
The VM should migrate and be able to run.