@mguimond
Not sure how old your XO is but this is the current Commit. Master, commit 5349f. Suggest try updating and try again. Maybe someone from Vates will have more information.

@WorkAccount1000

Prior to myself finding that option in the config file use to run this command that worked as well..

cd /opt/xo/xo-web

sudo yarn run turbo run build --filter @xen-orchestra/web

@WorkAccount1000

Reach out to who's script you are using for deploying XO from sources.

This script - https://github.com/ronivay/XenOrchestraInstallerUpdater there is an option in the config file to enable XOv6. There are concerns with not being fully ready to its disabled by default. I currently have not any issues related to that.

@bvitnik thanks for that info. There is so much to learn with linux. Not that there is alot to learn with windows. I am still learning new stuff every day but still know just enough to get myself in trouble with Linux.

@Pilow I try the dhcp4 vs dhcp

So I started with a Ubuntu 24.4 image from XOA hub. I create a new vm from that image with my cloud config from above. I start the vm up. Once booted I shut it down and remove the Cloud config drive. leaving 1 single os drive. I boot the vm up and fully update the vm and install a few minor tweaks. Then shut the vm down. Networking is configure dhcp.

If convert this newly created vm to a template. Then create another vm from this template. Even though the VM is generating a new mac address when the vm boots its still getting / using the same ip from vm used to create the template.

If i put either network configs in during vm creation from new template i get no ip address. I cant log into console because the user does not have a password. I have tried to put password: userspassword in the config but that does not work.

network:
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
      - type: dhcp

or

network:
  version: 2
  ethernets:
    eno1:
      dhcp4: true

Think I figured it out. first i was using the wrong key. A lot of going back and forth trying new keys forgot to swap back to original...

new config...

#cloud-config
hostname: {name}
users:
  - name: newusername
    gecos: New User
    sudo: ALL=(ALL) NOPASSWD:ALL
    groups: users, admin
    shell: /bin/bash
    ssh_authorized_keys:
      - ssh-ed25519 AAAAC3....18ZbA

Any suggestions should I not use something in the above config if the server was in production?

So i am trying to learn how to use the Custom config / cloud-init for ubuntu.

If I add my ssh-key to my user account in Xen orchestra (XOA or XO-CE) I can select that during the vm creation and that works but the VM is stuck with the username ubuntu. I would to change that.

I am not sure if I am messing up the user creation or the ssh-key as i am not able to log in do to authentication error.

My config ---

#cloud-config
hostname: {name}
users:
  - newusername
ssh_authorized_keys:
      - ssh-rsa AAAAB3NzaC1.....XbZH6muQrfegKoTsuw== Generated By Termius

The above is not my actual key. In the key saved in user profile stops before the"==" and as stated that key works. So i assume if I correct the config to remove the "==" and after that key should work as well. So my assumption is the user name is the issue.

I would like to make the username to my desire but have the same permission as the user account ubuntu has when just inserting ssh-key.

@SethNY

Unless i am missing something here.

xcp-ng host 8.3
From windows 11 25h2 update. no license key installed yet.

PS C:\Users\> wsl
The Windows Subsystem for Linux is not installed. You can install by running 'wsl.exe --install'.
For more information please visit https://aka.ms/wslinstall

Press any key to install Windows Subsystem for Linux.
Press CTRL-C or close this window to cancel.
This prompt will time out in 60 seconds.
The requested operation requires elevation.
Downloading: Windows Subsystem for Linux 2.6.1
Installing: Windows Subsystem for Linux 2.6.1
Windows Subsystem for Linux 2.6.1 has been installed.
Installing Windows optional component: VirtualMachinePlatform

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26200.7171

Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.
The requested operation is successful. Changes will not be effective until the system is rebooted.
Windows Subsystem for Linux has no installed distributions.
You can resolve this by installing a distribution with the instructions below:

Use 'wsl.exe --list --online' to list available distributions
and 'wsl.exe --install <Distro>' to install.
PS C:\Users\> wsl --version
WSL version: 2.6.1.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.66
MSRDC version: 1.2.6353
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26200.7171
PS C:\Users\> wsl --update
Checking for updates.
The most recent version of Windows Subsystem for Linux is already installed.

