Posts made by ashinobi

Hi, Everyone.

I am trying to learn docker and decided to spinup a windows 10 22h2 in xcp-ng. When I install docker desktop, it was able to finish the installation and require a restart. After the restart, Windows 10 won't able to boot and is stuck in Diagnosing PC.

I have tried installing XenServer VM tool version 9.3.3 or no VM tool but same issue. I have also tried updating the VM first to latest patch and installing Docker Desktop without Windows patch but still the same problem.

I have also tried enabling/disabling Nested Virtualization but still the same problem.

I have used VMWare Workstation 17.0 and used the same Windows 10 22h2 installer with VMWare tools installed and no patches installed and the installation finishes and was able to reboot to Windows.

Please advice on what should I do, maybe something I have overlooked or miss that is why this is not working in XCP-NG.

The XCP-NG server details as follow:

[05:13 home-hypervisor ~]# lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: XCP-ng
Description: XCP-ng release 8.2.1 (xenenterprise)
Release: 8.2.1
Codename: xenenterprise

it is running on AMD EPYC 3251 SoC Processor, 8 Core/16 Thread

@MathieuRA

Thanks for doing the fix, I have tested this and I confirm it is working. I am able to migrate VMGuest to a different host by ticking the check box in the vmlist.

@Danp

That's fine, thank you for the help. I still have the migrate option when I go to the vm settings itself. Thanks for trying to help with my small issue and the information you shared about the use of git command

@Danp said in Getting errors when migrating 4 out 5 VMGuest:

checkout xo5/fix-bulk-migration

When I did "git pull" I get the following:

root@xen-orchestra:/opt/xo/xo-src/xen-orchestra# git pull
hint: You have divergent branches and need to specify how to reconcile them.
hint: You can do so by running one of the following commands sometime before
hint: your next pull:
hint:
hint:   git config pull.rebase false  # merge (the default strategy)
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
fatal: Need to specify how to reconcile divergent branches.

Do I need to merge any repository or ignore this?

@Danp

That is weird, if that is still from the wrong branch because when I ran the script it showed it is trying to download from the branch I specified:

I will try your method, unfortunately my backups for my VM Guest just kicked in so I'll update you once the backup has finished and I was able to run the command you have provided

Regards

@Danp

Unfortunately I am still having the same issue. I have rebooted XO and both host as well:

@Danp

do I change "Branch=MASTER" to "Branch=xo5/fix-bulk-migration"? to make it work?

@Danp

As you know that I am using XenOrchestraInstallerUpdater script so I will be dependent on its config file. Base on the config file the installation is located at /opt/xo

# Base dir for installation and future updates
INSTALLDIR="/opt/xo"

so I assume that is the directory where XO is running and if I go to /opt directory there is only one folder in there which is "xo"

admin@xen-orchestra:/opt$ ls -ltrh
total 4.0K
drwxr-xr-x 4 root root 4.0K Feb  9 06:25 xo

If I check the status of "xo-server.service" it is pointing to the "/opt/xo" where it is running

admin@xen-orchestra:/opt$ systemctl status xo-server.service
● xo-server.service - XO Server
     Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2024-02-09 06:25:48 ACDT; 4h 51min ago
   Main PID: 4769 (node)
      Tasks: 11 (limit: 9359)
     Memory: 163.9M
        CPU: 7min 13.551s
     CGroup: /system.slice/xo-server.service
             └─4769 node /opt/xo/xo-server/dist/cli.mjs

Feb 09 08:45:48 xen-orchestra xo-server[4769]:   network: 'PrivateNetwork2',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   host: 'xcp-ng-Server2',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   pool: ''
Feb 09 08:45:48 xen-orchestra xo-server[4769]: }
Feb 09 08:45:48 xen-orchestra xo-server[4769]: 2024-02-08T22:15:48.527Z xo:xo-server:sdn-controller:private-network INFO Host added {
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   privateNetwork: '0ad66652-81c9-4c67-b484-286a1621c23e',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   network: 'PrivateNetwork1',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   host: 'xcp-ng-Server2',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   pool: ''
Feb 09 08:45:48 xen-orchestra xo-server[4769]: }

@Danp

Here is what I got from running "rev-parse --abbrev-ref HEAD"

admin@xen-orchestra:/opt/xo/xo-src/xen-orchestra$ sudo git rev-parse --abbrev-ref HEAD
[sudo] password for admin:
xo5/fix-bulk-migration

It shows that I am using the alternate branch which is the "fix-bulk-migration"

@Danp

In regards to migration to vm screen, I confirm that is still working.

In regards to the screenshot of the about page:

I saw this morning there were 12 commits so I just updated to it as well.

@olivierlambert

Hi, apologies for the late reply, I did restart XO and still have the same problem. Also just to make sure I have restarted both XCP-NG host as well and perform the migrate and still has the same problem.

[05:27 home-hypervisor ~]# uptime
 05:51:29 up 27 min,  1 user,  load average: 0.41, 0.37, 0.20
[05:51 home-hypervisor ~]# hostname
home-hypervisor


[05:44 xcp-ng-Server2 ~]# uptime
 05:51:25 up 15 min,  1 user,  load average: 0.90, 0.64, 0.35
[05:51 xcp-ng-Server2 ~]# hostname
xcp-ng-Server2

rrivera_admin@xen-orchestra:~$ uptime
 05:51:20 up 6 min,  1 user,  load average: 0.13, 0.19, 0.11
rrivera_admin@xen-orchestra:~$ hostname
xen-orchestra

@olivierlambert

No, but I am rebooting it now. I'll update you once the server is up and tested the migration.

@Danp

Thanks. I have successfully run it

root@xen-orchestra:/opt/xo/xo-src/xen-orchestra# yarn; yarn build
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
$ husky install
husky - Git hooks installed
Done in 4.22s.
yarn run v1.22.19
$ turbo run build --scope xo-server --scope xo-server-'*' --scope xo-web
• Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
• Running build in 22 packages
• Remote caching disabled
 WARNING  Failed to check if we can skip restoring outputs for xo-lib#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-auth-saml#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-transport-xmpp#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-remote-parser#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-auth-github#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-auth-google#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-transport-slack#build: GrpcFailure(Cancelled). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-transport-icinga2#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-transport-email#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-collection#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache

 Tasks:    25 successful, 25 total
Cached:    0 cached, 25 total
  Time:    4m46.846s

Done in 287.74s.

perform the migration test but I am still having the same error message.

@Danp

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.

@Danp

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.lock

I 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

@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 git

I have installed XO using XenOrchestra Installer Updater script, would this cause the problem?

@MathieuRA

Is the fix part of XO commi 2498a? If not how can I download the update. My apologies if that I am not familiar.

@MathieuRA

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?

@olivierlambert

I did that as mention 3 of the vm's doesn't have iso mounted and it still experience the problem.