Hello together,
I just want to share an experience with migration of one of our servers which resulted in bsod right just before login screen appears.
First of all, thanks for proxmox and its availability.
We started with multiple test VMs and productive VMs being itself part of a testsytem with the following scenario:
Everything went well during tests with simple test-VMs and with the more complex test-system-VM with active testing data (approx. 1TB). Finally we wanted to migrate the production system and that went wrong. We got blue screens at every startup right before logon (during applying computer settings...) and all related to ntfs-bugchecks (STOP-Code 0x00000024 with some additional parameters and crashdump says its the ntfs.sys and fltmgr.sys). The VM came up with safe mode only: chkdsk hangs 3-5 mins before giving any output, so very suspicous.
Since we migrated a bunch of VMs successfully before without changing installed Software-Components, we did not suspect the AV product. But in the end an uninstallation of all AV-Components solved it. Boot ok, chkdsk fast as usual, no trouble any more.
one thing to add: remove vmTools before mig or disable in safe mode vmci and vm-services.
It was a terrible trip as we transferred the os partition again and again with different settings of storage, network, blocksize, compression on/off... First we thought of any kind of corruption during transfer, but 1,8+ TiB were ok except the os partition? The source VM's OS partition was healthy.
btw: other problems might occur, when proxmox host clock is accidentially wrong and windows gets its time from domain source after enabling network connections for this vm using proxmox-UI -> crash after reboot, perhaps due to timing bug in AV-product. This VM was unconnected for test reasons, then switched on network, reboot and crash. Another VM got into hanging situation. So better check clock and make use of ntp before going on with VM creation
and: keep an eye on instant creation of hiberfil.sys right afer first boot of target VM - why is that in an server OS? Might fill up disk :/
bye in hope it helps someone else.
I just want to share an experience with migration of one of our servers which resulted in bsod right just before login screen appears.
First of all, thanks for proxmox and its availability.
We started with multiple test VMs and productive VMs being itself part of a testsytem with the following scenario:
- VMWare Guests should be migrated to proxmox (6.3-2) environment
- less downtime as possible
- installing scsi and net drivers as legacy hardware before migration for successful bootup
- transfer of 2+ TiB of data including legacy OS with legacy software into new proxmox location out of the vmWare-VM using dd and transferring the dd-data using netcat over lan into the new vm (no conversion trouble) with live linux iso
- verifying data files (not in use) using hash checks within the old vm before transfer and inside the new vm after transfer
- all this as preparation of final data transfer from legacy VMs with old OS inside the VMs: Windows 2008 R2 (as an intermediate step before final migration)
- finally legacy VMs with old OS will be decomissioned
Everything went well during tests with simple test-VMs and with the more complex test-system-VM with active testing data (approx. 1TB). Finally we wanted to migrate the production system and that went wrong. We got blue screens at every startup right before logon (during applying computer settings...) and all related to ntfs-bugchecks (STOP-Code 0x00000024 with some additional parameters and crashdump says its the ntfs.sys and fltmgr.sys). The VM came up with safe mode only: chkdsk hangs 3-5 mins before giving any output, so very suspicous.
Since we migrated a bunch of VMs successfully before without changing installed Software-Components, we did not suspect the AV product. But in the end an uninstallation of all AV-Components solved it. Boot ok, chkdsk fast as usual, no trouble any more.
one thing to add: remove vmTools before mig or disable in safe mode vmci and vm-services.
It was a terrible trip as we transferred the os partition again and again with different settings of storage, network, blocksize, compression on/off... First we thought of any kind of corruption during transfer, but 1,8+ TiB were ok except the os partition? The source VM's OS partition was healthy.
btw: other problems might occur, when proxmox host clock is accidentially wrong and windows gets its time from domain source after enabling network connections for this vm using proxmox-UI -> crash after reboot, perhaps due to timing bug in AV-product. This VM was unconnected for test reasons, then switched on network, reboot and crash. Another VM got into hanging situation. So better check clock and make use of ntp before going on with VM creation
and: keep an eye on instant creation of hiberfil.sys right afer first boot of target VM - why is that in an server OS? Might fill up disk :/
bye in hope it helps someone else.
Last edited:
