[SOLVED] GPU passthrough 43 error when adding the hypervisor flag

gerhardt

New Member
Mar 29, 2020
7
0
1
32
I installed a win10 guest and passed throught a nvidia gpu to it. Everything works fine with the following configuration:
Code:
bios: ovmf
boot: d
cores: 12
cpu: host
hostpci0: 0a:00,pcie=1
hostpci1: 01:00,pcie=1,x-vga=1
hostpci2: 05:00,pcie=1
machine: q35
memory: 49152
name: Win10
net0: e1000=E2:D2:23:F8:9F:4E,bridge=vmbr2
numa: 0
onboot: 1
ostype: win10
scsi1: /dev/disk/by-id/usb-EAGET_G70_HDD_000000004974-0:0,size=976762584K
scsihw: virtio-scsi-pci
smbios1: uuid=b1b0d04a-ddb2-4f6b-a9f4-9c878479e23b
sockets: 1
usb0: host=1-3,usb3=1
usb1: host=1-4,usb3=1
usb2: host=1-7,usb3=1
usb3: host=1-14,usb3=1
vmgenid: 45c3067b-f47b-41a1-9cb0-79a626e44c66

I enable the nested virtualization and edit the vm config file to remove the hypervisor flag from cpu with args:
Code:
args: -cpu host,-hypervisor

then when I start the vm, the nvidia gpu stops working with 43 error. Does the x-vga conflict with the cpu args? Why it stops working when I just added a flag to cpu with the x-vga remains on?

Can anyone please help out making the gpu working with the hypervisor flag removed from cpu?

Thanks in advance.
 
the nvidia gpu stops working with 43 error
error 43 is just a generic driver error, it can have many different reasons

why do you need the '-hypervisor' flag? any particular reason?

if you need it, i would look at what we set by default
you can see the full command with
Code:
qm showcmd ID --pretty

find the line with '-cpu' then copy and modify it and put it into your args
 
error 43 is just a generic driver error, it can have many different reasons

why do you need the '-hypervisor' flag? any particular reason?

if you need it, i would look at what we set by default
you can see the full command with
Code:
qm showcmd ID --pretty

find the line with '-cpu' then copy and modify it and put it into your args
I want to install hyper-v in the win10 guest. I tried your method and it works! It seems that my cpu args in conf file override the default cpu flag. Anyway, thank you for your help.
 
mhmm... we probably could include the 'hypervisor' flag in our supported cpu flag list, so that you can do it like:

Code:
cpu: host,flags=-hypervisor

instead of messing around with args

can you open an enhancement request at https://bugzilla.proxmox.com ?
 

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!