Confirm commit 1a7b5 backups completed successfully.

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

@stormi

Thanks for the reply back. Update when sucessfull. Windows Server 2025 iso now properly installs.

At work I was not able to install default certs for UEFI due to one failing to download. Run these updates and I was able to successfully install the certs to the host.

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

@dinhngtu Well those directions didnt work as I was unable to locate the setup.exe file in any of the vmware directories. I asked google ai how to force uninstall the vmware tools and started to follow those directions of maunally deleting the services and folder and registry entries. However the vm pysically became unbootable. It would not show the logo of the bios starting up. The vm would appear to be starting up but no console screen would load. I even tried to restore from a backup taken two days ago. That VM started up and of coarse windows wanted todo updates and vm became unbootable again.

I deleted all previous vm and did a fresh migration. This time i did remove the tools prior to the migration. VM is back working.

@Pilow

Did dirty upgrade left all boxes checked and vm is setup to update drivers via windows update....

I have rebooted vm and restarts no issues.

@dinhngtu same mine where two fresh VMs fresh install of server 2025. Older iso works newer iso does not. For me the newer iso the system rebooted 2 maybe 3 times then crashed to a hard power off of the vm.

Again no xen tools installed as os never finished installing on a fresh vm. no OS upgrade.

as @MBNext stated disabling Purge snapshot data when using CBT worked for me.

Correction XCP-NG backups are Application aware... Just not accessible from the right click menu on the backup. If you click from the menu bar at top it is available...

@Pilow

I thought restarting tool stack affected both host? Either way did try that but on host 1 originally. So i restarted on host 2 (where problem is). still no locked. I rebooted host 2 and that seem to do the trick. Took a few min for garbage collection to complete. All clean now.

Thanks.

@paco Go to the vm in question and go to the storage and disable the CBT. Once migrated you can reneable or the backup job will reenable.

I had issues i could not move to new SR when CBT was enabled.

FYI we have the Broadcom NetXtreme Gigabit Ethernet (BCM5720) in Dell R660 and Broadcom Adv. Dual 10GBASE-T Ethernet in Dell r640.

Currently have no issues with ether nic in XCP-NG 8.3

@pdonias

I can confirm with @probain with UI bug.

If i start new vm from template and select the template Ubuntu 24.04.3 to start.

Then switch to any other template (pic below shows Rocky Linux template) the storage name does update by adding *_qxaj at the end but still remains named ubuntu not rocky linux. Also see the description bug appear.

If i switch back to the original template (second template switch) the storage name drops the _qxaj and description bug goes away.

@marcoi check with who wrote your script to install XO from sources.

https://github.com/ronivay/XenOrchestraInstallerUpdater - this has a option in config file to enable v6 during install/upgrade.

or try -

cd /opt/xo/xo-web
yarn run turbo run build --filter @xen-orchestra/web

@olivierlambert Thank you for the reply. There was a thread on here about the iso not being mounted properly and I commented about having power off the vm and back and it will load the iso.

This is specifically true with the 0.4.0 for linux. Image pulled from the XO Hub will not mount the ios if the vm is powered on. There is Yellow Explanation mark next to it. Power off vm and power on vm iso is ok. Reboot vm does not let the ios to work.

@bvitnik thanks didnt know about the purge option. It didnt show on sudo apt --help

Are the new rust xen-guest-agent ready for production? Should I stay with the traditional xe-guest-utilities on the guest tools iso?
While trying to uninstall the xen-guest-agent and install the xe-guest-utilities I ran into this...

Is dpkg -l | grep xe not the proper way to detect what tools is installed?

