Search results

  1. M

    PVE 6.2 GPU PCIe Passtrough issue

    I will test the NoMachine solution that you offer me and I will get back to you as soon as it is done
  2. M

    PVE 6.2 GPU PCIe Passtrough issue

    I don't know, I would have to do LAN tests. Anyway it works pretty well
  3. M

    PVE 6.2 GPU PCIe Passtrough issue

    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)
  4. M

    PVE 6.2 GPU PCIe Passtrough issue

    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?
  5. M

    PVE 6.2 GPU PCIe Passtrough issue

    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?
  6. M

    PVE 6.2 GPU PCIe Passtrough issue

    I just picked up an EVGA 1060 3GB SuperClocked. Normally the bios is UEFI compatible, but I don't know how to check it. I'm a taker if you have an idea? I connect a screen to the HDMI of the 1060 and I configure my VM before launching it. Here is the .conf: agent: 1 args: -cpu...
  7. M

    PVE 6.2 GPU PCIe Passtrough issue

    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 ?
  8. M

    PVE 6.2 GPU PCIe Passtrough issue

    My new test VM with Seabios result error code 43 too :( I try a lot of tips, but nothing to do...
  9. M

    PVE 6.2 GPU PCIe Passtrough issue

    Good question. I don't know. Where is this option ? What's the impact ?
  10. M

    PVE 6.2 GPU PCIe Passtrough issue

    Unfortunatly, no. It seems like PVE natively hide the VM to the nvidia's driver. When I install manually the nvidia's driver, error code 43 disappears on devices manager, but after restart, code 43 is already here. I'll create now a Seabios Win 10 VM for test (need to reinstall Win)
  11. M

    PVE 6.2 GPU PCIe Passtrough issue

    Apparently you have to get the Nvidia driver to believe that it is not in a VM :oops: I also read something that appeals to me: GPUs before 7xx are not compatible with OVMF, only Seabios. Is it true ? :rolleyes: Edit : My first test is to install the Nvidia driver manually on my OVMF VM
  12. M

    PVE 6.2 GPU PCIe Passtrough issue

    This is just what I'm doing... Not easy
  13. M

    PVE 6.2 GPU PCIe Passtrough issue

    my new VM .conf : I added cpu: host,hidden=1,flags=+pcid and hostpci0: 01:00,pcie=1,x-vga=on root@ATLANTA:~# nano /etc/pve/qemu-server/702.conf GNU nano 3.2 /etc/pve/qemu-server/702.conf agent: 1 audio0: device=intel-hda,driver=spice bios: ovmf bootdisk: virtio0 cores: 4 cpu...
  14. M

    PVE 6.2 GPU PCIe Passtrough issue

    Sorry if I am not precise enough in my answers. I execute on the Putty console echo "options kvm ignore_msrs=1" > /etc/modprobe.d/kvm.conf OK I'll add softdep in vfio.conf hostpci0 does not appear, perhaps because I don't passthroug my GPU on this VM for the moment ?
  15. M

    PVE 6.2 GPU PCIe Passtrough issue

    Yes I was wrong with mobprode, you're right ! Full VM config : root@ATLANTA:~# nano /etc/pve/qemu-server/702.conf GNU nano 3.2 /etc/pve/qemu-server/702.conf agent: 1 audio0: device=intel-hda,driver=spice bios: ovmf bootdisk: virtio0 cores: 4 efidisk0...
  16. M

    PVE 6.2 GPU PCIe Passtrough issue

    Hi, Here is my VM config root@ATLANTA:~# nano /etc/pve/qemu-server/702.conf GNU nano 3.2 /etc/pve/qemu-server/702.conf agent: 1 audio0: device=intel-hda,driver=spice bios: ovmf bootdisk: virtio0 I try to assign my GPU but there is an error : root@ATLANTA:~# echo "options...
  17. M

    PVE 6.2 GPU PCIe Passtrough issue

    Hello, I don't know how you know this command, but it cannot be invented! I would not have found it alone, that's for sure. Thank you for your help. Here my Putty output : login as: root root@192.168.1.10's password: Linux ATLANTA 5.4.65-1-pve #1 SMP PVE 5.4.65-1 (Mon, 21 Sep 2020 15:40:22...