@dfrizon interesting i tried 24.04.2 iso and that failed but you state 24.04.1 worked?

Other thread believe this is a Ubuntu issue but as stated ISOs that have been download for some time worked in the past until recently.

Maybe related to my issues as well... https://xcp-ng.org/forum/topic/11476/error-installing-ubuntu-24.04-on-new-xcp-ng-host.?_=1761746474282

@Jeremyz1

Thank you for also confirming issue. I think Vates is aware from comment in support ticket but still waiting to hear back. I did some extensive testing last night with 7 host consiting of 3 pools.

the one time last night i was succuess i want sure if it was because i rebooted everything or because i changed from LVM group formant to traditional format during the install but was not able to replicate again.

doing some further testing ubuntu server 25.04 will install successfully. Server 24.04.3 lts will not. Desktop 24.0.2 will install successfully.

After multiple test on work server and home lab. I did managed to install ubuntu 24.04.3 by telling the installer to not format the drive in lvm group. But after trying to replicate that i was never successful.

This was tested with between 7 different host. 3 home lab and 4 at work. For at work have paid support. All host fully updated XOA - 5.111.1 XO-CE commit 87471 all host on 8.3 with no available updates.

I also test other Ubuntu templates all end with the same results.

Yeah not sure. Trying to remember when i was last successful in creating new vm with ubuntu 24.04.3. The best i can come up with is on 10/22/25 as i created a new vm within a day or two from that date.

But that fact that two separate systems showing the same problem....

@dinhngtu

Just tried Ubuntu 24.04.3 on my work servers and the install failed their as well I will open a support ticket as i have support on these servers.

Edit - Opened support ticket - Ticket#7746678

@dinhngtu

Could you tell me where and how to fetch error report?

The only other cavoite i can state but i dont think should have caused this, but just to be 100% transparent.

When i tried connecting the new host to xo-ce i did try to add the new (Intel) host to a pool that consited of AMD cpus. I also tried using the same SR for VM storage as the other pool but it would not add the SR to the new pool but only to the host.

I have since created a new SR for the vm storage but i was able to mount the ISO SR from the other pool to the new pool. That ISO SR can been see by both pools and see the contents of the SR.

As stated before i was able to success fully install Windows 11 and Ubuntu Server 25.10 with no issues. Only Ubuntu 24.xx.xx fail to install.

@manilx

success. Updated to Commit 45ef6

Ubuntu 24.04.2 installer failed as well...

Fresh download of 24.04.3 iso and same error. Also getting same error on my existing host also.

I at first i didnt try any other Linux distros as I primarily use Ubuntu. However i just tried 25.10 and that worked.

Will try again with 24.04.03 iso again or redownload the iso.... Had no problems with the iso before.

@olivierlambert

What more information is needed?

Fresh install of xcp-ng 8.3 on host. Join host to existing xo-ce as 2nd pool (single host).

Connected nfs SR for vms and connected same ISO SR from pool 1.

did secureboot-certs install on host.

Created new vm for windows 11 and installed successfully.

Create new vm for Ubuntu error doring install.

Same here also

86 Updating Xen Orchestra from '51855c22d' to 'bf705e0a9'
 87 + cd /opt/xo/xo-builds/xen-orchestra-202510281017 && yarn --network-timeout 300000 && yarn --network-timeout 300000 build
 88 yarn install v1.22.22
 89 [1/5] Validating package.json...
 90 [2/5] Resolving packages...
 91 [3/5] Fetching packages...
 92 warning bare-os@3.6.2: The engine "bare" appears to be invalid.
 93 [4/5] Linking dependencies...
 94 warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@6.1.0" has unmet peer dependency "@types/node@*".
 95 warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@6.1.0" has unmet peer dependency "typescript@>=5".
 96 warning "@typescript-eslint/eslint-plugin > ts-api-utils@1.4.3" has unmet peer dependency "typescript@>=4.2.0".
 97 warning " > @xen-orchestra/web-core@0.32.0" has unmet peer dependency "pinia@^3.0.1".
 98 warning " > @xen-orchestra/web-core@0.32.0" has unmet peer dependency "vue@~3.5.13".
 99 warning " > @xen-orchestra/web-core@0.32.0" has unmet peer dependency "vue-i18n@^11.1.2".
100 warning " > @xen-orchestra/web-core@0.32.0" has unmet peer dependency "vue-router@^4.5.0".
101 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @xen-orchestra/rest-api > inversify@6.2.2" has unmet peer dependency "reflect-      
    metadata@~0.2.2".
102 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @xen-orchestra/rest-api > swagger-ui-express@5.0.1" has unmet peer dependency       
    "express@>=4.0.0 || >=5.0.0-beta".
103 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > xo-server > typed-flash@1.0.1" has unmet peer dependency "@types/express@*".
104 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @vates/event-listeners-manager > tap > @tapjs/test > @isaacs/ts-node-temp-fork-for- 
    pr-2009@10.9.7" has unmet peer dependency "@types/node@*".
