Search results

OMG I am feeling so stupid. The disks were indeed connected to the wrong controllers. :rolleyes: What a stupid mistake. I am sorry for wasting your time. With correct cabling everything works as expected now. Even without the changes in /etc/modprobe.d/

Before starting the VM: root@proxmox:~# ls -l /dev/disk/by-path/pci-* lrwxrwxrwx 1 root root 9 Oct 3 13:29 /dev/disk/by-path/pci-0000:00:12.0-ata-1 -> ../../sda lrwxrwxrwx 1 root root 9 Oct 3 13:29 /dev/disk/by-path/pci-0000:00:12.0-ata-1.0 -> ../../sda lrwxrwxrwx 1 root root 10 Oct 3 13:29...

After adding options vfio_pci ids=1b21:0612 the behavior was exactly the same. After adding the second line softdep ahci pre: vfio_pci the system did not boot anymore. It did not find volume group "pve" anymore. So it seems that this command also affects the system SATA controller...

Both SATA controllers use the same kernel module "ahci", so I guess blacklisting the module is not an option. Which IDs should I use for options vfio_pci ids=1b21:0612 in my system? 0000:0400?

SATA Controller seems to be in a single group 14 without any other devices. Ethernet controllers and the system SATA controller are in different groups. root@proxmox:~# for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci...

Hi, although this is not my thread I have a similar issue. How can I blacklist my ASM1062 controller? root@proxmox:~# lspci -tv -[0000:00]-+-00.0 Intel Corporation Gemini Lake Host Bridge +-00.1 Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal...

Hi, I am new to Proxmox and tried to pass through a SATA controller to a VM (OMV). I am using an J5040-ITX system. This system has two SATA controllers. (Intel + ASM1062) The Intel Controller is used for the Proxmox system and I want to pass through the ASMedia Controller to the VM. I did load...