@stormi Microcode updated on affected Gen11 i7. Running normally.

@gduperrey I jumped in all the way by mistake... I updated a wrong host, so I just did them all. Older AMD, Intel E3/E5, NUC11, etc. So far, so good. Add/migrate/backup/etc VMs are working as usual. Good for guest tools too, but mine are mostly Debian 7-11. Stuff is as usual so far.

I agree and I'll say it again, Thanks! It's not just Linux/Xen stuff. It is XCP-ng and XO that make everything work as a cohesive vertical open-source solution (some nice buzz words). Thanks to the Vates team and community that have built and support it. I look forward to ongoing continuous improvement and innovation!

@bleader Installed and running.

@bleader Updates running on several old and new intel machines (including microcode update). Working fine so far. Rolling Pool Reboot is a helpful feature.

@bleader I installed it on a bunch of busy hosts. All are fine, but none used PCI passthrough. The Rolling Pool Reboot in XO was very helpful.

@abudef @olivierlambert @thomas-dkmt I agree. I read block the same way... how about disable or prevent. (French? empêcher)

@julien-f @olivierlambert

Thanks for the ability to delete XO task logs feature! (XO commit f6e6e)

@gduperrey Installed and running on Intel systems, and Zen3 system that sees the microcode update.

@stormi I did a standalone host ISO install, all works as expected. I also did a pool ISO upgrade (8.2.1 to 8.3), master first, others second, migrated live VMs from old to new, all works as expected.

@acebmxer Did you activate your License?
Click on XOA then Licenses (at the top). Make sure you see This license is active on this XOA

@olivierlambert Something Odd...

I am running XOA latest channel version: 5.109.0.... Today it asked me to allow an upgrade (not sure to what), so I did. The upgrade ran and disconnected me, as usual. Now all I see is Cannot GET / after a damaged login page.

So I SSH'd in to the OS and did a downgrade to the stable channel and then upgrade to the latest channel and it works again...

@olivierlambert In XOA 5.109.0 and XO (master 31a3f), I'm trying to delete a disconnected server, but it gives me an error, this should be allowed.

server.remove
{
  "id": "7c2131df-2798-4837-9770-6e01facb7629"
}
{
  "code": 25,
  "data": {
    "actual": "disconnected",
    "expected": [
      "connected",
      "connecting"
    ],
    "object": "7c2131df-2798-4837-9770-6e01facb7629",
    "property": "status"
  },
  "message": "incorrect state",
  "name": "XoError",
  "stack": "XoError: incorrect state
    at incorrectState (/usr/local/lib/node_modules/xo-server/node_modules/xo-common/src/api-errors.js:21:32)
    at XenServers.disconnectXenServer (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/xen-servers.mjs:541:13)
    at XenServers.unregisterXenServer (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/xen-servers.mjs:133:5)
    at Xo.remove (file:///usr/local/lib/node_modules/xo-server/src/api/server.mjs:48:3)
    at Task.runInside (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:175:22)
    at Task.run (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:159:20)
    at Api.#callApiMethod (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/api.mjs:469:18)"
}

@markr @Greg_E I just installed a fresh copy of retail Win11 Pro 24H2 from ISO and all updates on my XCP 8.3 host with Xeon E5v2 CPU. Win11 installed and I get to the desktop to install the Xen tools. I have Secure-Boot, TPM, and driver update enabled in the settings.

@dnikola The AQC113 10G card (from your vendor) also support 2.5G with the driver loaded.

@dnikola As for the other card you listed, no, it's still a 8125 card. The single port 10G card (from the same site) is a AQC113 chipset, you'll need to install the atlantic-module-alt to support it. If you must have 2.5G then the Intel i225/i226 card is the other choice (not from that site).

@dnikola Please make sure your motherboard firmware is up to date (BIOS F30e). There are a LOT of stability issues with Intel CPUs for that board and old BIOS.

If you still have r8125 crashes, then try a newer r8125 alt version (9.016.00) from my download page and see if it works better. I gave it a quick test and it installs and works, but YMMV... You can always uninstall it.

@olivierlambert There are new versions of the r812x drivers. They don't compile cleanly for XCP. The r8127 driver was withdrawn and the r8125/r8126 was split into two different drivers. Realtek never publishes release notes.

I'll have to test the new driver and see if it's worth trying. I don't know if and update would solve this panic issue as there are lots of undocumented code changes.

The forum has been quiet about new r8125 issues, so in general the current driver has been working well enough. Just two issues I remember, including this one.

Realtek has also released new hardware revisions of the r812x chips that need new driver support and are only recently supported by their vendor driver and in upstream Linux 6.15 (not even 6.12 LTS yet).

As for the r8127, it looks like it could be a desktop game changer as it's a small cheap low power 10G chip. But like the others, its release is delayed and it does not have driver support yet (or test samples).

@TeddyAstie It could be! The crash does look like a r8125 driver issue.

It's older Realtek code that has been working well on XCP systems. The newer current Realtek released code has new issues, so there's no quick direct update... I have not seen the current r8125 XCP driver cause crashes.

I would point my finger back at this specific system and some odd condition that the driver does not handle correctly.

As this is vendor code, there is no upstream Linux testing.... so, no non-XCP problem reports.

@gduperrey Installed and running on Intel systems, and Zen3 system that sees the microcode update.