@ph7 that's fine, keep on testing our new XO-6, we are very happy with all our community feedback 
Product team
Private
Posts
-
RE: XOv6, New VM not same as XO-Lite
-
RE: Schedule a single non repeating task
@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.
-
RE: Schedule a single non repeating task
@edsilber Hello and thank you for your help! I'm currently reviewing the user interface and discussing it with the XO team. I'll get back to you as soon as I've found the best way to help you…
-
RE: XOv6, New VM not same as XO-Lite
@ph7 XO-Lite and XO-6 are 2 differents projects, so no they are not using the same code, even if the UI looks similar... ^^"
-
RE: XOv6, New VM not same as XO-Lite
@ph7 hello and thanks for your reply.
The current XO-6 form is not yet finalized... we are still working on it. An informational message will be added to indicate what will and will not be possible to manage in this version of the form. The final version is planned for early 2026, and we are working as quickly as possible to provide all users with the best possible experience on this VM creation form.
We apologize for any inconvenience and will do our best to minimize it.
-
RE: XCP-ng 8.3 updates announcements and testing
@flakpyro Thanks for letting us know. I suppose there was a mirror that was not ready yet, or had a transient issue, and unfortunately XOA's rolling pool update feature is not very resilient to that at the moment.
-
RE: XCP-ng 8.3 updates announcements and testing
IMPORTANT NOTICE!After publishing the updates, we discovered a very nasty bug when using the UEFI certificates that we distribute. Long story short, they're too big, and there's only limited space (57K), and combined to a preexisting bug in varstored, this will cause the VM to stop booting after Windows or any other OS attempts to append to the DBX (revocation database).
We pulled the
varstoredupdate, but those who updated can be affected.There are conditions for the issue:
- Existing VMs are not affected, unless you propagated the new certs to them
- New VMs are affected only if you never installed UEFI certs to the pool yourself (through XOA or
secureboot-certs install), or cleared them usingsecureboot-certs clearin order to use our default certificates.
If you have the affected version of
varstored(rpm -q varstoredyieldsvarstored-1.2.0-3.1.xcpng8.3) :- on every host, downgrade it with
yum downgrade varstored-1.2.0-2.3.xcpng8.3. No reboot or toolstack restart required. - if you have affected UEFI VMs, that is VMs that meet the conditions above but are not broken yet, don't install updates, turn them off, and fix them by deleting their DBX database: https://docs.xcp-ng.org/guides/guest-UEFI-Secure-Boot/#remove-certificates-from-a-vm. This has to be done when the VM is off. Your OS will add its own DBX afterwards.
- If you already have broken VMs (this warning reaching you too late), revert to a snapshot or backup. Other ways to fix them will require a patched
varstoredcurrently in the making.
-
RE: Display Dashboard in NOC Using Authentication Token
@kagbasi-ngc hello! For now the token has to be added in cookie, why do you need to send it by url?
-
RE: XCP-ng 8.3 updates announcements and testing
@acebmxer said in XCP-ng 8.3 updates announcements and testing:
@stormi
How to revert changes if needed to? and/or how to switch back to normal repo?The command only enables the testing repositories for the time of the update, so no need to disable them afterwards.
Reverting changes can be done with
yum downgrade, but it's not always doable. XAPI updates can come with an upgrade of the XAPI database. If you downgrade, then XAPI with detect that the database is too recent and will refuse to start.So, you can technically downgrade the files, but not the state.
