sureshanaparti commented on pull request #5410:
URL: https://github.com/apache/cloudstack/pull/5410#issuecomment-935749660
> @sureshanaparti sorry for the delay, I have been debugging and running
some tests:
>
> I am also pushing a commit (tested recently on it as well) which I am
addressing a review from @GutoVeronezi. These are the output of my recent tests:
>
> ### 1 VM With local Root disk
> **(i) Without volumes mapping:** migrate virtualmachinewithvolume
virtualmachineid=1f83b074-2d25-4eb1-9e10-bf26ccb71e50
hostid=a19dcabd-53b6-44e4-9f57-2fa70d876ef8 => Success
>
> **(ii) With ROOT volume mapping:** migrate virtualmachinewithvolume
virtualmachineid=1f83b074-2d25-4eb1-9e10-bf26ccb71e50
hostid=448a0207-975b-41e1-af07-0c6e55dae0b3
migrateto[0].volume=e6e28756-0beb-4f75-8e6e-9ba5cc50b983
migrateto[0].pool=887fe175-7422-4e3a-a9ed-392932afa631 => Success
>
> ### 2 VM With local Root disk + Shared (RBD) DATA disk
> **(i) Without volumes mapping:** migrate virtualmachinewithvolume
virtualmachineid=1f83b074-2d25-4eb1-9e10-bf26ccb71e50
hostid=448a0207-975b-41e1-af07-0c6e55dae0b => Success
>
> **(ii) With ROOT volume mapping:** migrate virtualmachinewithvolume
virtualmachineid=0f6c2e2d-7960-4715-b0c9-8634ccc36548 hostid=
migrateto[0].volume=e6e28756-0beb-4f75-8e6e-9ba5cc50b983
migrateto[0].pool=2bfa2e18-d76f-46db-8605-4aafb1438030 => Success
>
> ### 3 VM With local Root disk + Shared (NFS) DATA disk
> **(i) Without volumes mapping:** migrate virtualmachinewithvolume
virtualmachineid=1f83b074-2d25-4eb1-9e10-bf26ccb71e50
hostid=448a0207-975b-41e1-af07-0c6e55dae0b => Failed with error:`"Copy
volume(s) to storage(s) [{volume: "13433", from: "23", to:"26"}] and VM to host
[{vm: "13452", from: "24", to:"46"}] failed in
StorageSystemDataMotionStrategy.copyAsync. Error message: [Exception during
migrate: org.libvirt.LibvirtException: internal error: unable to execute QEMU
command 'nbd-server-add': Block node is read-only]."`
>
> ### COnclusion
> In conclusion, all tests worked fine for me, except for the one with the
NFS data disk (which seems to work with you). I assume that the exception might
be due to configurations in the NFS pool or the Libvirt, due to
"LibvirtException: internal error: unable to execute QEMU command
'nbd-server-add': Block node is read-only."
Thanks @GabrielBrascher for sharing the test results. I've manually tested
these cases to re-confirm.
**1. VM With local Root disk**
(i) Without volumes mapping => Success
`migrate virtualmachinewithvolume
virtualmachineid=20100007-11cb-49c3-b1df-1c133d1e5698
hostid=0159d982-413f-4662-af19-1ec8d194ee3f`
(ii) With ROOT volume mapping => Success
`migrate virtualmachinewithvolume
virtualmachineid=20100007-11cb-49c3-b1df-1c133d1e5698
hostid=27495299-c2fc-47d5-9901-907769c0383e
migrateto[0].volume=fb97299c-0940-48c7-84a5-6245617839e1
migrateto[0].pool=f2833483-ddd1-49b2-b485-3ac1dd6c6870`
**2. VM With local Root disk + Shared (NFS) DATA disk**
(i) Without volumes mapping => Success
`migrate virtualmachinewithvolume
virtualmachineid=20100007-11cb-49c3-b1df-1c133d1e5698
hostid=0159d982-413f-4662-af19-1ec8d194ee3f `
(ii) With ROOT volume mapping => Success
`migrate virtualmachinewithvolume
virtualmachineid=20100007-11cb-49c3-b1df-1c133d1e5698
hostid=27495299-c2fc-47d5-9901-907769c0383e
migrateto[0].volume=fb97299c-0940-48c7-84a5-6245617839e1
migrateto[0].pool=f2833483-ddd1-49b2-b485-3ac1dd6c6870`
(iii) With ROOT and DATA volumes mapping => Failed (Is this case not
supported?)
`migrate virtualmachinewithvolume
virtualmachineid=20100007-11cb-49c3-b1df-1c133d1e5698
hostid=0159d982-413f-4662-af19-1ec8d194ee3f
migrateto[0].volume=fb97299c-0940-48c7-84a5-6245617839e1
migrateto[0].pool=e426bff5-286b-4c60-b80a-6385d9a7fbb1
migrateto[1].volume=c954a27f-10c4-46d7-9457-9891fd69c155
migrateto[1].pool=592e0d54-f768-31fa-92a9-c6e2120a159e`
API error: _"Failed to migrated vm VM instance {id: \"348\", name:
\"i-2-348-VM\", uuid: \"20100007-11cb-49c3-b1df-1c133d1e5698\", type=\"User\"}
along with its volumes. "_
Target Host's agent log:
_2021-10-06 08:07:19,052 WARN [kvm.resource.LibvirtConnection]
(agentRequest-Handler-3:null) (logid:074379e7) Can not find a connection for
Instance i-2-348-VM. Assuming the default connection.
2021-10-06 08:07:19,054 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) (logid:074379e7) Failed to get dom xml:
org.libvirt.LibvirtException: Domain not found: no domain with matching name
'i-2-348-VM'
2021-10-06 08:07:19,278 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) (logid:074379e7) Failed to get vm :Domain not
found: no domain with matching name 'i-2-348-VM'_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
