@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.

@gduperrey Installed and running on a few hosts. Good so far.

@gduperrey Installed and running on a few pools. Working correctly as expected.

It would be nice to have an "unregister" button, or better, a "use free license" button.

@stormi Got it... I missed that one for coretemp. Vates ticket opened for the XOA stats problem after 8.3 upgrade.

@stormi Upgrade problem... I upgraded a good working busy 8.2.1 server to 8.3 (using the new ISO). The upgrade went well without error. No guest VMs were changed.

Same issue in XO (Master 7be70) and XOA (5.107.2), so it must be an XCP issue. There are three new problems (all was working before);

1. XCP coretemp no longer loads/works. Error: coretemp coretemp.0: Adding Core 0 failed
2. XO Host CPU stats and Load are now reported as zero (It's a busy machine, they are not zero)
3. XO All guest VMs report zero CPU usage. Some just report No stats. for CPU. They do have current recognized guest tools (Linux and Windows). They do report other stats (memory, network, disk).

Other older XCP 8.3 hosts/guests are working.

@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.

@dinhngtu @olivierlambert @stormi I think the Windows VM's with old tools should show up in the Dashboard Heath report under "Guest Tools status"...

@flakpyro From my experience, VM with UEFI boots faster than BIOS. For some OS versions UEFI runs faster IF there are no Xen drivers. But for most installs it does not matter much, except for Debian... which has given me problems with pool/migration/reboot with the UEFI installs on XCP (there's a workaround).

So, I would vote for UEFI as the default for all OS/VMs that support it correctly since most are moving to that anyway (including XCP hosts).

@olivierlambert Any backups that run cause RPU to fail and not continue/restart. My example of this is hourly continuous replication breaks RPU.

@olivierlambert @flakpyro Commit 2fd5759 seems to solve the issue for me.