[SOLVED] Win 2003 blue screen after 6.8.8.2 kernel update ?

[Pcom]

Hi,

in our proxmox environment we have a Win server 2003. I know it's wrong, please don't tell me it's unsupported, we need this machine.

Yesterday evening i've updated all my proxmox server to latest kernel 6.8.8.2 and many other debian updates. I don't know if it's related but after this update the server 2003 machine doesn't boot anymore and give us blue screen every time (see attached image). I tried to disable ACPI, no signs of life, I tried to restore a backup of the VM, still BSOD, I tried to downgrade proxmox to kernel 6.8.8.1 and 6.5, nothign changes.

Any idea how to recover my 2003 machine?

Thanks

 

[LnxBil]

For such legacy systems, I often go down the nested road: running an older PVE inside of a newer PVE and in this nested PVE the older OSes. This is of course not very fast, yet it works most of the time.

 

[Pcom]

Can I ask what's the benefit of this? I mean, this server worked for many years on vmware esxi and now it's one year that is working in proxmox.

By the way, first of all now i need to regain access to a working VM. I don't know how to boot it anymore.

 

[LnxBil]

Can I ask what's the benefit of this?

You said that you suspect the PVE kernel, so running an older version will have an older kernel and chances are higher that it'll work again.

I mean, this server worked for many years on vmware esxi and now it's one year that is working in proxmox.

So? How many times have you upgraded your VMware in that time?

By the way, first of all now i need to regain access to a working VM. I don't know how to boot it anymore.

Revert the changes you made in your PVE and restore the VM from your backup.

 

[Pcom]

Revert the changes you made in your PVE and restore the VM from your backup.

Can you explain me how to remove all the updates installed yesterday? I tried to boot the older proxmox kernel but seems not enough, problem persist.

When I will recover the VM then I'll think about a long term solution

Thanks.

 

[sbs]

Hi,

Did you try acronis universal restore (I am not sure it is still called like this today)?
It can do magic fixing mismatched drivers at boot time, and let you boot back into the system so that you can install the drivers needed to match the hardware.

 

[LnxBil]

Did you try acronis universal restore (I am not sure it is still called like this today)?

You can try to boot the older kernel, otherwise restore from backup.

It can do magic fixing mismatched drivers at boot time, and let you boot back into the system so that you can install the drivers needed to match the hardware.

Reverting the kernel and booting the VM from the state of the update (e.g. from backup) should automatically solve the problem.

 

[Pcom]

Hi,

Did you try acronis universal restore (I am not sure it is still called like this today)?
It can do magic fixing mismatched drivers at boot time, and let you boot back into the system so that you can install the drivers needed to match the hardware.

No, never tried. It's a free product?

You can try to boot the older kernel, otherwise restore from backup.

Reverting the kernel and booting the VM from the state of the update (e.g. from backup) should automatically solve the problem.

Unfortunately it doesn't, tried 6.8.8.1 and 6.5.something and tried last two VM backups, always blue screen at boot

 

[sbs]

No, never tried. It's a free product?

No it's acommercial product. It was an option of the acronis backup suite. But it used to be quite cheap for a single license.

https://www.acronis.com/en-us/technology/universal-restore/

 

[toomanylogins]

Have you tried changing the vm cpu type ?

 

[Pcom]

Have you tried changing the vm cpu type ?

love you

I tried to change everything except cpu (without success), then I switched CPU from "host" to "kvm64" and server works again. Many thanks!

Can you or someone else explain me why this happened and if it could be related to latest kernel updates?

 

[hzk916]

After upgrade from 8.2.2 to Proxmox 8.2.7 blue screened my 2003 server, Switching scoket type from host to KVM64 solved the problem. Hardware was a AMD Ryzan 5 2600x.

 

[Pcom]

Glad this topic was helpful