Getting errors when migrating 4 out 5 VMGuest
-
I wonder if it's a bug on XO side. The VDI map is the list of which VDI are going where.
Can you screenshot exactly the steps you are doing in XO?
-
Sure thing.
Here is the steps when the issue happens:
-
In the list of VM's select the guest that I want to migrate, notice it is currently on home-hypervisor host
-
I click on the migrate button and on the pop-out box I selected "xcp-ng-server2" host and click the "OK" button
-
You will notice nothing happen.
-
If I go to Settings->Logs, notice that I get the VDI error message:
This is how I make it work:
-
In the VM list I click on the target VMguest and goes into its detailed information then I click on migrate button
-
It now opens the box to select which host we want to migrate to, I have selected "xcp-ng-server2" and click the "OK" button
-
After it returns to the detailed information page, notice that it now show a progress in migrating the vmguest to the xcp-ng-server2 host
-
After few seconds it has successfully migrated the vmguest to the "xcp-ng-server2" host
I hope I was able to provide the screenshot that you needed, please let me know if you need more information.
-
-
Thanks! That might be a bug. We are about to make a release (tomorrow) but we'll see if we can reproduce it quickly. Adding @Melissa-FR or @MathieuRA in the loop
-
Hi
I tried to reproduce the steps on different VMs, but I was not able to reproduce the issue.
-
@ashinobi do you have some VMs you try to migrate with ISO inserted?
-
Yes 2 vm has guest vm tools iso inserted the other 3 doesn't have any iso.
Thanks for testing, that is really strange it is consistent on my setup. Do you need more information on my setup just incase it is something unique on how I configure my XCP-NG and Xen Orchestra?
-
That's likely because of the ISO. Eject them, and try again.
-
Disk name for your Alpine 3.13 vmguest machine. Is that using default name? What I notice (not sure if it will be relevant or not) is the ones that are not working. All of them I renamed disk name (XenOrchestra, Unifi-Controller, Mail-Client and HomeAssistant). The one that is working is Windows 10 (64-bit)_itaze which I didn't rename.
I am now deploying 2 new VM's to test this theory and see if that is the one causing problem. I will update this thread once done with the test.
-
You should test first to eject all the ISO and migrate
-
I did that as mention 3 of the vm's doesn't have iso mounted and it still experience the problem.
-
Done with the testing and it did not make any difference. Probably there is something on my setup that maybe causing this problem since this is only happening on my setup it maybe a problem on my setup.
Any advise what logs should I monitor to find out what maybe causing this problem?
-
While investigating the code, I found something unexpected. We don't have exactly the same behavior for migrating from the Home/VM view and from the VM view itself.
I will try to fix this and it might solve your problem.
I will come back to you when I have opened the branch to allow you to do some tests on it. -
@ashinobi Several bug fixes related to VM migration are on the
xo5/fix-bulk-migrationbranch. Could you please test to see if they solve your issue? -
Is the fix part of XO commi 2498a? If not how can I download the update. My apologies if that I am not familiar.
-
@ashinobi Switch to the target branch with the command
git checkout xo5/fix-bulk-migration. Then rebuild using the standardyarn; yarn build. -
@Danp said in Getting errors when migrating 4 out 5 VMGuest:
xo5/fix-bulk-migration
Hi, Danp.
Thank you for replying to me, my apologies but I am still new to all of this and I am trying to learn. If I execute the command you gave me I get the below error:
admin@xen-orchestra:~/XenOrchestraInstallerUpdater$ sudo git checkout xo5/fix-bulk-migration [sudo] password for admin: error: pathspec 'xo5/fix-bulk-migration' did not match any file(s) known to gitI have installed XO using XenOrchestra Installer Updater script, would this cause the problem?
-
It looks like you are using the installation script from @ronivay. I've never used it, so you may get better advice from one of the other forum members. I suspect that you weren't in the correct directory at the time you issued that command.
This is what it looks like on my end --
root@ubuntuxo:/home/danpollak# cd /opt/xen-orchestra/ root@ubuntuxo:/opt/xen-orchestra# git checkout xo5/fix-bulk-migration branch 'xo5/fix-bulk-migration' set up to track 'origin/xo5/fix-bulk-migration'. Switched to a new branch 'xo5/fix-bulk-migration' root@ubuntuxo:/opt/xen-orchestra# git checkout master Switched to branch 'master' -
Hi, Danp.
Thanks for the info, since I am using the script, the location for my installation is different:
admin@xen-orchestra:/opt/xo/xo-src/xen-orchestra$ ls AGPL.txt book.json CHANGELOG.pre-2022.md CODE_OF_CONDUCT.md ISC.txt package.json PULL_REQUEST_TEMPLATE.md scripts turbo.json @xen-orchestra babel.config.js CHANGELOG.md CHANGELOG.unreleased.md docs LICENSE.md packages README.md SECURITY.md @vates yarn.lockI have ran the command as per your instruction, but I got an error when running yarn:
admin@xen-orchestra:/opt/xo/xo-src/xen-orchestra$ sudo git checkout xo5/fix-bulk-migration [sudo] password for admin: Branch 'xo5/fix-bulk-migration' set up to track remote branch 'xo5/fix-bulk-migration' from 'origin'. Switched to a new branch 'xo5/fix-bulk-migration' admin@xen-orchestra:/opt/xo/xo-src/xen-orchestra$ yarn build yarn run v1.22.19 $ turbo run build --scope xo-server --scope xo-server-'*' --scope xo-web /bin/sh: 1: turbo: not found -
You need to run
yarnfollowed byyarn build. FYI, you can combine them into a single command like this --yarn; yarn build -
Here is what I got after running yarn:
admin@xen-orchestra:/opt/xo/xo-src/xen-orchestra$ sudo yarn;yarn build [sudo] password for admin: yarn install v1.22.19 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... [4/5] Linking dependencies... warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@5.0.0" has unmet peer dependency "@types/node@*". warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@5.0.0" has unmet peer dependency "typescript@>=4". warning "@vue/eslint-config-typescript > @typescript-eslint/eslint-plugin > ts-api-utils@1.0.3" has unmet peer dependency "typescript@>=4.2.0". warning "workspace-aggregator-04a3b3bf-f2de-4fa4-8c4d-af65746d82b1 > @vates/node-vsphere-soap > soap@1.0.0" has incorrect peer dependency "axios@^0.27.2". warning "workspace-aggregator-04a3b3bf-f2de-4fa4-8c4d-af65746d82b1 > @vates/event-listeners-manager > tap > @tapjs/test > @isaacs/ts-node-temp-fork-for-pr-2009@10.9.5" has unmet peer dependency "@types/node@*". warning "workspace-aggregator-04a3b3bf-f2de-4fa4-8c4d-af65746d82b1 > @vates/event-listeners-manager > tap > @tapjs/asserts > tcompare > react-element-to-jsx-string@15.0.0" has unmet peer dependency "react@^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0". warning "workspace-aggregator-04a3b3bf-f2de-4fa4-8c4d-af65746d82b1 > @vates/event-listeners-manager > tap > @tapjs/asserts > tcompare > react-element-to-jsx-string@15.0.0" has unmet peer dependency "react-dom@^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0". warning Workspaces can only be enabled in private projects. [5/5] Building fresh packages... $ husky install husky - Git hooks installed Done in 185.69s. yarn run v1.22.19 $ turbo run build --scope xo-server --scope xo-server-'*' --scope xo-web ERROR run failed: IO error: failed to create directory `/opt/xo/xo-src/xen-orchestra/node_modules/.cache/turbo` error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
