BIOS..Good question. I don't know. Where is this option ? What's the impact ?
Passthough should only work on full UEFI environment.My new test VM with Seabios result error code 43 too
I try a lot of tips, but nothing to do...
That is the setup I have with a 1080 being passed through. I believe the GPU rom needs to support UEFI, so any of the gtx series cards you mention should work.So, MB bios UEFI, PVE VM bios OVMF, and GPU vbios UEFI compatible ?
Do you think if I find a GTX 9xx/10xx that solve issue ?
agent: 1
balloon: 0
bios: ovmf
bootdisk: scsi0
cores: 8
cpu: host
efidisk0: VM:vm-101-disk-0,size=1M
hostpci0: 17:00,pcie=1,romfile=GTX1080.bin,x-vga=1
machine: q35
memory: 8192
name: Windows10
net0: virtio=,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
parent: Working_Configuration
sata0: none,media=cdrom
sata1: none,media=cdrom
scsi0: VM:vm-101-disk-1,cache=writeback,size=60G
scsihw: virtio-scsi-pci
smbios1: uuid=
sockets: 1
vmgenid:
That is the setup I have with a 1080 being passed through. I believe the GPU rom needs to support UEFI, so any of the gtx series cards you mention should work.
In fact I have two simultaneous and separate instances of windows 10 each with a dedicated GPU being passed through. For one of my cards, I did have to extract and specify the romfile in the vimd.conf file.
In my configuration the GPU pass-through works great, although windows 10 somehow still knows that its run on a virtual processor. I tried various flags to no avail.
Code:agent: 1 balloon: 0 bios: ovmf bootdisk: scsi0 cores: 8 cpu: host efidisk0: VM:vm-101-disk-0,size=1M hostpci0: 17:00,pcie=1,romfile=GTX1080.bin,x-vga=1 machine: q35 memory: 8192 name: Windows10 net0: virtio=,bridge=vmbr0,firewall=1 numa: 0 ostype: win10 parent: Working_Configuration sata0: none,media=cdrom sata1: none,media=cdrom scsi0: VM:vm-101-disk-1,cache=writeback,size=60G scsihw: virtio-scsi-pci smbios1: uuid= sockets: 1 vmgenid:
agent: 1
args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off'
audio0: device=intel-hda,driver=spice
bios: ovmf
bootdisk: virtio0
cores: 4
cpu: host,hidden=1,flags=+pcid
efidisk0: local-lvm:vm-702-disk-0,size=4M
hostpci0: 01:00,pcie=1,x-vga=on
machine: q35
memory: 4096
name: HomePlayStation
net0: virtio=3E:B8:E5:BE:B0:BA,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
sata2: none,media=cdrom
scsihw: virtio-scsi-pci
smbios1: uuid=53a650b1-d7ec-44a3-a391-9f47e31b7969
sockets: 1
vga: none
virtio0: local-lvm:vm-702-disk-1,cache=writeback,size=60G
vmgenid: d05a034a-62f8-41bf-84d1-4320ca2511af
You probably also want to pass through a USB-controller as well. Maybe one from your motherboard (check your IOMMU groups) or a PCIe-card (but search for a known to work card).On the other hand, I don't know how to use screen is mouse because I no longer have access from NoVNC ...
In fact, I would like not to have to plug a monitor into the server's 1060's HDMI, and be able to launch a game through Moonlight or Rainway, on my laptop.
So knowing that, do I have to plug a monitor into the 1060 and connect a keyboard mouse to the server?
I do not know. Good discovery ! I will test, but I don't feel it's optimized for gaming, unlike Parsec, Rainway etc ...
So if I use this kind of software, is there no need to do a keyboard / mouse passthrought?
Actually, I test Rainway and Moonlight (nvidia GPU only), and for now, both are free and very good for gaming. Good input lag, good graphics render, good compression when remote gaming via wifi (no test in WAN for now)
I don't know, I would have to do LAN tests.
Anyway it works pretty well