Intel code 43

Zoxfee

New Member
Jul 27, 2020
8
0
1
21
I've looked through a number of posts here on passthrough. Most mention nvidia but a few go through the integrated graphics.
Some of the settings I have used caused crashes and non-boots, others have brought up the the brink of success halted by the "code 43" error.
I have followed the wiki (blacklisting modules, modifying grub, proper vfio config)

Legacy boot (BIOS) for host, SeaBIOS for the guest

proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.2-10 (running version: 6.2-10/a20769ed)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.1-1
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-9
pve-cluster: 6.1-8
pve-container: 3.1-12
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-11
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-11
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1

agent: 1
balloon: 2048
bootdisk: scsi0
cores: 2
ide2: local:iso/wind10act.iso,media=cdrom
ide3: local:iso/virtio-win.iso,media=cdrom,size=402812K
memory: 6144
name: Win10
net0: virtio=F6:41:3B:CC:53:DB,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: local-lvm:vm-100-disk-0,cache=writeback,discard=on,size=40G
scsihw: virtio-scsi-pci
smbios1: uuid=25701a31-bf12-42eb-b34f-40149a2b3237
sockets: 1
vmgenid: 074be4f3-1240-46a2-962e-9aec53117cf9
hostpci0: 00:02.0

I do not have "args" in the <vmid>.conf because I constantly had errors or noVNC would no longer work with them.
Adding the PCI device does have the device show up in the Device Manager of the guest, even recognize the device as "Intel HD 4600 graphics"
Manual installing the drivers from the Intel site does not help

List of tweaks that did not help:
  • Changing machine to "q35" causes a non-boot situation (fail to start QEMU ...)
  • Changing cpu type from default (kvm64) to host yields no changes, boots fine but still code 43
  • adding "x-vga=on" yields
    kvm: -device vfio-pci,host=0000:00:02.0,id=hostpci0,bus=pci.0,addr=0x10,x-vga=on: vfio 0000:00:02.0: failed getting region info for VGA region index 8: Invalid argumentdevice does not support requested feature x-vga
    TASK ERROR: start failed: QEMU exited with code 1
  • I've installed a dummy HDMI and has made no difference regardless of repeating any of the settings above

I am afraid I am missing something simple, or worse, I will not be able to passthrough the GPU.

Anyone with the same cpu had better luck?
 

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!