[SOLVED] Help Proxmox dies when I start the Windows 11 VM

[helgisnw]

Hi I installed proxmox ve 8.0.3 on
intel D-1581
4HDD 1SSD
samsung 64GB DDR3L
Gtx 1660super
Gtx 770
system

due to the driver issue, I installed with nomodeset

after that the xpenology and hackintosh vm worked fine(with little bit of problem like vm shutdown or delete vm not working) , but after I made win11 vm and finished setting vm, my whole server has died. What’s the probelm….

 

[leesteken]

It's not clear to me if you mean that your hardware is no longer working or Proxmox crashes/freezes when you start a VM or whether Proxmox does not boot anymore. Each case has very different answers. If might help you can tell what you changed before it "died". If enough can still run, maybe you can share the IOMMU groups and VM configuration file?

 

[helgisnw]

It's not clear to me if you mean that your hardware is no longer working or Proxmox crashes/freezes when you start a VM or whether Proxmox does not boot anymore. Each case has very different answers. If might help you can tell what you changed before it "died". If enough can still run, maybe you can share the IOMMU groups and VM configuration file?

All server freezes. If I force shutdown the whole server and reboot Proxmox, it does work until I restart the windows vm. When it freezes I can’t even access to ssh or type on server’s terminal

 

[helgisnw]

I can’t even see the iommu group it won’t show group just devices

 

[leesteken]

All server freezes. If I force shutdown the whole server and reboot Proxmox, it does work until I restart the windows vm. When it freezes I can’t even access to ssh or type on server’s terminal

Sounds like you are doing passthrough of a device in an IOMMU group that also contains essential devices for the Proxmox host like network and storage controllers. Since you cannot share a group between VMs and/or the Proxmox host, Proxmox will lose the drives and network connection unexpectedly and crash/freeze.

I can’t even see the iommu group it won’t show group just devicesView attachment 53901

This looks like IOMMU/VT-d is not enabled, and PCIe passthrough won't even work (VM should fail to start). What is the output of cat /proc/cmdline when Proxmox starts normally?
What does the Windows VM configuration look like (qm config)? Looks like you already found the nice command for showing the IOMMU groups (for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci -nns "${d##*/}"; done). Maybe you could use SSH and copy-paste the text in CODE-tags instead of screenshots, after IOMMU/VT-d is enabled again?

 

[helgisnw]

Sounds like you are doing passthrough of a device in an IOMMU group that also contains essential devices for the Proxmox host like network and storage controllers. Since you cannot share a group between VMs and/or the Proxmox host, Proxmox will lose the drives and network connection unexpectedly and crash/freeze.

This looks like IOMMU/VT-d is not enabled, and PCIe passthrough won't even work (VM should fail to start). What is the output of cat /proc/cmdline when Proxmox starts normally?
What does the Windows VM configuration look like (qm config)? Looks like you already found the nice command for showing the IOMMU groups (for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci -nns "${d##*/}"; done). Maybe you could use SSH and copy-paste the text in CODE-tags instead of screenshots, after IOMMU/VT-d is enabled again?

First, I only did the HDD passthrough(Not to the windows vm to the xpenology). I check the iommu group because I saw the solution that if the HDD and the lan card’s iommu group is same, lan host pc’s lan can die(is it true?).

I tried to find the iommu stuff but the Due to Chinese main board (or the bios hidden setting) I failed I’ll re check the bios again.
However if there is no option on the mainboard, should I need to edit the bios(Aptio setup utility) to show the iommu option?

Sorry for my bad English(I’m not native speaker)

 

[maomaocake]

to oversimplify Iommu pass through you can only pass through groups of devices which means that what you read is true.

Since you say you are using a Chinese motherboard I will assume that vt-d is already Enabled (go to cpu setting and find anything that says Vanderpool) since that is usually how the bios of these boards come.

my suggestion to you is that you try to see that your /etc/kernel/cmdline has the following lines

intel_iommu=on iommu=pt



ps I'm sorry for my poor formatting I'm on mobile

 

[leesteken]

First, I only did the HDD passthrough(Not to the windows vm to the xpenology). I check the iommu group because I saw the solution that if the HDD and the lan card’s iommu group is same, lan host pc’s lan can die(is it true?).

I tried to find the iommu stuff but the Due to Chinese main board (or the bios hidden setting) I failed I’ll re check the bios again.
However if there is no option on the mainboard, should I need to edit the bios(Aptio setup utility) to show the iommu option?

Sorry for my bad English(I’m not native speaker)

This looks like IOMMU/VT-d is not enabled, and PCIe passthrough won't even work (VM should fail to start). What is the output of cat /proc/cmdline when Proxmox starts normally?
What does the Windows VM configuration look like (qm config)?

Please show the output of cat /proc/cmdline or explain why you cannot do that.

 

[helgisnw]

Actually.. I just downgraded the Proxmox to 7.4-3 and it works. thanks for help!!