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.

i have applied updates to my 2 amd home lab hosts. Ryzen 7700x and 7950x amd x670e mobo's. No issues to report. Windows vm migrated between hosts no isssues. No issues with windows vm booting with uefi enabled prior to update.

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

@MathieuRA

Again thank you so much for you time trying to assist with this. The script OP has responded and updated the script to work correctly now.

Again thank to all Vates staff for all the hard work you do that goes unnoticed.

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

Just install update on XOA for 6.1 and theme option is there now, and still does not stay after closing browser. Test on win 11 pc with google chrome. Lite mode\dark modes does but themes keeps defaulting to default when closing the browser.

@olivierlambert

No private browsing or incognito mode. Also tried with fresh install of fire fox same issue.

Themes are not persistent. If I set a theme Nord in dark mode. It will stay if i log out and log back in. But i close the browser and open new and log in back to default.

I am using https://github.com/ronivay/XenOrchestraInstallerUpdater script. Not sure if that has anything do with it. Cant test is XOA as these update not live in XOA yet.

Noticed this with 2 from two pc's one running windows 11 with brave browser and with Ubuntu 25.10 desktop with brave browser.

@dinhngtu said in XCP-ng Windows PV tools announcements:

Hello all,

The XCP-ng Standard VGA Display Driver for Windows v0.1.29.2216 has been released https://github.com/xcp-ng/win-xstdvga

This driver provides high-resolution consoles and resolution switching for Windows VMs running on the XCP-ng hypervisor.

This is a beta release. This driver will eventually be integrated into the main Windows PV tools package.

Driver pulled for bug fixes. Will come back soon

Test on windows 11 vm no issues to report.

@dinhngtu

I think it just have been a bad migration or the Win 11 Template did other things to the windows 10 os. Since new test vm did not show the time issues, and a fresh migration of the vim with correct template selected did not have the issues either.

I dont know but maybe there is a way to put detect the correct VM template or make note. I didnt think using the win 11 template would have caused issues since using the "wrong" template on vm creation does not have the same effect.

vm boots with no issues after retying migration with Windows 10 template.

Maybe there can be checks put in place to not apply vtpm with bios is selected? Going forward will make sure to select the current os for the template not a newer version.

test vm time was ok. I have started to remigrate over the same vm again this time making sure to select win10 for template. ETA is about 2hrs

@olivierlambert

I am doing another fresh install of windows to check the time issue.

As for the VTPM issue. Initial boot up the vm gave the warring but booted. I attempted to mount the tools iso but it would not mount correctly. So i had to shutdown the vm. When i powered it back on. It would not power on after giving the error. I deleted the vtpm and the vm booted but again gave the error and the vtpm was added again.

I can open a support tunnel if needed. This is all testing before moving critical vms at this location.

As title says VM time is ahead by 5 hours. I checked the host time via idrac (dell server) time is correct their. Via idrac I access the virtual console and verify xcp-ng host is using default ntp server info.

Other host at same location is esxi host and the vms on that host have the correct including the Windows Domain controller.

On the vm with incorrect time I see " Last successful time synchronization is 2/1/26 8:15:34 am( was correct 15 min ago) Time server local CMOS Clock. Time zone is set correctly.

Edit also note - VM was migrated from ESXI Windows 10 bios boot. Formigration i choose Windows 11 template.

When booting the vm I get this error:
Manually deleting the VTPM does not help. VM still boots but gives error.

vm.start
{
  "id": "146c5089-1e37-d3b4-83a3-8ba53a0ee2e6",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "code": "NOT_IMPLEMENTED",
  "params": [
    "Booting BIOS VM with VTPMs attached"
  ],
  "call": {
    "duration": 3868,
    "method": "VM.start",
    "params": [
      "* session id *",
      "OpaqueRef:6373a25c-a4f8-9c57-f487-23d851a3a35e",
      false,
      false
    ]
  },
  "message": "NOT_IMPLEMENTED(Booting BIOS VM with VTPMs attached)",
  "name": "XapiError",
  "stack": "XapiError: NOT_IMPLEMENTED(Booting BIOS VM with VTPMs attached)
    at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202601291557/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202601291557/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:64:5)
    at processImmediate (node:internal/timers:472:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

While shutding down the vm to add this note about VTPM, when vm booted back up time is now correct. Noted VM was rebooted and shutdown a few times from initial boot and for vm tools install.
Time is now synced with the domain controller.
Thoughts?

@Danp said in ️ XO 6: dedicated thread for all your feedback!:

@acebmxer said in ️ XO 6: dedicated thread for all your feedback!:

When creating new vm in XOv6 it does not set the correct number of cpu's....

I set 4 cpu's and after creation there is only 1. Also the ISO image is not mounted after creation.

Confirmed in my lab. I also noticed that I had to explicitly add a network adapter, which is a change from XO5.

That also. I forgot to include that about network adapter. VM does boot and appear to work correct after fixing those issues.