Problem on Migrating Windows Server 2003

O

OrbitalCanon

New Member
Proxmox Subscriber
Jul 7, 2026
3
0
1
Hello,

I am trying to migrate a Windows Server 2003 virtual machine from VMware ESXi 6.0 to Proxmox VE.

The VM is currently running properly on ESXi. Since my ESXi subscription is ending, I would like to move it to Proxmox.

I created a snapshot of the running Windows Server 2003 VM, exported/generated the .vmdk disk file, and transferred it to the Proxmox host using scp.

After that, I created a new VM on Proxmox and attached/imported the converted disk. My current Proxmox VM configuration is:

bios: seabios
boot: order=ide0
cores: 2
ide0: local-zfs:vm-112-disk-0,size=102390M
machine: pc-i440fx-7.2
memory: 4096
meta: creation-qemu=11.0.0,ctime=1783383714
name: ****
scsihw: virtio-scsi-pci
smbios1: uuid=bb0d136c-7a17-4b3a-916e-55213d722b1d
sockets: 1
vmgenid: 351b3161-19fb-4e2e-be71-2b89c733c721

However, when I try to boot the VM on Proxmox, Windows Server 2003 fails with the following BSOD:

STOP: 0x0000007B
INACCESSIBLE_BOOT_DEVICE

I also tested installing Windows Server 2003 from an ISO on Proxmox, and that works. However, this old VM has several services and configurations already running, so I would prefer to boot from the migrated disk instead of reinstalling and configuring everything again from scratch.

My goal is to boot the existing Windows Server 2003 system disk on Proxmox.

Does anyone have advice on how to fix the 0x0000007B boot issue after migrating from ESXi to Proxmox?

I suspect it may be related to the storage controller driver or HAL/boot device configuration, but I am not sure what the best approach is for Windows Server 2003.

Any suggestions would be appreciated.

Thank you.
 
Honestly, don’t. Don’t do this at all. It’s 2026. There’s no support on that OS by its manufacturer. Whatever it’s running, leave running as is. Migrate services to a newer OS or look for replacement of your old app, but stop wasting your and anybody else’s time on running Windows 2003.
 
I think we'll have to use an even older version, but as he says, it would be better to avoid using junk like this.

Code: 
kvm -M help
Supported machines are:
microvm              microvm (i386)
pc-i440fx-9.2        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-9.1        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-9.0        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-8.2        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-8.1        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-8.0        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-7.2        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-7.1        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-7.0        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-6.2        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-6.1        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-6.0        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-5.2        Standard PC (i440FX + PIIX, 1996) (deprecated)
pc-i440fx-5.1        Standard PC (i440FX + PIIX, 1996) (deprecated)
pc-i440fx-5.0        Standard PC (i440FX + PIIX, 1996) (deprecated)
pc                   Standard PC (i440FX + PIIX, 1996) (alias of pc-i440fx-11.0)
pc-i440fx-11.0       Standard PC (i440FX + PIIX, 1996) (default)
pc-i440fx-10.2       Standard PC (i440FX + PIIX, 1996)
pc-i440fx-10.1       Standard PC (i440FX + PIIX, 1996)
pc-i440fx-10.0       Standard PC (i440FX + PIIX, 1996)
pc-q35-9.2           Standard PC (Q35 + ICH9, 2009)
pc-q35-9.1           Standard PC (Q35 + ICH9, 2009)
pc-q35-9.0           Standard PC (Q35 + ICH9, 2009)
pc-q35-8.2           Standard PC (Q35 + ICH9, 2009)
pc-q35-8.1           Standard PC (Q35 + ICH9, 2009)
pc-q35-8.0           Standard PC (Q35 + ICH9, 2009)
pc-q35-7.2           Standard PC (Q35 + ICH9, 2009)
pc-q35-7.1           Standard PC (Q35 + ICH9, 2009)
pc-q35-7.0           Standard PC (Q35 + ICH9, 2009)
pc-q35-6.2           Standard PC (Q35 + ICH9, 2009)
pc-q35-6.1           Standard PC (Q35 + ICH9, 2009)
pc-q35-6.0           Standard PC (Q35 + ICH9, 2009)
pc-q35-5.2           Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-5.1           Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-5.0           Standard PC (Q35 + ICH9, 2009) (deprecated)
q35                  Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-11.0)
pc-q35-11.0          Standard PC (Q35 + ICH9, 2009)
pc-q35-10.2          Standard PC (Q35 + ICH9, 2009)
pc-q35-10.1          Standard PC (Q35 + ICH9, 2009)
pc-q35-10.0          Standard PC (Q35 + ICH9, 2009)
isapc                ISA-only PC
nitro                Nitro Enclave
none                 empty machine
x-remote             Experimental remote machine

