@florent what if we use XO Proxies ?

New version release ! A new patch version of the OME appliance is now available [image: 1761814461561-606721a0-e549-47b3-8b69-55d7b233d21f-image-resized.png] What I changed: Add xen-blkfront and xen-netfront driver Add guest tool (so RAM/network is reported, soft shutdown is working) /dev/sd* is replaced by /dev/xvd* Remove grub password Change admin and root password SSH is now enabled SElinux is working correctly DHCP is enabled by default As usual, please send a DM if you want the link to the vhd Feedback is welcome !

@Greg_E Do you mean autoupdate? It's not planned just yet, but you can update them with Group Policy using our guide here: https://docs.xcp-ng.org/guides/winpv-update/ (I think you don't need the Autoreboot setting any more, but it's worth testing). You can also use other tools like SCCM, PDQ etc. The drivers themselves are production-ready, and should not cause the domain controller issue on Server 2025. As for getting the drivers signed, the certificate did cost some time and money, but the most difficult part is dealing with Microsoft (since we're signing drivers, we needed not just a certificate but also a Microsoft hardware vendor account).

I'm going to build an updated installer with an updated bnxt_en driver, as more and more servers require it.

@mlcrane You're welcome! If everything started correctly, you should see this in Xen Orchestra along with VM IP: [image: 1760383624584-9df72e83-29ba-4166-b4bd-50d75f90cc87-image.png] The previous error you had "Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider" didn't quite make sense to me since the driver package was signed by Microsoft, perhaps you were missing an important update at the time, or your VM clock was out of sync?

@rhkean note we did not publish any build yet (there is code available, but I wouldn't advise anyone to jump on it yet )

@Danp Yup, that fixed the time and the logs also. Thanks! [12:42 19] xoa@xoa:~$ timedatectl Local time: Sun 2025-10-19 12:42:55 EDT Universal time: Sun 2025-10-19 16:42:55 UTC RTC time: Sun 2025-10-19 16:42:55 Time zone: America/New_York (EDT, -0400) System clock synchronized: yes NTP service: active RTC in local TZ: no [12:42 19] xoa@xoa:~$ last reboot reboot system boot 6.1.0-40-amd64 Sun Oct 19 12:42 still running reboot system boot 6.1.0-40-amd64 Sun Oct 19 08:27 - 12:42 (04:15) reboot system boot 6.1.0-40-amd64 Sun Oct 19 08:18 - 08:26 (00:08) reboot system boot 6.1.0-40-amd64 Sat Oct 18 15:16 - 08:17 (17:01)

Good catch Dan and good decision @McHenry Even if you don't run VM, dom0 is used for VM transfer/backup/replication, so having 4GiB or RAM is a lot better in your case

@olivierlambert Thanks. --rename isn't mentioned in the KB. If I don't see something in the next week or two, I might be able to test it in a lab and then propose an update via a github fork.

@florent They are set to 30GB, but thinned provisioned, so they might be a less than that.

Thanks @MathieuRA !

@edsilber After exploring the UI, I confirmed that it's not possible to schedule a one-time cron job from the XO-5 interface. We're prioritizing the development of new features for XO-6, so we'll take your suggestions regarding scheduling into account for the new interface. I propose an alternative: using the REST API to run schedules by creating your own execution script (if you are on linux: https://www.veeble.com/kb/scheduling-one-time-jobs-in-linux-using-at-command/). The REST API link is: {your-xo-url}/rest/v0/docs/#/schedules Please feel free to contact me if you have any further questions.

@Cyrille is back next week

@flakpyro said in VM start stuck on "Guest has not initialized the display (yet).": @dinhngtu said in VM start stuck on "Guest has not initialized the display (yet).": You must run secureboot-certs clear if you're updating from 1.2.0-2.4 or 1.2.0-3.1 and have previously run secureboot-certs install with the above versions installed. Should we run this before installing the update or after 1.2.0-3.2 has been installed? You should run that preferably after updating all hosts. @lukasz_s said in VM start stuck on "Guest has not initialized the display (yet).": @dinhngtu thanks for advice i've upgraded varstored and varstored-tools: rpm -qa | grep varstored varstored-1.2.0-3.2 varstored-tools-1.2.0-3.2 than i've cleared varstore with secureboot-certs clear should taht folder contain more files ? ls /usr/share/varstored/ KEK.uth PK.auth db.auth what about dbx file ? That file is not shipped with varstored nor needed for now. We're validating the final 1.2.0-3.2 and preparing our guidance for the official update.

@lsouai-vates Thanks for the response. I was just looking for a way to create a full screen display for a NOC, without requiring interactive login. Sounds like that's not possible at the moment?

@olivierlambert thank you very much, you are helpful

Additional info: uuid ( RO) : 127a8a7b-e277-27dc-802f-7f779676e18e name-label ( RO): Async.VBD.eject name-description ( RO): subtask_of ( RO): <not in database> subtasks ( RO): resident-on ( RO): 74e89397-c334-43f5-8322-5331c31ae368 status ( RO): pending progress ( RO): 0.000 type ( RO): <none/> result ( RO): created ( RO): 20251106T19:44:14Z finished ( RO): 19700101T00:00:00Z error_info ( RO): allowed_operations ( RO): current_operations ( RO): other-config (MRW): debug_info:cancel_points_seen: 1

@florent yeah that is what i did deploy xo-ce while waiting for a response. I still have 3 more vms to migrate. I so i will continue this route for the migration. Thank you for the confirmation.

@ph7 huh, that is weird. I'll try to troubleshoot more over the weekend. Thanks for pointing it out. @olivierlambert said in Upgraded RAM, It get's detected but not used. Any ideas?: I would first upgrade the BIOS of the motherboard. Consumer grade hardware is pretty buggy in general when you are using "advanced" features, sadly. That's the first thing i tried, no luck unfortunately

@ph7 that's fine, keep on testing our new XO-6, we are very happy with all our community feedback