Search results

  1. T

    Intel B50pro passthrough.

    Here are the settings i have. I have secureboot on so I am using grub. cmdline: intel_iommu=on iommu=pt /etc/modules vfio vfio_iommu_type1 vfio_pci vfio_virqfd I recommend installing intel graphic firmware apt install firmware-intel-graphics I dont know if it will help but wont hurt. After...
  2. T

    Intel B50pro passthrough.

    There isn't any specific ones for intel cards I use. I dont have access to my computer remotely. I can get all the information on how mine is set up, later today. When you had the code 43 error in windows, what did the windows event viewer say? What did the dmesg in linux say when turning on...
  3. T

    Intel B50pro passthrough.

    Let's not blacklist 'xe'.
  4. T

    Intel B50pro passthrough.

    Thats great! For some reason, your computer is not reinitializing the pci bus. Let me look into that. I know Dells have boot delay option in bios. Try that. I never got code 43 with intel cards / intel igp. Do you have all the modules config done and kernel cmdline options configured?
  5. T

    Intel B50pro passthrough.

    The B50 is located in 03:00.0. From what i gather it is connected to the correct pcie slot. For a mini computer, not really much of a option. Lets try this echo "1" > /sys/bus/pci/rescanthen check for 03:00.0 if it shows up.
  6. T

    Intel B50pro passthrough.

    Thanks for the info. I know this is going to be annoying, but if you can get back to windows can you go to device manager and right click on B50 card and go to properties. Send me this info: I am trying to get an idea how your computer is setup internally.
  7. T

    Intel B50pro passthrough.

    check the lspci.txt file
  8. T

    Intel B50pro passthrough.

    That doesnt seem like a complete list. lspci -M > lspci.txt
  9. T

    Intel B50pro passthrough.

    You ran the wrong command this time. it is capital M not m
  10. T

    Intel B50pro passthrough.

    That error is normal. lspci by itself doesn't show everything sometimes.. -M is more thorough. If you can get that output in a text file and attach it.
  11. T

    Intel B50pro passthrough.

    It will work without rebar. This might be a long shot but can you attach the file for this command lspci -M
  12. T

    Intel B50pro passthrough.

    When you tested out with windows, did you install the arc pro drivers? And it showed B50 in the Intel Command Center? I received my B50 two weeks ago and I had to do a firmware update in windows for it to work fully. Installing the intel arc pro drivers installs the firmware as part of the...
  13. T

    Intel B50pro passthrough.

    In proxmox shell type in uname -r
  14. T

    VM Internal Error

    So I take that back on the the statement it is working with the newer firmware. It randomly started to freeze up again. I did notice, after few freezes and stopping and starting the VM again, eventually it works fine for a while.
  15. T

    Intel B50pro passthrough.

    I didn't see this anywhere, what is your kernel version?
  16. T

    VM Internal Error

    Thanks for the reply. So I downloaded the latest linux-firmware from git and extracted the latest xe firmware to /lib/firmware file. So far havent had any issues with vm crashing for a week now. Interestingly, updating the kernel will remove the newer firmwares, so I have to copy the files over.
  17. T

    Intel Arc Pro B50 - xe driver not binding on PVE host

    B50 will not have a dri device. It doesnt not have any video output. Did you try with xe.vram_bar_size=256
  18. T

    VM Internal Error

    This is what it shows after the VM becomes unresponsive. Feb 01 12:31:22 pve QEMU[1683917]: error: kvm run failed Bad address Feb 01 12:31:22 pve QEMU[1683917]: RAX=ffff82f14c229500 RBX=ffffb3867e10c000 RCX=ffffb3867e10c000 RDX=0000000000000000 Feb 01 12:31:22 pve QEMU[1683917]...
  19. T

    Intel Arc Pro B50 - xe driver not binding on PVE host

    do you have non-free-firmware in debian apt sources? pve-firmware package installed? I would also make sure it is not set as boot vga in bios and everything set to EFI and above 4G decoding. If those fails then try xe.vram_bar_size=256 in kernel cmdline