there is

xe vm-param-get param-name=networks uuid=<vm_uuid>

Found it. Error is related to https://github.com/xapi-project/xen-api/issues/4141

Somehow, the PCIe bus address of the server's ASPEED VGA adapter changed.

I got the new bus address with lspci and edited state.db accordingly. Works now. However, this seems to be a very strange bug.

stormi created this issue in xapi-project/xen-api

open XAPI failing to initialize after GPU removal? #4141

Found it. Error is related to https://github.com/xapi-project/xen-api/issues/4141

Somehow, the PCIe bus address of the server's ASPEED VGA adapter changed.

I got the new bus address with lspci and edited state.db accordingly. Works now. However, this seems to be a very strange bug.

stormi created this issue in xapi-project/xen-api

open XAPI failing to initialize after GPU removal? #4141

Are there any tools to edit state.db?

@Danp unfortunately not, at least not externally. And I think restore metadata would be kind of tricky, since the xapi tools won't work, XO is inside a VM and reinstalling xcp-ng would kill the SR on the primary disk.

It's a test/dev system at home anyway and not too important. I'll erase it and make a new one. However, I do now understand the importance of metadata backups better.

Hi,

after recovering from a power failure, xapi keeps crashing with this obscure error in xensource.log:

Aug 13 11:34:20 hostname xapi: [debug||0 ||xapi] xapi top-level caught exception: INTERNAL_ERROR: [ (Scanf.Scan_failure\x0A  "scanf: bad input at char number 6: looking for ':', found '.'") ]

Does anyone have an idea what causes this situation?

All the best,
Sven

By the way, is there a safe way to uninstall Citrix drivers and management agent, turn off "Windows Update Tools" and install the free OSS drivers?

@olivierlambert Might be... However, all the other windows VMs with citrix drivers seem to run fine (at least until now). As the failed VM was a Domain Controller, I'll set up a new one with free drivers for the moment. Rolling back images isn't recommended my MS for DCs.

I'll keep my eyes open - just wanted to check if anyone else got into the same trouble.

Hi there,

a Windows 2019 Server Guest would not boot anymore after recent updates.
I am getting BSOD STOP 0xc000021a.

Host is a XCP-ng 8.1 with current platch level, Guest has Windows Update Tools enabled.

Anyone else experiencing this kind of problem?

• or - DO try this at home and get Linux skills by doing it

I've done it on a Rock64 (which is a similar device, but slightly more powerful). It runs quite nicely on Debian arm64, although I don't not use it for production (yet).

BUT: Do not try this at home without sufficient Linux skills.

there is

xe vm-param-get param-name=networks uuid=<vm_uuid>