Your issue was unrelated to tools but a Xen upgrade from 4.13 to 4.17 without rebooting it (ie the libs were on Xen 4.17 while the hypervisor still running in memory was 4.13). A reboot solved that.
administrators
-
RE: XCP-NG 8.3 + rust tools - Unable to shutdown VM
-
RE: After installing updates: 0 bytes free, Control domain memory = 0B
@olivierlambert You would need to ask @Andrew as I only went off of his post where he stated the following
I started looking at https://xcp-ng.org/docs/releases.html,
-
RE: Passing Though a GPU
It's perfectly normal that the PCI device number is different between the dom0 and the VM. Because the VM is a fully independent system with its own PCI enumeration.
-
RE: Technique for shared repo of cloudinit templates
Your pre-recorded Cloudconfig own setup is user-wide (so per user). It won't be universal for everyone.
-
RE: After installing updates: 0 bytes free, Control domain memory = 0B
@Danp I mean, originally, the link where you found it, outside the doc itself? I have redirect almost all old docs link to the new one.
-
RE: XCP-NG 8.3 + rust tools - Unable to shutdown VM
@nikade said in XCP-NG 8.3 + rust tools - Unable to shutdown VM:
XEN_INCOMPATIBLE
There have been several threads related to the recent 8.3 updates where xen was updated from v4.13 to v4.17, and the user encountering problems until the host was rebooted. Could this be your issue?
-
RE: After installing updates: 0 bytes free, Control domain memory = 0B
@Danp where did you find the https://xcp-ng.org/docs/release-8-2.html link originally?
-
RE: After installing updates: 0 bytes free, Control domain memory = 0B
Ah so in the doc itself, understood, fixing it now!
edit: that's the old doc, cf https://docs.xcp-ng.org/releases/release-8-2/
I will be sure to redirect the old one to the new one.