Older hardware (hardware compatible with older operating systems) is no longer supported or is deprecated.

I think this clearly indicates that older operating systems do not support it.

*pc-q35-5.0 is also relatively new compared to Windows Server 2003; it’s virtual hardware that was released after Windows Server 2003 reached its end of support (EOSL) in 2020.
I think this is kind of like wondering whether Windows Server 2003 would run on a motherboard released in 2026 (23 years after its release, or 11 years after its end of life).
Well, I haven’t tried it, so I don’t really know.

ChangeLog
https://wiki.qemu.org/ChangeLog/11.0

Code: 
The pc-i440fx-2.6, pc-q35-2.6 through to pc-i440fx-4.0 and pc-q35-4.0 machines have been removed.

He's saying that if you want to run it on the current version, you'll need to edit the registry on that Windows Server 2003 machine that isn't currently working.

l.leahu-vladucu

Post in thread 'Imported ESXi VM with Windows 2000 is not booting'

Another idea: not sure if this helps, but you can also try setting the machine version to an older one. I see that you are using pc-i440fx-9.0, so in the Machine settings keep using i440fx, but under Advanced, you can try setting an older version and see if this makes any difference.

By the way, some workarounds might be necessary to make Windows XP and Windows Server 2003 work - see this wiki page about Mergeide. There's also a link to a page for Windows 2000, but unfortunately, it seems to be dead. Thankfully, the Wayback Machine cached it - see this link.
  • Like

Advanced Migration Techniques to Proxmox VE
https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE

Well, whether or not an OS for the EOSL can be developed is none of my business, though.

Even if it works out, you’ll likely run into all sorts of problems. And no one will be able to help you with any of them. Proxmox VE support is limited to Proxmox VE, and they have absolutely no knowledge of Windows Server 2003 (and even if they did, they probably wouldn’t answer because they don’t want to turn this into a Windows Q&A forum). As a result, you’ll have to contact Microsoft, but they’ll probably turn you away.
 
Last edited:
uzumo said:
I think we'll have to use an even older version, but as he says, it would be better to avoid using junk like this.

Code: 
kvm -M help
Supported machines are:
microvm              microvm (i386)
pc-i440fx-9.2        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-9.1        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-9.0        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-8.2        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-8.1        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-8.0        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-7.2        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-7.1        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-7.0        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-6.2        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-6.1        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-6.0        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-5.2        Standard PC (i440FX + PIIX, 1996) (deprecated)
pc-i440fx-5.1        Standard PC (i440FX + PIIX, 1996) (deprecated)
pc-i440fx-5.0        Standard PC (i440FX + PIIX, 1996) (deprecated)
pc                   Standard PC (i440FX + PIIX, 1996) (alias of pc-i440fx-11.0)
pc-i440fx-11.0       Standard PC (i440FX + PIIX, 1996) (default)
pc-i440fx-10.2       Standard PC (i440FX + PIIX, 1996)
pc-i440fx-10.1       Standard PC (i440FX + PIIX, 1996)
pc-i440fx-10.0       Standard PC (i440FX + PIIX, 1996)
pc-q35-9.2           Standard PC (Q35 + ICH9, 2009)
pc-q35-9.1           Standard PC (Q35 + ICH9, 2009)
pc-q35-9.0           Standard PC (Q35 + ICH9, 2009)
pc-q35-8.2           Standard PC (Q35 + ICH9, 2009)
pc-q35-8.1           Standard PC (Q35 + ICH9, 2009)
pc-q35-8.0           Standard PC (Q35 + ICH9, 2009)
pc-q35-7.2           Standard PC (Q35 + ICH9, 2009)
pc-q35-7.1           Standard PC (Q35 + ICH9, 2009)
pc-q35-7.0           Standard PC (Q35 + ICH9, 2009)
pc-q35-6.2           Standard PC (Q35 + ICH9, 2009)
pc-q35-6.1           Standard PC (Q35 + ICH9, 2009)
pc-q35-6.0           Standard PC (Q35 + ICH9, 2009)
pc-q35-5.2           Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-5.1           Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-5.0           Standard PC (Q35 + ICH9, 2009) (deprecated)
q35                  Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-11.0)
pc-q35-11.0          Standard PC (Q35 + ICH9, 2009)
pc-q35-10.2          Standard PC (Q35 + ICH9, 2009)
pc-q35-10.1          Standard PC (Q35 + ICH9, 2009)
pc-q35-10.0          Standard PC (Q35 + ICH9, 2009)
isapc                ISA-only PC
nitro                Nitro Enclave
none                 empty machine
x-remote             Experimental remote machine

