@Davidj-0

Thank you, this solved my issue.

@Davidj-0

Thank you, this solved my issue.

@Davidj-0

1. I mean that Xen Orchestra sees the host as running. Even though it should show offline. The host has been reinstalled, due to upgrading the storage (local disks only)

2. There is only a local SR on the host that has been totally wiped (meaning that the operating system of the host is no longer existing and the disks are removed long ago)

3. All the important VM:s has already been migrated to another host. This host does no longer exist, therefore I wonder why Xen Orchestra shows it running and powered on.

4. I am just trying to remove the host, because it is no longer exists. The host has been completely wiped, and rejoined again as another host (because of a fresh reinstallation)

Hi!
I've gotten myself into a bit of a mess I guess and I need help to resolve it. I changed storage on one of my host, and that meant that I did not power down the host correctly. But now, when I try to forget the host, a running VM does not let me remove the host.

The problem:

1. The host is "running" even though it is not connected.
2. It has a "running" ghost VM
3. The VM has a GPU attached
4. Trying to shut the VM down results in the host offline error message.

How can I resolve this issue?

@gck303
What happens if you spin up a new Windows Server 2019 and on the old Windows Server 2019 run the backup program and restore the backup on the new Windows Server 2019? Might be a solution?

I've encounter this error on a few occasions. There might be a few reasons:

• The VM has features or hardware requirements that cannot be met by the host (too much assigned memory, Network, CPU-cores, GPU or storage does not match with the server)
• The XOA has not been refreshed (it can help to sign out/sign in again and get a new session going)
• Force shutdown (Works sometimes, but sometimes not that even helps and might not always be a good solution)
• Try to use the XCP-NG Center (Even though it is old, it can also give some hits of what is wrong, it does not work though in 8.3)
• Restart the host (Last resort to resolve the issue for me at least)

Looking at your error message, it looks like there is some trouble with the network and storage. Have you maybe migrated the VM or such?