Edit - while it let me install wsl 2 it wont let me install ubuntu 22.04 error about the virtualization. Currently have nested virtualization disabled at the vm settings.

wsl --install ubuntu-22.04
Launching Ubuntu 22.04 LTS...
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/enablevirtualization
Press any key to continue...

@tsukraw

Wait for vates to reply for more technical information. Take a look at this - https://xcp-ng.org/blog/2025/10/16/qcow2-beta-announcement/

you are at 1.5tb so I think you should be ok with out qcow2 support. I personal had some performance and other issues with it and disable as I didnt need 2tb support yet.

@olivierlambert Yes I previously was. now back on VHD. This was in my home lab, not work enviorment.

@Danp

Not sure if related or not but I ended up removing the beta qcow2 support. Even though after recreating my SR I was still seeing other odd behaviors.

Backup progress was not shown on vms when qcow2 support enabled.
CBT delete snapshots were having issues
With CBT disabled snapshots were adding up and coalescing issues.

I didn't do any official speed testing but overall performance seemed slower.

After disabling qcow2 support all seems better now. Backup process is able to be monitored, CBT backups working as expected and performance is back.

@joeymorin

If its any help check out my post - https://xcp-ng.org/forum/topic/11525/unhealthy-vdis/4

Check out this post for cert error not sure if its related- https://xcp-ng.org/forum/topic/9083/stunnel-sdn-cert-error-when-adding-host-to-pool/7?_=1762983691777

@stevewest15 will need a reply from @olivierlambert or other vates member. my screenshot was from a Dell r660 but also have Dell r640 that work as well... Just double check your host is fully updated with bios / idrac firmware along with xcp-ng host and your XOA or XO-CE.

@stevewest15

As @olivierlambert stated if its support it will just appear...

They are working adding support for HPE and Supermicro servers. This was from Dell server.

It seams migration back to new SR is very very slow. in the 1 - 2 hr mark when the initial migration with converting vhd to qcow2 was quicker in the 20 - 40 min mark.

@Danp it appears the unhealthy vdi are no longer appearing, long after backup completes.

Just to eliminate any issues with the SR i decided to migrate all the vms off that SR onto a tmp SR and recreate the original SR. I am in the process of migrating them back to the newly created SR.

I ran those above command again and this is the output now..