105 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @xen-orchestra/rest-api > inversify > @inversifyjs/core > @inversifyjs/reflect-     
    metadata-utils@0.2.4" has unmet peer dependency "reflect-metadata@0.2.2".
106 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @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".
107 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @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".
108 warning Workspaces can only be enabled in private projects.
109 [5/5] Building fresh packages...
110 $ husky install
111 husky - Git hooks installed
112 Done in 27.79s.
113 yarn run v1.22.22
114 $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web
115 turbo 2.5.8
116 
117 • 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-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       
118 • Running build in 21 packages
119 • Remote caching disabled
120 @xen-orchestra/qcow2:build: cache miss, executing e9d3169e4c8d9523
121 @xen-orchestra/qcow2:build: yarn run v1.22.22
122 @xen-orchestra/qcow2:build: $ tsc
123 @xen-orchestra/qcow2:build: src/disk/QcowDisk.mts(94,52): error TS2365: Operator '&' cannot be applied to types 'bigint' and 'number'.
124 @xen-orchestra/qcow2:build: error Command failed with exit code 2.
125 @xen-orchestra/qcow2:build: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
126 @xen-orchestra/qcow2:build: ERROR: command finished with error: command (/opt/xo/xo-builds/xen-orchestra-202510281017/@xen-orchestra/qcow2) /tmp/yarn--  
    1761661100812-0.024448560644666273/yarn run build exited (2)
127 @xen-orchestra/qcow2#build: command (/opt/xo/xo-builds/xen-orchestra-202510281017/@xen-orchestra/qcow2) /tmp/yarn--1761661100812-0.024448560644666273/   
    yarn run build exited (2)
128 
129  Tasks:    26 successful, 28 total
130 Cached:    0 cached, 28 total
131   Time:    7.455s
132 Failed:    @xen-orchestra/qcow2#build
133 
134  ERROR  run failed: command  exited (2)
135 error Command failed with exit code 2.
136 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
137 + rm -rf /opt/xo/xo-builds/xen-orchestra-202510281017

Just setup a new Intel host and getting this error when install Ubunut 24.04. Windows 11 installed no issues.

I did have an rtx 4070 gpu passed through to the vm when it failed. I removed the gpu and the install still failed.

@McHenry

Depending how you have Load Ballance setup they may or may not move back to the original host. If the VM has hardware passed through from the host: then the vm can not be migrated and will have to be shut down during the update and then fired back up after host has come back.

If no hardware is locked to the vm you can set the host affinity and that should lock the vm to that host. (Advance settings of the vm)

@dinhngtu
Thank you for all the help. See output below. Please let me know if you would like for me to test anything from my side.

[10:02 localhost ~]# xe vm-list --minimal | xargs -d, -Ix sh -c "echo Scanning x 1>&2; varstore-ls x" > /dev/null
Scanning ece6db75-533b-5359-1a99-28d5dc1a6912
Scanning c81f1f1b-9f95-38ec-f96e-5ce8fea073e6
unserialize_variables: Tolerating oversized data 60440 > 57344
Scanning 4fb6dee8-c251-93e6-0c20-b1c1c67351ba
Scanning 8a570993-6522-c837-0931-6fd1812dbd96
Scanning b31749b8-bc1a-0e8a-a864-50a06391592e
Scanning bf1b61d5-14ca-9f0e-7040-24c177693cea
Scanning af6eeff7-5640-28a9-dbdb-87f094a04665
Scanning 43ba924b-8bf7-4a50-b258-2e977f6f2f0c
Scanning 5a625c92-3702-2ce6-1790-39497745e83c
Scanning 9f36a8c5-c988-8546-b0f9-30ac9d0a5015
Scanning a7f5b1bb-7fe2-d0b5-5187-f29e5d4d15d7

[10:23 localhost ~]# varstore-rm c81f1f1b-9f95-38ec-f96e-5ce8fea073e6 d719b2cb-3d3a-4596-a3bc-dad00e67656f dbx
unserialize_variables: Tolerating oversized data 60440 > 57344
[11:40 localhost ~]# xe vm-list --minimal | xargs -d, -Ix sh -c "echo Scanning x 1>&2; varstore-ls x" > /dev/null
Scanning ece6db75-533b-5359-1a99-28d5dc1a6912
Scanning c81f1f1b-9f95-38ec-f96e-5ce8fea073e6
Scanning 4fb6dee8-c251-93e6-0c20-b1c1c67351ba
Scanning 8a570993-6522-c837-0931-6fd1812dbd96
Scanning b31749b8-bc1a-0e8a-a864-50a06391592e
Scanning bf1b61d5-14ca-9f0e-7040-24c177693cea
Scanning af6eeff7-5640-28a9-dbdb-87f094a04665
Scanning 43ba924b-8bf7-4a50-b258-2e977f6f2f0c
Scanning 5a625c92-3702-2ce6-1790-39497745e83c
Scanning 9f36a8c5-c988-8546-b0f9-30ac9d0a5015
Scanning a7f5b1bb-7fe2-d0b5-5187-f29e5d4d15d7
[11:40 localhost ~]#

