If it helps anyone. I rolled back to an earlier driver for PV Bus driver for the one that starts with 0. I did this on two VMs. Not sure what the difference is, but both have been running for a few days now with zero issues. Could be a coincidence.
I'll update again if the problem starts again.
If it helps anyone. I rolled back to an earlier driver for PV Bus driver for the one that starts with 0. I did this on two VMs. Not sure what the difference is, but both have been running for a few days now with zero issues. Could be a coincidence.
I'll update again if the problem starts again.
@olivierlambert no just drivers from the windows updates.
@olivierlambert thanks for the reply Oliver! This is something like I will login to XOA and the console screen is blank for the VM. So I'll try remote to remote desktop and it's the same.
I've had it at times where i've done something like used remote desktop and if l let it sit there it may come back after a couple minutes.
Seems like I will start noticing it after a couple days. Then after a couple more I lose the display. The VM seems to function still.
If I try to reboot it from XOA it won't reboot, or I get tired of waiting for it to reboot.
I guess it would be more accurate to say this happens with Windows Server 2019 since it's the only Windows OS I've tried in the past.
For some reason whenever i use a Windows VM I have a problem after a few days. The console screen just goes blank. Same thing if I try to remote into the VM. The VM is functioning but I lose the display.
Has anyone else ever had similar problems? It's the third time this has happened to me with a Windows VM. I use the Windows Update feature in XOA to install the drivers
I have a VM if it runs more than a couple days it takes forever to reboot or I just have to force a reboot on it. The CPU usage spikes as soon as I try to shut it down. I am using Citrix Drivers.
Is it normal to see PV Devices hidden under device manager? If I try to remove them the VM it won't boot. It looks like when the drivers have updated it left the old devices.
@nraynaud I unfortunately deleted my ova files. However, I still have the esxi server. I am exporting a new ova now. If I can get the error to happen for me again I will send you a link to download the ova file.
I was having this problem too. I used OVFTool 4.3.0 to export a VM to ova. I am not sure if it's just coincidence or not, but the first ova imported fine using sources.
However, I exported two more VMs using a different machine and I received the same error. I used XO from quick deploy on the main screen. Both of the VMs imported fine using the quick deploy. This was on a fresh install last week. (My First Time Using XCP-ng)
The first VM was smaller than the other two. It was exported out on a Windows 10 machine. The other two VMs were on a Windows Server 2012R2 machine.
I am sure other people have done this before as well, but I used Veeam Agent to import most of my larger VMs. I booted off the ISO and restored from my backups and had little problems with getting the machines to work. The only thing I changed was the NIC type to an intel because I wasn't getting gigabit speeds during the restore.