[10:31 xcp-ng-qhfpcnmb ~]# cat /var/log/SMlog | grep -i exception
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] Raising exception [101, The request is missing the serverpath parameter]
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] ***** generic exception: sr_probe: EXCEPTION <class 'xs_errors.SROSError'>, The request is missing the serverpath parameter
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] ***** NFS VHD and QCOW2: EXCEPTION <class 'xs_errors.SROSError'>, The request is missing the serverpath parameter
[10:32 xcp-ng-qhfpcnmb ~]# cat /var/log/SMlog | grep -i error
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] ***** generic exception: sr_probe: EXCEPTION <class 'xs_errors.SROSError'>, The request is missing the serverpath parameter
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]     raise xs_errors.XenError('ConfigServerPathMissing')
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] ***** NFS VHD and QCOW2: EXCEPTION <class 'xs_errors.SROSError'>, The request is missing the serverpath parameter
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]     raise xs_errors.XenError('ConfigServerPathMissing')
[10:32 xcp-ng-qhfpcnmb ~]# grep -i coales /var/log/SMlog
Nov  8 09:23:26 xcp-ng-qhfpcnmb SM: [566243] We have secondary for 2944d0bb-11fe-4a3d-8272-6b3354d07342, blocking leaf coalesce
Nov  8 09:23:48 xcp-ng-qhfpcnmb SM: [567385] We have secondary for 01b89462-cae3-4657-b0f1-83eee08dce66, blocking leaf coalesce
Nov  8 09:35:29 xcp-ng-qhfpcnmb SMGC: [576746] Got other-config for 2944d0bb(64.000G/136.000K?)[vhd]: {'leaf-coalesce': 'false'}
Nov  8 09:35:29 xcp-ng-qhfpcnmb SMGC: [576746] Leaf-coalesce disabled for 2944d0bb(64.000G/136.000K?)[vhd]
Nov  8 09:35:34 xcp-ng-qhfpcnmb SMGC: [576990] Coalesced size = 5.992G
Nov  8 09:35:34 xcp-ng-qhfpcnmb SMGC: [576990] Leaf-coalesce candidate: 053f72af(64.000G/80.000K/0)[qcow2]
Nov  8 09:35:34 xcp-ng-qhfpcnmb SMGC: [576990] Leaf-coalescing 053f72af(64.000G/80.000K/0)[qcow2] -> *b99d6033(64.000G/23.931G/23.926G)[qcow2]
Nov  8 09:35:34 xcp-ng-qhfpcnmb SMGC: [576990]   Running COW coalesce on 053f72af(64.000G/80.000K/0)[qcow2]
Nov  8 09:35:36 xcp-ng-qhfpcnmb SMGC: [576990] Removed leaf-coalesce from 053f72af(64.000G/23.931G/23.926G)[qcow2]
Nov  8 09:46:08 xcp-ng-qhfpcnmb SMGC: [584997] Got other-config for 01b89462(128.000G/1.705G?)[vhd]: {'leaf-coalesce': 'false'}
Nov  8 09:46:08 xcp-ng-qhfpcnmb SMGC: [584997] Leaf-coalesce disabled for 01b89462(128.000G/1.705G?)[vhd]
Nov  8 09:46:10 xcp-ng-qhfpcnmb SMGC: [585279] Got other-config for 01b89462(128.000G/1.705G?)[vhd]: {'leaf-coalesce': 'false'}
Nov  8 09:46:10 xcp-ng-qhfpcnmb SMGC: [585279] Leaf-coalesce disabled for 01b89462(128.000G/1.705G?)[vhd]
Nov  8 09:46:26 xcp-ng-qhfpcnmb SMGC: [585740] Coalesced size = 19.549G
Nov  8 09:46:26 xcp-ng-qhfpcnmb SMGC: [585740] Leaf-coalesce candidate: 0541a5bc(128.000G/117.867M/89.189M)[qcow2]
Nov  8 09:46:26 xcp-ng-qhfpcnmb SMGC: [585740] Leaf-coalescing 0541a5bc(128.000G/117.867M/89.189M)[qcow2] -> *906ab99e(128.000G/77.916G/77.904G)[qcow2]
Nov  8 09:46:28 xcp-ng-qhfpcnmb SMGC: [585740] Coalescing parent *2e1779a9(128.000G/117.883M/89.193M)[qcow2]
Nov  8 09:46:28 xcp-ng-qhfpcnmb SM: [585740] Remote coalesce for /var/run/sr-mount/5ca7d722-6820-6762-d872-b65f6fc7f3f8/2e1779a9-06a0-44cc-bd83-172c82f15f42.qcow2
Nov  8 09:46:28 xcp-ng-qhfpcnmb SM: [586271] DAMS: Calling remote coalesce with: {'path': '/var/run/sr-mount/5ca7d722-6820-6762-d872-b65f6fc7f3f8/2e1779a9-06a0-44cc-bd83-172c82f15f42.qcow2', 'vdi_type': 'qcow2'}
Nov  8 09:46:37 xcp-ng-qhfpcnmb SM: [586271] DAMS: Remote coalesce returned 137438953472
Nov  8 09:46:38 xcp-ng-qhfpcnmb SMGC: [585740] Coalesce summary
Nov  8 09:46:39 xcp-ng-qhfpcnmb SMGC: [585740]   Running COW coalesce on 0541a5bc(128.000G/25.891M/24.750M)[qcow2]
Nov  8 09:46:41 xcp-ng-qhfpcnmb SMGC: [585740] Removed leaf-coalesce from 0541a5bc(128.000G/77.916G/77.904G)[qcow2]
Nov  8 09:47:48 xcp-ng-qhfpcnmb SM: [587542] Aborting GC/coalesce
Nov  8 09:47:56 xcp-ng-qhfpcnmb SM: [587621] Aborting GC/coalesce
Nov  8 09:47:56 xcp-ng-qhfpcnmb SM: [587621] Aborting GC/coalesce
Nov  8 09:53:48 xcp-ng-qhfpcnmb SM: [591030] Aborting GC/coalesce
Nov  8 09:54:52 xcp-ng-qhfpcnmb SM: [592147] We have secondary for 053f72af-867b-499e-8123-4c6897737948, blocking leaf coalesce
Nov  8 09:59:14 xcp-ng-qhfpcnmb SMGC: [595908] Got other-config for 053f72af(64.000G/193.000K/0)[qcow2]: {'leaf-coalesce': 'false'}
Nov  8 09:59:14 xcp-ng-qhfpcnmb SMGC: [595908] Leaf-coalesce disabled for 053f72af(64.000G/193.000K/0)[qcow2]
Nov  8 09:59:18 xcp-ng-qhfpcnmb SMGC: [596131] Coalesced size = 5.991G
Nov  8 09:59:18 xcp-ng-qhfpcnmb SMGC: [596131] Leaf-coalesce candidate: 406997bc(64.000G/80.000K/0)[qcow2]
Nov  8 09:59:18 xcp-ng-qhfpcnmb SMGC: [596131] Leaf-coalescing 406997bc(64.000G/80.000K/0)[qcow2] -> *e7281aae(64.000G/23.935G/23.926G)[qcow2]
Nov  8 09:59:18 xcp-ng-qhfpcnmb SMGC: [596131]   Running COW coalesce on 406997bc(64.000G/80.000K/0)[qcow2]
Nov  8 09:59:20 xcp-ng-qhfpcnmb SMGC: [596131] Removed leaf-coalesce from 406997bc(64.000G/23.935G/23.926G)[qcow2]
Nov  8 10:00:29 xcp-ng-qhfpcnmb SM: [597528] We have secondary for f8a9567f-66a3-4fdc-9313-711d13851cb6, blocking leaf coalesce
Nov  8 10:06:28 xcp-ng-qhfpcnmb SM: [602617] We have secondary for 0b3d1b69-0936-4951-be61-3939a96cb462, blocking leaf coalesce
[10:32 xcp-ng-qhfpcnmb ~]# grep -A 5 -B 5 -i exception /var/log/SMlog
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] _testHost: Testing host/port: 10.100.2.183,2049
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] scanning2 (target=10.100.2.183)
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] scanning
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] ['/usr/sbin/showmount', '--no-headers', '-e', '10.100.2.183']
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   pread SUCCESS
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] Raising exception [101, The request is missing the serverpath parameter]
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] lock: released /var/lock/sm/sr
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] ***** generic exception: sr_probe: EXCEPTION <class 'xs_errors.SROSError'>, The request is missing the serverpath parameter
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   File "/opt/xensource/sm/SRCommand.py", line 113, in run
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]     return self._run_locked(sr)
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   File "/opt/xensource/sm/SRCommand.py", line 163, in _run_locked
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]     rv = self._run(sr, target)
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   File "/opt/xensource/sm/SRCommand.py", line 345, in _run
--
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   File "/opt/xensource/sm/NFSSR", line 177, in probe
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]     self.validate_remotepath(True)
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   File "/opt/xensource/sm/NFSSR", line 119, in validate_remotepath
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]     raise xs_errors.XenError('ConfigServerPathMissing')
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827] ***** NFS VHD and QCOW2: EXCEPTION <class 'xs_errors.SROSError'>, The request is missing the serverpath parameter
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   File "/opt/xensource/sm/SRCommand.py", line 392, in run
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]     ret = cmd.run(sr)
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   File "/opt/xensource/sm/SRCommand.py", line 113, in run
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]     return self._run_locked(sr)
Nov  8 09:53:39 xcp-ng-qhfpcnmb SM: [590827]   File "/opt/xensource/sm/SRCommand.py", line 163, in _run_locked

@blueh2o

Try to shut down the vm. I have had issues were i was not able to mount a tools iso to vm or some times eject unless the vm was powered off. After vm tools installed usually didn't have any issues.

@Danp

I also had to cut alot of the bottom of that log just to post it.