test@Test:~$ dpkg -l | grep xe
ii  byobu                           6.11-0ubuntu1                           all          text window manager, shell multiplexer, integrated DevOps environment
ii  libxext6:amd64                  2:1.3.4-1build2                         amd64        X11 miscellaneous extension library
ii  plymouth                        24.004.60-1ubuntu7.1                    amd64        boot animation, logger and I/O multiplexer
ii  plymouth-theme-ubuntu-text      24.004.60-1ubuntu7.1                    amd64        boot animation, logger and I/O multiplexer - ubuntu text theme
ii  publicsuffix                    20231001.0357-0.1                       all          accurate, machine-readable list of domain name suffixes
ii  python3-pyparsing               3.1.1-1                                 all          alternative to creating and executing simple grammars - Python 3.x
ii  screen                          4.9.1-1build1                           amd64        terminal multiplexer with VT100/ANSI terminal emulation
ii  tmux                            3.4-1ubuntu0.1                          amd64        terminal multiplexer
ii  whiptail                        0.52.24-2ubuntu2                        amd64        Displays user-friendly dialog boxes from shell scripts
ii  xe-guest-utilities              7.30.0-13                               amd64        Virtual Machine Monitoring Scripts
rc  xen-guest-agent                 0.4.0                                   amd64        Guest Agent for Xen-based virtual machines
test@Test:~$ sudo apt remove xen-guest-agent
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'xen-guest-agent' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
test@Test:~$ dpkg -l | grep xe
ii  byobu                           6.11-0ubuntu1                           all          text window manager, shell multiplexer, integrated DevOps environment
ii  libxext6:amd64                  2:1.3.4-1build2                         amd64        X11 miscellaneous extension library
ii  plymouth                        24.004.60-1ubuntu7.1                    amd64        boot animation, logger and I/O multiplexer
ii  plymouth-theme-ubuntu-text      24.004.60-1ubuntu7.1                    amd64        boot animation, logger and I/O multiplexer - ubuntu text theme
ii  publicsuffix                    20231001.0357-0.1                       all          accurate, machine-readable list of domain name suffixes
ii  python3-pyparsing               3.1.1-1                                 all          alternative to creating and executing simple grammars - Python 3.x
ii  screen                          4.9.1-1build1                           amd64        terminal multiplexer with VT100/ANSI terminal emulation
ii  tmux                            3.4-1ubuntu0.1                          amd64        terminal multiplexer
ii  whiptail                        0.52.24-2ubuntu2                        amd64        Displays user-friendly dialog boxes from shell scripts
ii  xe-guest-utilities              7.30.0-13                               amd64        Virtual Machine Monitoring Scripts
rc  xen-guest-agent                 0.4.0                                   amd64        Guest Agent for Xen-based virtual machines
test@Test:~$ 

@bvitnik that worked.

@bvitnik said in Custom config / cloud-init:

@acebmxer Did you do:

cloud-init clean --logs --seed

before converting the VM to template?

Also, network configuration is not part of the cloud-config (aka user data). In XO, there is a separate field called "Network config" where it should be specified. See examples at the end of the guide I pasted earlier. network: key should also be removed (commented in the examples).

besides getting it working on fresh vm from the ubuntu template from the Hub. I do have that command in script to prepare the vm to create a template from it. AI says this will cause the vm not to recreate the 50-cloud-init.yaml file. So how do I work around that also.

@bvitnik
This is creating new vm from Hub template. If i try the below network config the VM hangs on boot. Think previously it would eventually boot but have not networking as stated previously.

#cloud-config
# network:                                                                                                                                              
   version: 2                                                                                                                                          
   ethernets:
    enX0:
      dhcp4: true
      dhcp6: false
      set-name: "enX0"

This is copy pasted from the link you provided about additional infomation to add to documentation. does not show network: commented out. When i use this with ips corrected to my network the vm boots fast but again still no networking. Even if i comment out network. Still no networking. I have to leave blank during vm creation. Can you past your working network config?

#cloud-config
network:
  version: 2
  ethernets:
    eth0:
      dhcp4: false
      addresses:
        - 10.0.2.6/27
      gateway4: 10.0.2.1
      nameservers:
        addresses:
          - 10.0.2.1
          - 1.1.1.1

EDIT -

This is a working config for new vm from Ubuntu Hub template. VM boots and gets IP address. Its not much different then my original. I dont know. Still learning this stuff.

network:
  version: 2
  ethernets:
    enX0:      # or whatever your interface name is
      dhcp4: true

Edit -2 while the above works for dhcp the below does not work for static. VM does not get static ip

network:
  version: 2
  ethernets:
    enX0:      # or whatever your interface name is
      dhcp4: false
      addresses: - 10.100.10.206/24
      gateway4: 10.100.10.254
      nameservers:
          addresses:
               - 10.100.10.254
               - 1.1.1.1