You have to remove some entries from the pool parameters. The first step is to pull the pool's other_config parameter -- [17:31 xcp-slnqfzrh ~]# xe pool-param-get uuid=63b7154a-1a6c-8642-525e-c6abb0acxxx param-name=other-config xo:clientInfo:579c9820-a9fc-5ff0-0065-6eca7813677f: {"lastConnected":1770075085319,"networkInterfaces":{"enX0":[{"address":"192.168.1.123","netmask":"255.255.255.0","family":"IPv4","mac":"66:04:08:97:5e:e8","internal":false,"cidr":"192.168.1.123/24"},{"address":"fe80::6404:8ff:fe97:5ee8","netmask":"ffff:ffff:ffff:ffff::","family":"IPv6","mac":"66:04:08:97:5e:e8","internal":false,"cidr":"fe80::6404:8ff:fe97:5ee8/64","scopeid":2}]}}; auto_poweron: true; memory-ratio-hvm: 0.25; memory-ratio-pv: 0.25 Then you need to remove this entry using this syntax -- xe pool-param-remove uuid=<pool_uuid> param-name=other-config param-key=xo:clientInfo:<vm_uuid>

Mentioning also @Team-Hypervisor-Kernel who now manages the drivers. Maybe it's related to https://github.com/xcp-ng-rpms/microsemi-aacraid/issues/2#issuecomment-3837183087 It looks like the switch to the vendor driver instead of the kernel built-in for 8.3 (initiated by XenServer, and that we followed at the time as it was probably made in order to support newer cards) was not without drawbacks. 0nelight created this issue in xcp-ng-rpms/microsemi-aacraid open Microsemi Adaptec Series-8 Card not working in XCP-NG 8.3 #2

This filter works in XOA -- other:XenCenter.CustomFields.export_vga:"true" You can try this with curl -- curl -k -b authenticationToken=$tk "https://xoa.pc.scharp.org/rest/v0/vms?fields=name_label%2Cpower_state%2Cuuid&filter=other%3AXenCenter.CustomFields.export_vga%3A%22true%22"

@henri9813 Ahh alright, I understand now! Thanks for clarifying.

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

@Tristis-Oris There are many features missing since it's alpha now, but you can open bug tracker request on github if you want to keep track of progress for this particular feature.

@wilsonqanda Make sure to turn off "Network" in boot order. You might also want to increase the VM's root disk size when creating it. Here's a full cloud config that I used (except the ssh keys): #cloud-config hostname: {name} ssh_authorized_keys: - ssh-rsa ... disable_root: false apt: sources: xen-guest-agent: filename: xen-guest-agent.list source: deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/ append: false packages: - xen-guest-agent

I just want to add that I am seeing the same issue with Ubuntu 24.04.3. Creating a VM does work, but it crashes immediately when trying to start it for setup. I have not yet tried the approach of starting with 24.04(.00) and then upgrading to the lastest version due to lack of time. We are still using XCP-NG 8.2.1 on the server in question. If an upgrade to 8.3 solves the issue, please let us know. Reading the thread, it appears to have the same problem, though. Processor is an AMD Ryzen 9 3900X. We have not had any other issues with the system and it's been running for a few years.

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.

@MathieuRA As announced, I have now installed branch xo6/update-site-dashboard and it seems to be working. It no longer loads endlessly and shows me that I haven't configured anything yet Thank you very much!