Xen 4.0 did some changes to the tick tack machinery for Dom0/U
I see that a default installation of Bookworm default to a clocksource set to xen, this is not good for some or actually most of the applications run today, latency increase and increased load.
Changing clocksource to TSC might be a better option or is it? i have been using TSC for some time with much better latency and performance results
I can agree with you that my meaning of sneaky this time was not accounted for, at first glance my thought was this function was removed by intention by vates when the xsconsole was revamped to further push backup/restore options towards XO usage. I see now that i was wrong in that assumption!
How do you restore this metadata backup in xcp-ng 8.3 without the use of XO?
This is absolutely something to write about in the release note of 8.3. when is it expected back?
@Danp Was working perfectly fine in 8.2.1 LTS
In xcp 8.3 xsconsole has got a revamp, i suspect this function was removed in this operation.
What happen to the XSCONSOLE backup restore and update function?
where is the pool metadata backup functions and schedules menu?
why is this not mentioned in the deprecation notices here in the docs?
i am happy we did catch this before upgrading, anyway to get this function back?
Why isn't the removed functionality available in XO lite?
Snicky this one from vates
Iam considering trying out the testing branche of debian, currently bullseye. Are there anything wrong in using the debian 10 Buster template in XCP-NG 8.1 to run bullseye?
@stormi as long as you dont have any untrusted vms running on this cpus there is no problem with security issues.
Thanks you guys for testing the l5630 cpu, this gave me confidence to upgrade my dell r610 with 2x x5675 cpus with hypervisor 8.0, upgrade was done with iso and cd and the upgrade process went very smooth, server boot up and everything seems almost nice.
i did notice it load cpu microcode rev 1f on boot, i also notices systemd is throwing a error on boot: systemd failed to load kernel modules, this has no impact and the host is running fine with no error other than that. i suspect the error might be related to upgrade fra 7.6, i will try to reinstall 8.0 as a fresh install and see if this clears the kernel modules stuff.
Can anybody that has the means try to run Citrix Hypervisor 8.0 on those legacy 56xx series CPUs?
Have anybody tried xcp 8.0 with the intel x56xx series cpu?
why is support for this cpus dropped, are there any technical behind it or just that they are old and considerd Legacy?
i would like to know if this cpus have been tried with this veriosn of xcp.