Older hardware (hardware compatible with older operating systems) is no longer supported or is deprecated.

I think this clearly indicates that older operating systems do not support it.

*pc-q35-5.0 is also relatively new compared to Windows Server 2003; it’s virtual hardware that was released after Windows Server 2003 reached its end of support (EOSL) in 2020.
I think this is kind of like wondering whether Windows Server 2003 would run on a motherboard released in 2026 (23 years after its release, or 11 years after its end of life).
Well, I haven’t tried it, so I don’t really know.

ChangeLog
https://wiki.qemu.org/ChangeLog/11.0

Code: 
The pc-i440fx-2.6, pc-q35-2.6 through to pc-i440fx-4.0 and pc-q35-4.0 machines have been removed.

He's saying that if you want to run it on the current version, you'll need to edit the registry on that Windows Server 2003 machine that isn't currently working.

l.leahu-vladucu

Post in thread 'Imported ESXi VM with Windows 2000 is not booting'

Another idea: not sure if this helps, but you can also try setting the machine version to an older one. I see that you are using pc-i440fx-9.0, so in the Machine settings keep using i440fx, but under Advanced, you can try setting an older version and see if this makes any difference.

By the way, some workarounds might be necessary to make Windows XP and Windows Server 2003 work - see this wiki page about Mergeide. There's also a link to a page for Windows 2000, but unfortunately, it seems to be dead. Thankfully, the Wayback Machine cached it - see this link.
  • Like

Advanced Migration Techniques to Proxmox VE
https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE

Well, whether or not an OS for the EOSL can be developed is none of my business, though.

Even if it works out, you’ll likely run into all sorts of problems. And no one will be able to help you with any of them. Proxmox VE support is limited to Proxmox VE, and they have absolutely no knowledge of Windows Server 2003 (and even if they did, they probably wouldn’t answer because they don’t want to turn this into a Windows Q&A forum). As a result, you’ll have to contact Microsoft, but they’ll probably turn you away.
Click to expand...
so, what do you want to say is to change the configuration on machine to the newest version, is it correct?
 
KarelBP said:
Honestly, don’t. Don’t do this at all. It’s 2026. There’s no support on that OS by its manufacturer. Whatever it’s running, leave running as is. Migrate services to a newer OS or look for replacement of your old app, but stop wasting your and anybody else’s time on running Windows 2003.
Click to expand...
Well, I agree with that. However, our organization does not have plan to do upgrade or redevelopment, so we only rely on currently running VMs.
 
OrbitalCanon said:
so, what do you want to say is to change the configuration on machine to the newest version, is it correct?
Click to expand...
Are you trying to ask an AI or something?

I never said anything like that. If you don’t feel like reading it, you don’t have to, but that won’t fix the problem.

It goes without saying that achieving your goal requires effort on your part, doesn’t it?

Please read everything, including the links. If the solution remains the same in the current version, you'll find the answer there.

Alternatively, since you seem to have a support ticket, you can pay to have this resolved instead of posting on the forum.
 
Last edited:
ESXi VMs usually use the LSI Logic Parallel controller. Try the LSI 53C895A or the LSI Logic Parallel within the PVE VM.

Beside that you mentioned a snapshot. Did you convert the complete snapshot chain including the descriptor file?
 
You must log in or register to reply here.
Top Bottom
Back