Migrated Windows2019 vmdk keeps rebooting
-
I am using a new and fresh XCP-NG 8.3 install. Storage is on a Synology NAS with Intel DS SSDs and using a 10GBe network to the XCP hosts.
I have migrated a Windows 2019 server from Proxmox by moving and running qemu-img on the files. Originally this VM was installed on ESXi and was migrated into Proxmox.
The problem:
-
the Windows 2019 server restarts every few minutes. After a few minutes it reboots. This cycle repeats and repeats.
-
the network when it is up is not great . There are mised and delayed responses to a ping
-
no other VM has this problem
-
I have tried migrating from different VMDK files and backups. The same result
-
There are no obvious mistakes in the XCP config
-
I have checked all the logs in the XCP hosts. There is nothing obvious. I can provide anything more if needed
-
A fresh install of Win2019 in XCP works fine.
I am not sure where to go next...
Is this problem resolvable? I am tempted just to rebuild a new server and re-install the software.
Thanks, George
PS. Brilliant forum. Brilliant software. Double thumbs up!
-
-
@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? -
@gck303 Were there any I/O drivers installed on your Server 2019 server? Do you have any events in the VM's System log, or any crash dumps?
-
@kassebasse It only stays up for five minutes or so. It is not around for long enough to take a backup.
@dinhngtu Ah, good point. I will check to see if there were drivers installed for Proxmox/ESXi. I guess it would possible that there are some left there.
I have not attempted to install any XCP drivers on the VM. Might that be a resolution?
-
@gck303 said in Migrated Windows2019 vmdk keeps rebooting:
@kassebasse It only stays up for five minutes or so. It is not around for long enough to take a backup.
@dinhngtu Ah, good point. I will check to see if there were drivers installed for Proxmox/ESXi. I guess it would possible that there are some left there.
I have not attempted to install any XCP drivers on the VM. Might that be a resolution?
Installing the Xen-Guest-Drivers won't act as a fix to this issue. Though it is recommended that you install the drivers for performance and metric reasons, that is purely after any issues have been fixed.
What I would recommend is wherever this VM is running successfully now, uninstall any hypervisor specific drivers and then either export it to OVA/XVA and then import it.
While this of course does change your production system, if your goal is to move off of your existing hypervisor to XCP-ng you'll need to remove these drivers anyways.
-
So....................... it is dynamic memory causing me problems.
I have have set the min/max and static memory to the be same. The system stays up fine.
Now to figure our how/if I need dynamic memory to work on a Windows VM. I do not seem to be having problems with linux based workloads.