@dinhngtu

@acebmxer Scanning on 1 host will scan the whole pool at once.

In the output you posted, there's only c81f1f1b-9f95-38ec-f96e-5ce8fea073e6 which needs fixing.

That is the same pool/host i ran the following command on.

wget https://koji.xcp-ng.org/repos/user/8/8.3/xcpng-users.repo -O /etc/yum.repos.d/xcpng-users.repo
yum update --enablerepo=xcp-ng-ndinh1 varstored varstored-tools
secureboot-certs clear

The vm being called out is the vm that would not boot that is booting now after running the above command.

Is this the command i need to run?

varstore-rm c81f1f1b-9f95-38ec-f96e-5ce8fea073e6 d719b2cb-3d3a-4596-a3bc-dad00e67656f dbx

I opened a support ticket #7746470

I get the following from different host...

Pool1 Master host:
[09:48 xcp-ng-vyadytkn ~]# xe vm-list --minimal | xargs -d, -Ix sh -c "echo Scanning x 1>&2; varstore-ls x" > /dev/null
Scanning ab9e8cde-fad8-5089-29c8-c904a810857a
Scanning d2025b59-6268-6bb9-28cd-e4812395563c
Scanning 4567b8da-3a3c-00a4-cf6b-ccdae302a645
Scanning 291f9d05-88c8-fc37-107a-368a55c649be
Scanning 88d7ba09-e65a-dd82-8d45-ec3df3e3f9d4
Scanning bcc182c6-dbb7-33c4-3e8b-c7db9b246e7b
Scanning 5a2c18ca-e9ce-abfc-8bd7-2794f94c6c3a
Scanning f4a4669a-2baf-47f2-b16a-08f60963e922
Scanning d4352870-d73c-5cda-9470-ffd7cd01e251
Scanning b0c21701-7309-dd9c-fa2a-bdc84a24565e
Scanning 342b470e-fac9-6579-f82d-2517b8de6112
Scanning 2c21c005-9230-f3f3-cdf6-2d39407b3456
Scanning 102a5ac2-ab7f-68ca-9fa1-b549d64ec4a9
Scanning c9dadc90-6fb8-eee7-d3e5-e1ae1024a77f
Scanning 5703adef-d804-6b15-ba2f-7b3357a711bb
Scanning a8858f86-ceab-2d5d-5d46-1b083c3fa399
Scanning 82b191df-a63c-4357-b618-4467f714008a

Pool 2 Master host (Problem VM)

[10:02 localhost ~]# xe vm-list --minimal | xargs -d, -Ix sh -c "echo Scanning x 1>&2; varstore-ls x" > /dev/null
Scanning ece6db75-533b-5359-1a99-28d5dc1a6912
Scanning c81f1f1b-9f95-38ec-f96e-5ce8fea073e6
unserialize_variables: Tolerating oversized data 60440 > 57344
Scanning 4fb6dee8-c251-93e6-0c20-b1c1c67351ba
Scanning 8a570993-6522-c837-0931-6fd1812dbd96
Scanning b31749b8-bc1a-0e8a-a864-50a06391592e
Scanning bf1b61d5-14ca-9f0e-7040-24c177693cea
Scanning af6eeff7-5640-28a9-dbdb-87f094a04665
Scanning 43ba924b-8bf7-4a50-b258-2e977f6f2f0c
Scanning 5a625c92-3702-2ce6-1790-39497745e83c
Scanning 9f36a8c5-c988-8546-b0f9-30ac9d0a5015
Scanning a7f5b1bb-7fe2-d0b5-5187-f29e5d4d15d7

@dinhngtu

All 4 host have the same version. They were just not updated the same way at the same time was the point i was making and that so far only 1 vm seems to be affected.

But i guess to play it self i should downgrade all 4 host.

Edit - ran the following commands on master host of pool with the vm with issue. VM now boots up.

Sorry for all the questions.

wget https://koji.xcp-ng.org/repos/user/8/8.3/xcpng-users.repo -O /etc/yum.repos.d/xcpng-users.repo
yum update --enablerepo=xcp-ng-ndinh1 varstored varstored-tools
secureboot-certs clear

Should run that above commands on all the remaining host?

Or should i run this command on any of the four host?

yum downgrade varstored-1.2.0-2.3.xcpng8.3

@dinhngtu Thank you for that reply.

Just to clarify I have 4 host. 2 host i updated to latest update once they became available to public via pool updates. The other 2 host I had to push the second beta release to get command secureboot-certs install to work. Then I pushed the rest of the update again once they became public.

So far im only seeing 1 vm having the issue on the later 2 host the had the beta updates installed. There that test PC and 1 windows server (Printsrver), xoproxy, and xoce.

Should i run those commands on all 4 host or just the later 2 with the troubled vm?

@stormi would this issue cause this behavior? VM stuck at startup...

Updated AMD Ryzen pool at home and update two Intel Dell r660 and r640 pools at work. No issues to report back.