I created a Windows 11 and a Linux Mint VM on the same system.
The GPU is passed through to both VMs via passthrough, and the USB ports for the mouse and keyboard are routed from the host to the VM.
The GPU is an RX 6600XT installed on an Asus...
Just add iommu=pt at the end of the existing line. intel_iommu/amd_iommu is not needed.
You can check the current boot args with cat /proc/cmdline. Also see docs here.
No, as it would not make sense to disable power management for all SATA controllers. But drivers do get fixes, improvements and occasional new bugs on every new kernel version.
Please note that none of this is Proxmox specific as the PCI(e)...
Thank you.
Than I will stay with rombar=0 and try rombar=1 after the next big PVE update.
Maybe it will work than. Otherwise I hope I never get an problem with rombar=0.
And thanks again for your help with the other issue (other thread).
I...
Congratulations, your hardware works with PCI(e) passthrough which is unfortunately not that common.
Probably not. This is a common option to try enabled and/or disabled when doing PCI(e) passthrough.
Search for libata.force and then lookup...
Thank you, now I understand what I do, when setting libata.force=nolpm.
But I don't understand why deactivating the power management allows using rombar=1.
Could it be possible, that in earlier proxmox kernels the default value was...
You are right. I have the problem now.
So I opened a new thread, because I am not sure what is the better workaround .....
ASM1166 - No passthrough with rombar=1 possible - PVE9 bug?
Hello,
I want to passthrough an ASM1166 M.2.PCIe card to an VM.
It only works, if I set rombar=0.
Also it seems in PVE9 you don't have to blacklist the driver of the ASM1166, because PVE did this alone.
Is it new, that blacklisting the driver...
Hallo,
I passthrough my GPU on an AMD B550 board to an Win11 guest with PVE9.1.1.
Everything works, but in the manual is written, that i have to set "iommu=pt" to the kernel command line.
I have a zfs system. So in my opinion I have to set...
I did create this myself. It's just basic GNU/Linux scripting using Bash using the Proxmox command-line tools. There is a hookscript section in the manual: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_hookscripts
Thank you.
Did you create this yourself?
Or is there an overview with code examples somewhere, and how I can ultimately integrate it in the proxmox host?
Since I can't easily pass through two GPUs with my B550 motherboard, I'm looking for an alternative.
I'd like to create a hookscript that can do the following:
If VM1 is shut down, then start VM2.
AND
If VM2 is shut down, then start VM1...
Yes.
I cannot guarantee that there is no risk, as passing real hardware to a VM can interfere with the host. But without the pcie_acs_override, IOMMU should protect you from devices secretly communicating (and reading memory).
Sure, every system could have security issues.
But thanks to you, I now understand where the danger lies with ACS Override and when it might be acceptable.
Of course, only the user can make the final decision.
In principle software inside the VM can use the PCI(e) devices (passed through to the VM) to potentially read the all memory of the Proxmox host (via the devices still connected to the host).
Whether this actually works to read the host memory...
One last question.
This only applies if the ACS patch is active, right?
If you passthrough a GPU to a VM using the standard IOMMU groups (without patching), then there's no risk. Right?
You always get this because devices connected to/via B550 are not properly isolated.
You are not patching the kernel. You are enabling the "break the groups" that is already in the Proxmox kernel.
This is unsafe because it makes it look like...
Thank you, that I don't know.
Thank you, that is clear to me. Even though I find it very difficult to accurately assess the risk for my specific use case.
In my opinion it is very good, that in this forum the mebers tell us, that it is risky.
In...
This is to do to get IOMMU groups.
And in most cases you get a big IOMMU-chipset group with B550 boards.
Then you can brake this isolation an become virualized seperate IOMMU groups for the chipset group by patching the kernel with:
"quiet...