Can't move VDISK within Local SR
Petahh opened this issue · 10 comments
Dear developers,
Relatively straight forward problem. I can't move VDISK between Local SRs.
No idea if this was intention to disable in higher versions or a bug.
This behavior is not observed in Version 7.6.1.
I can observe this in version 7.6.3 upwards till latest release.
Thank you very much for your support and for making this amazing project possible!
First of all, you are using https://github.com/xcp-ng/xenadmin which is an independent fork of the current repo and has different release and versioning cycles, so issues with that client should be first reported to their issue page and only escalated here if it is proven they are upstream problems.
Beyond this, if your VM has no home server assigned, by design you can't move the vdi to local sr. As a workaround, do "Move VM" instead which will also allow you to set a home server on the VM.
@kc284 I think you did not understand @Petahh s issue correctly. He wants to move a VDI from a local SR to another local SR; no shared storage at all. One Server, no "Pool", so the home server thing should not matter, because there is only one host.
I had the exact same issue and in the end used XenOrchestra to do the job :-/ so it's not a restriction on XAPI side.
Hi Konstantina!
The versions referenced above are XCP-ng Center versions (close fork of XenCenter). XCP-ng itself keeps the same versioning as Citrix Hypervisor. From what I understand, this is mostly related to a change in the code of XenCenter here, since XenOrchestra is able to move the VDISK. I guess @borzel and @Petahh will be able to specify which versions of XCP-ng they are using if that's relevant. Probably 7.6.0, 8.0.0 or both, which will translate to the exact same versions of XenServer / Citrix Hypervisor.
xen-hypervisor 4.7.6
xen-hypervisor 4.7.6
Ok, so either XenServer 7.6 or XCP-ng 7.6.
XCP-ng 7.6 sorry forgot to mention.
Ok, at the moment the move between local SRs is disallowed even if the VM has a home server and the target SR can be seen from the host, which I suppose is unexpected. I can't identify a regression though, and the code preventing this is fairly old. In any case, I'll re-open this issue for us to look at.
I also saw the old code, this is why I asked back to you with increased force :-)