Successful upgrade from XCP-NG 7.6 to 8.0. I've let everything run for a few days and I haven't had any issues. (Single Dell R620)

Updating one of my test servers now. (Dell R610)

If all goes well, I will update another test server (Dell R620) later this week.

@300cpilot

I'm going to try the remote event viewer over the next few days to see if anything of interest comes up. As for remote desktop, and ping I get no response.

@olivierlambert @borzel

I'll pull the latest builds and see if I have any luck. I'm also going to pull the latest Windows Server updates on a few of the VMs (seems they just came out a few hours ago as I checked for updates earlier and had nothing)

Successful upgrade from XCP-NG 7.6 to 8.0. I've let everything run for a few days and I haven't had any issues. (Single Dell R620)

Update: The same VM crashed again, the others are working fine as of this post. I left it up as a remote desktop session last night and I came back to my office today and it was still up as a RDP session, but not responsive. I checked XCP-NG Center and the same blue screen with a cursor was there.

Still trying to find the cause of this.

@borzel Sometime between the 7:40 and 12:12 on the first line. I'm guessing it went down right as I was posting here.

Like I said whatever it's doing it doesn't seem to log it. Is there any other log files I should check?

EDIT: I have a theory, testing it now.

EDIT 2: I'm wondering if this has something to do with XCP-NG Center. The KMS server (the one that locked up) was the only one I logged into when checking if everything was working. Trying to duplicate this now.

I had one lock up on me. Surprising the one with the shortest uptime.

EDIT: I just updated the xcp-emu-manager-0.0.9-1 that was posted about a bit ago. Not sure if this will help or not.

Have you heard of anyone else having these issues? I'm debating on doing a fresh install of XCP-NG to see if that helps.

EDIT 2: There are no error logs given in Windows. One minute it's working, the next it's not. I'm going through the XCP-NG logs at the moment to see if there is anything there.

EDIT 3: Here is a list of every line with the UUID of the VM associated with it: https://pastebin.com/ip30uyMN

Quick Update

I haven't had any crashes since posting here. Before posting here it was each of my 2016 & 2019 VMs on XCP-NG that would lock up. Now it's none of them. Some of them I updated, while others I did nothing... Strange.

I'll update this post again in a few days, or sooner if anything changes.

@300cpilot

I'm going to try the remote event viewer over the next few days to see if anything of interest comes up. As for remote desktop, and ping I get no response.

@olivierlambert @borzel

I'll pull the latest builds and see if I have any luck. I'm also going to pull the latest Windows Server updates on a few of the VMs (seems they just came out a few hours ago as I checked for updates earlier and had nothing)

I have a few Windows 2016 & 2019 Standard Servers on my test network and after about a 5-7 days or so of uptime and then they completely lock up.

A few things of note:

• All hosts are on 7.6
• This happens with and without client tools
• Each VM instance is fully activated and updated
• This is happening on hosts in multiple pools and on different hardware
• None of these hosts are running the experimental update that was posted a few weeks ago. I am going to migrate a Windows Server VM to a host that is to see if the problem persists
• Reboot and shutdown fails, even after a tool-stack restart
• Force shutdown and manually starting them seems to work fine
• Windows 10 does not seem to lock up like this
• Linux and BSD based VMs are working fine

Looking forward to suggestions and responses! I hope to fully migrate my productions servers over to XCP-NG from VMware around June-July of this year! (We will be contacting for pro support in the coming months.)

There is a bit of a time gap in the pictures below. I don't get the time to work with my test network everyday so I didn't notice the crashes. I have left one VM in a crashed state in case there are any questions about it.

This fixed the issue for a few migrations. The latest one put the VM into a suspended mode and then disconnected me from the host. I restarted the tool-stack on each host and when I went to reconnect to the host I was migrating the VM from it would let me in for a moment and then kick me out again and it was in a maintence mode according to the icon. To resolve this I rebooted the host. I'm currently seeing if I can replicate this behavior.

Other than this I haven't run into any issues so far.

Let me know if there is anything specific you would like tested.

@stormi

Do you have any suggestions for me to try to help see if this is related?

So far I have run into one issue. When I force a live migration the VM I migrate gets stuck at 99% and sits there. I let it sit overnight to see if it would go through, but it didn't .

When attempting to cancel the migration it left a copy of the VM frozen on each host. When attempting to reboot/shutdown or even force reboot/shutdown I would get an error saying they did not exist.

Rebooting the hosts fixed the this issue, but left me with a full copy of the VMs on each host. I was also unable to reboot the host I migrated the VM from unless I used the xsconsole window. XCP-NG Center did not work.

If I get time today I will roll back the R610 to 7.6 and see if I have the same results.

Here are a few photos: https://imgur.com/a/wYw6AdL

Other than this edge case issue, everything seems to be working fine so far!