[SOLVED] [Urgent] windows error while adding windows server 2008 (not R2) virtualmachines to proxmox

[yatcvic]

Good evening everyone , i have a windows server 2008 (not R2) imported to proxmox but while boot up showing windows error "Windows failed to start. A recent hardware or software change might be the cause."

When I go back to vmware workstation using same vmdk file, it is worked. May I know is there any way to do?

Thanks in advance.

 

[tplz]

I'm not very knowledgeable about this, but I've had a similar issue caused by Proxmox using a different storage controller and hard disk interface (IDE, SCSI, SATA, VirtIO Block) than was configured in VMWare. Check that the Proxmox VM is configured to use a controller and hard disk interface that is close to or the same as the VMWare VM. Failing that, maybe try other combinations of controller and disk interface on the Proxmox VM to try and find a combination that works.

 

[yatcvic]

thanks bro !

I checked the .vmx file of the windows server 2008 and I found guestOS = "longhorn" , may I know how to import to proxmox?

 

[tplz]

thanks bro !

I checked the .vmx file of the windows server 2008 and I found guestOS = "longhorn" , may I know how to import to proxmox?

From what I can tell, Longhorn is just an internal Microsoft codename that refers to Windows Vista. I don't believe this is relevant to the import process.

Could you post your Proxmox VM's config file? It's located in Proxmox at /etc/pve/qemu-server/<VM ID>.conf.

Additionally, could you provide a screenshot of the VMWare VM's configuration page which shows the VMs RAM, CPU, Drive, etc.

 

[yatcvic]

Yes sure !

Here it is:

-------------------------------------


root@mcsiproxmox:/mnt/pve/vmimport/images# qm config 150
agent: 0
boot: order=ide0;net0;ide2;ide1
cores: 4
cpu: x86-64-v2-AES
ide0: vmimport:150/vm-150-disk-0.raw,size=475886M
ide1: vmimport:iso/virtio-win-0.1.240.iso,media=cdrom,size=612812K
ide2: vmimport:iso/Windows_Server_2008_R2_x64.iso,media=cdrom,size=2926546K
machine: pc-i440fx-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1715944563
name: MCSI1mcsi001
net0: e1000=BC:24:11:30:EF:9D,bridge=vmbr0,firewall=1
numa: 0
ostype: win7
smbios1: uuid=d38c0af1-0bd4-4870-b7c0-e328e24238d0
sockets: 1
vmgenid: c1c35567-7a6a-4b1f-9795-a07d06dc2bdb
root@mcsiproxmox:/mnt/pve/vmimport/images#


--------------------------------------

And I have uploaded the VM configuration screenshot as attachment , in between I am trying to edit the guestOS field of the .vmx file and re-generate the vmdk file again using ovftool. Will keep posted

Thank you so much for help !

 

[tplz]

Yes sure !

Here it is:

-------------------------------------


root@mcsiproxmox:/mnt/pve/vmimport/images# qm config 150
agent: 0
boot: order=ide0;net0;ide2;ide1
cores: 4
cpu: x86-64-v2-AES
ide0: vmimport:150/vm-150-disk-0.raw,size=475886M
ide1: vmimport:iso/virtio-win-0.1.240.iso,media=cdrom,size=612812K
ide2: vmimport:iso/Windows_Server_2008_R2_x64.iso,media=cdrom,size=2926546K
machine: pc-i440fx-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1715944563
name: MCSI1mcsi001
net0: e1000=BC:24:11:30:EF:9D,bridge=vmbr0,firewall=1
numa: 0
ostype: win7
smbios1: uuid=d38c0af1-0bd4-4870-b7c0-e328e24238d0
sockets: 1
vmgenid: c1c35567-7a6a-4b1f-9795-a07d06dc2bdb
root@mcsiproxmox:/mnt/pve/vmimport/images#


--------------------------------------

And I have uploaded the VM configuration screenshot as attachment , in between I am trying to edit the guestOS field of the .vmx file and re-generate the vmdk file again using ovftool. Will keep posted

Thank you so much for help !

Try:
- Assuming you don't need them, remove the VirtIO .iso and the Windows Installer .iso (Likely won't fix the problem but good housecleaning none the less)
- Change the SCSI controller to VMWare PVSCSI
- Detach (Click on the disk, then click 'Detach') the OS disk and re-attach it using the bus/device option "SCSI"

 

[yatcvic]

Thank you so much bro !

After modified the guest os field from "longhorn" to "windows7srv-64" in the .vmx file , then re-export the .ova file again , and put it back into Proxmox, it is worked now!

Even I found some missing drivers while booting up but I have fixed it by installed virtio drivers manually.

Thanks again bro! If you dont talk about the .vmx file checking I even cannot find the guest os is something kind of different !