XCP-ng 8.3 updates announcements and testing
-
@bufanda Hello,
There is equivalent
sm
packages in the qcow2 repo for testing, XAPI will be coming soon.
You can update while enabling the QCOW2 repo to get the sm and blktap QCOW2 version and get the XAPI version letter if you want. -
@dthenot No worries, just wanted to make sure I understand the expected behavior when I had the qcow2 patches installed.
-
@bufanda You just need to make sure to have a sm and blktap qcow2 version.
Otherwise, having a normal sm version would drop the QCOW2 VDI from the XAPI database and you would lose VBD to VM aswell as name of VDI.
So it could be painful depending on how much you have
But in the case, you would install a non QCOW2 sm version, you would only lose the QCOW2 from DB, those would not be deleted or anything. Reinstalling a QCOW2 version then rescanning the SR would make them re-appear. But then you would have to identify them again (lost name-label) and relink them to VM.
We try to keep our QCOW2 version on top of the testing branch of XCP-ng but we could miss it -
@dthenot Only have 2 Test VMs currently not running with qcow2. Nothing production and nothing crucial. It's a lab pool. As I said just to understand the behavior when I test the new updates. But thanks for the details. Really appreciated
-
Installed and working on my lab test machine, HP ProLiant DL165 G7 with AMD Opteron 6136 CPU and 32 GB of RAM.
-
@gduperrey Installed and running on a few hosts. Good so far.
-
Updates published: https://xcp-ng.org/blog/2025/07/03/july-2025-security-and-maintenance-update-for-xcp-ng-8-3-lts/
Thank you for the tests!
-
Sorry to join the bandwagon late this time, but i got these errors while booting:
[ 0.826901] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20180810/dswload2-160) [ 0.826908] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180810/psobject-221) [ 0.826910] ACPI Error: Ignore error and continue table load (20180810/psobject-604) [ 0.826912] ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543) [ 0.827236] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20180810/dswload2-160) [ 0.827239] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180810/psobject-221) [ 0.827241] ACPI Error: Ignore error and continue table load (20180810/psobject-604) [ 0.827242] ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543) [ 0.827245] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.GPP5.EWPM], AE_ALREADY_EXISTS (20180810/dswload2-316) [ 0.827248] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221) [ 0.827250] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.GPP5._PRW], AE_ALREADY_EXISTS (20180810/dswload2-316) [ 0.827252] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221) [ 0.827254] ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543) [ 0.827257] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.GPP5.RTL8._S0W], AE_ALREADY_EXISTS (20180810/dswload2-316) [ 0.827259] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
I think this is after the new update
Processor : AMD Ryzen 7 7840HS
-
Hi,
It's just an ACPI error, it shouldn't be a problem.
-
I agree. But just thought I should report nevertheless.
Update: This seems to be related to 7840HS motherboard. I tried it on another AMD Ryzen 7945HX but did not get this error.
-
It's clearly due to the motherboard, yes. Mostly buggy BIOS/UEFI and ACPI tables. This world is like the far west.