PCI Passthrough Error on Hetzner server

ggsmarket

Member
Oct 9, 2014
37
0
6
vpscheaper.com
Hi,

My current server i7-2600 dedicated server

I installed Proxmox 3.4 and Kernel 3.10-8-pve

My root@test ~ # lspci
Code:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5)
00:1c.7 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
05:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01)

My root@test ~ # lspci -n
Code:
00:00.0 0600: 8086:0100 (rev 09)
00:01.0 0604: 8086:0101 (rev 09)
00:02.0 0300: 8086:0102 (rev 09)
00:16.0 0780: 8086:1c3a (rev 04)
00:1a.0 0c03: 8086:1c2d (rev 05)
00:1c.0 0604: 8086:1c10 (rev b5)
00:1c.5 0604: 8086:1c1a (rev b5)
00:1c.6 0604: 8086:1c1c (rev b5)
00:1c.7 0604: 8086:244e (rev b5)
00:1d.0 0c03: 8086:1c26 (rev 05)
00:1f.0 0601: 8086:1c4a (rev 05)
00:1f.2 0106: 8086:1c02 (rev 05)
00:1f.3 0c05: 8086:1c22 (rev 05)
03:00.0 0c03: 1b21:1042
04:00.0 0200: 10ec:8168 (rev 06)
05:00.0 0604: 1b21:1080 (rev 01)

My root@test ~ # pveversion -v
Code:
proxmox-ve-2.6.32: 3.4-156 (running kernel: 3.10.0-8-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-39-pve: 2.6.32-156
pve-kernel-3.10.0-8-pve: 3.10.0-30
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

I tried to run 3 lines to fix intel-IOMMU. But i failed
Code:
    # echo "8086 0102" > /sys/bus/pci/drivers/pci-stub/new_id
    # echo 0000:00:02.0 > /sys/bus/pci/devices/0000:00:02.0/driver/unbind
    # echo 0000:00:02.0 > /sys/bus/pci/drivers/pci-stub/bind
When i type "dmesg | grep -e DMAR -e IOMMU" to check IOMMU and see it is enabled.
Code:
[    0.000000] ACPI: DMAR 00000000ceb9af60 000B0 (v01 INTEL      SNB  00000001 INTL 00000001)
[    0.000000] Intel-IOMMU: enabled
[    0.024622] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020e60262 ecap f0101a
[    0.024626] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap c9008020660262 ecap f010da
[    0.024697] IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.623911] DMAR: No ATSR found
[    0.623931] IOMMU 0 0xfed90000: using Queued invalidation
[    0.623932] IOMMU 1 0xfed91000: using Queued invalidation
[    0.623933] IOMMU: Setting RMRR:
[    0.623940] IOMMU: Setting identity map for device 0000:00:02.0 [0xcf800000 - 0xdf9fffff]
[    0.625055] IOMMU: Setting identity map for device 0000:00:1a.0 [0xce8d1000 - 0xce8dffff]
[    0.625070] IOMMU: Setting identity map for device 0000:00:1d.0 [0xce8d1000 - 0xce8dffff]
[    0.625078] IOMMU: Prepare 0-16MiB unity mapping for LPC
[    0.625084] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[ 4370.645638] vfio-pci 0000:00:02.0: Device is ineligible for IOMMU domain attach due to platform RMRR requirement.  Contact your platform vendor.

My error is here
Code:
[COLOR=#000000][FONT=tahoma]kvm: -device vfio-pci,host=00:02.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: vfio: failed to set iommu for container: Operation not permitted[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]kvm: -device vfio-pci,host=00:02.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: vfio: failed to setup container for group 2[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]kvm: -device vfio-pci,host=00:02.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: vfio: failed to get group 2[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]kvm: -device vfio-pci,host=00:02.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: Device initialization failed.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]kvm: -device vfio-pci,host=00:02.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: Device 'vfio-pci' could not be initialized[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=35574346-d3a1-4d03-91a7-2f9075e8b4b0' -name NBe -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -no-hpet -cpu 'kvm64,hv_spinlocks=0xffff,hv_relaxed,+lahf_lm,+x2apic,+sep' -m 20480 -k en-us -readconfig /usr/share/qemu-server/pve-q35.cfg -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=00:02.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:a032d5374' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-ide0,format=raw,aio=native,cache=none,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=user,id=net0,hostname=NBe' -device 'e1000,mac=1E:38:57:81:18:82,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=q35' -global 'kvm-pit.lost_tick_policy=discard'' failed: ex[/FONT][/COLOR]

My 100.conf
Code:
bootdisk: ide0cores: 8
ide0: local:100/vm-100-disk-1.raw,size=300G
ide2: local:iso/en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso,media=cdrom
memory: 20480
name: NBe
net0: e1000=1E:38:57:81:18:82
numa: 0
ostype: win7
smbios1: uuid=35574346-d3a1-4d03-91a7-2f9075e8b4b0
sockets: 1
machine: q35
hostpci0:00:02.0,pcie=1,driver=vfio

Please help me enable my VGA....
 
A new Error :

Running as unit 100.scope.
TASK ERROR: start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 100 -p 'CPUShares=1000' /usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=85f78f30-dd52-4f00-8ac1-8350a0163b87' -name TEST -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga none -no-hpet -cpu 'kvm64,kvm=off,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce' -m 20480 -k en-us -readconfig /usr/share/qemu-server/pve-q35.cfg -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=00:02.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0,x-vga=on' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:419abd2e73' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-ide0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=user,id=net0,hostname=TEST' -device 'e1000,mac=A2:23:BF:F5:0E:FB,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=q35' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout

And my server was restarted with out reason....
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!