PCI GPU Passthrough

[Telemark]

Setting up GPU passthrough to a windows VM But now I'm stuck and just need a push in the right direction. Been reading the forums, but I'm no closer to fixing the issue

I'm getting this error, which looks like Ive got a config file wrong somewhere.

Task viewer: VM 104 - Start

OutputStatus
Stop
kvm: -device ide-cd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1: Can't create IDE unit 1, bus supports only 1 units
TASK ERROR: start failed: QEMU exited with code 1


Output from:
dmesg | grep -e DMAR -e IOMMU
[ 0.018649] ACPI: DMAR 0x000000002EFA0FC0 0000A8 (v01 INTEL NUC9i9QN 00000022 01000013)
[ 0.263046] DMAR: IOMMU enabled
[ 0.419878] DMAR: Host address width 39
[ 0.419879] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.419884] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
[ 0.419885] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.419889] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.419890] DMAR: RMRR base: 0x0000002f510000 end: 0x0000002f759fff
[ 0.419890] DMAR: RMRR base: 0x00000038800000 end: 0x0000003cffffff
[ 0.419892] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.419893] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.419893] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.423032] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 1.511178] DMAR: No ATSR found
[ 1.511257] DMAR: dmar0: Using Queued invalidation
[ 1.511260] DMAR: dmar1: Using Queued invalidation
[ 1.519665] pci 0000:00:1c.0: DMAR: Use Intel IOMMU bounce page dma_ops
[ 1.521879] pci 0000:03:00.0: DMAR: Use Intel IOMMU bounce page dma_ops
[ 1.522010] pci 0000:04:00.0: DMAR: Use Intel IOMMU bounce page dma_ops
[ 1.522118] pci 0000:04:01.0: DMAR: Use Intel IOMMU bounce page dma_ops
[ 1.522252] pci 0000:04:02.0: DMAR: Use Intel IOMMU bounce page dma_ops
[ 1.522359] pci 0000:04:04.0: DMAR: Use Intel IOMMU bounce page dma_ops
[ 1.522523] pci 0000:05:00.0: DMAR: Use Intel IOMMU bounce page dma_ops
[ 1.522660] pci 0000:39:00.0: DMAR: Use Intel IOMMU bounce page dma_ops
[ 1.523003] DMAR: Intel(R) Virtualization Technology for Directed I/O

Version:
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3



Any help appreciated.

Thanks

Andy

 

[dcsapak]

can you post the vm config?

qm config ID

 

[Telemark]

agent: 1
bios: ovmf
boot: order=ide0;ide2;net0
cores: 4
efidisk0: local-lvm:vm-104-disk-1,size=4M
hostpci0: 01:00,pcie=1
ide0: local-lvm:vm-104-disk-0,size=100G
ide1: ISO:iso/virtio-win-0.1.185.iso,media=cdrom,size=402812K
ide2: ISO:iso/Windows.iso,media=cdrom
machine: q35
memory: 8096
name: Win10
net0: e1000=BA:02:EA:67:83:20,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=30ed631b-6424-404c-ba84-fe3a14693fd9
sockets: 1
vga: virtio
vmgenid: 3c3fc076-ff2c-4d41-b491-57c36da7b437


Thank you

Andy

 

[dcsapak]

yeah, sadly with q35 you can only use 2 ide slots (qemu limitation)
i'd put the disk on scsi instead
and the cdroms on ide0 and ide2

alternatively it should be possible to put the isos into sata0/sata1

 

[Telemark]

Ok thanks will change the config...

Andy

 

[Telemark]

I did two things rebuilt a new win 10 with scsi for the hard disk, but I also deleted the IDE cdroms to get rid of the ide0 and ide2 for the original. The error no longer appears and It starts to boot. However the VM gets stuck with this (see attached) in the console and the VM doesn't boot. I know the console wont be working after the machine boots, Ive enabled remote login, but don't get that far.

The original machine has been put back to not using GPU passthrough and it boots normally

This happens on both VMs.........Slowly one step at a time.

Thanks again for any help.


Andy

 

[Telemark]

Rebuilt the Win 10 to get over the Uefi boot issues. Now the last item is code 43 on the card. Plenty of items on google to work through..

 

[Telemark]

Out of all the config files and different switches for grub config or VM config. All it took was a bios update for the host hardware. No code 43 error or any issues for the GPU passthrough with an Nvidia card.

 

[rifaterdemsahin]

moving to sata resolved this issue thanks