Hi Everyone
I've successfully gotten my LSI 9211-8i passed through to my freenas VM, running Proxmox 4.2-17/e1400248. My issue is that when I start the vm from the gui or qm start 100 command I get the following:
However, if I run the /usr/bin/kvm... command from that error, it will start up fine, it seems that the delay is coming from the passthrough, because if i remove the hostpci entry it works.
My question is, can this timeout be modified easily, my google searches have been fruitless. I'm fine with it taking an extra 5 seconds to start, but currently I have to ssh in and start it manually.
Barring that, is there anything I can tweak to make the passthrough quicker?
The system is:
2x Xeon E5645
Supermicro X8DTN+
144Gb DDR3 ecc reg
/etc/pve/qemu-server/100.conf (the vm in question):
dmesg | grep -e DMAR -e IOMMU
Thanks for any and all help, it is very much appreciated.
I've successfully gotten my LSI 9211-8i passed through to my freenas VM, running Proxmox 4.2-17/e1400248. My issue is that when I start the vm from the gui or qm start 100 command I get the following:
Code:
root@artemis:~# qm start 100
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' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=b9d43e1e-586a-40bd-9fe1-190015671575' -name Akashic -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 98304 -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=09:00.0,id=hostpci0,bus=pci.0,addr=0x10' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:9cdddb3d2cf5' -drive 'file=/dev/zvol/rpool/data/vm-100-disk-1,if=none,id=drive-virtio0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=3A:63:30:35:37:35,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=q35'' failed: got timeout
However, if I run the /usr/bin/kvm... command from that error, it will start up fine, it seems that the delay is coming from the passthrough, because if i remove the hostpci entry it works.
My question is, can this timeout be modified easily, my google searches have been fruitless. I'm fine with it taking an extra 5 seconds to start, but currently I have to ssh in and start it manually.
Barring that, is there anything I can tweak to make the passthrough quicker?
The system is:
2x Xeon E5645
Supermicro X8DTN+
144Gb DDR3 ecc reg
/etc/pve/qemu-server/100.conf (the vm in question):
Code:
balloon: 49152
bootdisk: virtio0
cores: 4
hostpci0: 09:00.0
machine: q35
memory: 98304
name: Akashic
net0: bridge=vmbr0,virtio=3A:63:30:35:37:35
numa: 0
ostype: other
smbios1: uuid=b9d43e1e-586a-40bd-9fe1-190015671575
sockets: 1
virtio0: local-zfs:vm-100-disk-1,size=64G
dmesg | grep -e DMAR -e IOMMU
Code:
root@artemis:~# dmesg | grep -e DMAR -e IOMMU
[ 0.000000] Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
[ 0.000000] ACPI: DMAR 0x00000000BF77E0E0 000144 (v01 AMI OEMDMAR 00000001 MSFT 00000097)
[ 0.000000] DMAR: IOMMU enabled
[ 0.170074] DMAR: Host address width 40
[ 0.170075] DMAR: DRHD base: 0x000000fbffe000 flags: 0x1
[ 0.170082] DMAR: dmar0: reg_base_addr fbffe000 ver 1:0 cap c90780106f0462 ecap f020fe
[ 0.170083] DMAR: RMRR base: 0x000000000e6000 end: 0x000000000e9fff
[ 0.170085] DMAR: RMRR base: 0x000000bf7ec000 end: 0x000000bf7fffff
[ 0.170086] DMAR: ATSR flags: 0x0
[ 0.170088] DMAR-IR: IOAPIC id 6 under DRHD base 0xfbffe000 IOMMU 0
[ 0.170090] DMAR-IR: IOAPIC id 7 under DRHD base 0xfbffe000 IOMMU 0
[ 0.170092] DMAR-IR: IOAPIC id 8 under DRHD base 0xfbffe000 IOMMU 0
[ 0.170094] DMAR-IR: IOAPIC id 9 under DRHD base 0xfbffe000 IOMMU 0
[ 0.170568] DMAR-IR: Enabled IRQ remapping in xapic mode
[ 1.116536] DMAR: dmar0: Using Queued invalidation
[ 1.116555] DMAR: Setting RMRR:
[ 1.116585] DMAR: Setting identity map for device 0000:00:1a.0 [0xbf7ec000 - 0xbf7fffff]
[ 1.116623] DMAR: Setting identity map for device 0000:00:1a.1 [0xbf7ec000 - 0xbf7fffff]
[ 1.116658] DMAR: Setting identity map for device 0000:00:1a.2 [0xbf7ec000 - 0xbf7fffff]
[ 1.116692] DMAR: Setting identity map for device 0000:00:1a.7 [0xbf7ec000 - 0xbf7fffff]
[ 1.116726] DMAR: Setting identity map for device 0000:00:1d.0 [0xbf7ec000 - 0xbf7fffff]
[ 1.116763] DMAR: Setting identity map for device 0000:00:1d.1 [0xbf7ec000 - 0xbf7fffff]
[ 1.116797] DMAR: Setting identity map for device 0000:00:1d.2 [0xbf7ec000 - 0xbf7fffff]
[ 1.116832] DMAR: Setting identity map for device 0000:00:1d.7 [0xbf7ec000 - 0xbf7fffff]
[ 1.116854] DMAR: Setting identity map for device 0000:00:1a.0 [0xe6000 - 0xe9fff]
[ 1.116868] DMAR: Setting identity map for device 0000:00:1a.1 [0xe6000 - 0xe9fff]
[ 1.116883] DMAR: Setting identity map for device 0000:00:1a.2 [0xe6000 - 0xe9fff]
[ 1.116897] DMAR: Setting identity map for device 0000:00:1a.7 [0xe6000 - 0xe9fff]
[ 1.116912] DMAR: Setting identity map for device 0000:00:1d.0 [0xe6000 - 0xe9fff]
[ 1.116926] DMAR: Setting identity map for device 0000:00:1d.1 [0xe6000 - 0xe9fff]
[ 1.116940] DMAR: Setting identity map for device 0000:00:1d.2 [0xe6000 - 0xe9fff]
[ 1.116955] DMAR: Setting identity map for device 0000:00:1d.7 [0xe6000 - 0xe9fff]
[ 1.117014] DMAR: Prepare 0-16MiB unity mapping for LPC
[ 1.117031] DMAR: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[ 1.117168] DMAR: Intel(R) Virtualization Technology for Directed I/O
[ 11.497445] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
[ 11.497447] AMD IOMMUv2 functionality not available on this system
Thanks for any and all help, it is very much appreciated.
Last edited: