Recent content by azeth

  1. A

    Error encountered on upgrade to new proxmox kernel 6.5.13-3-pve

    Hello. I have set up gpu passthrough on my workstation computer, all working fine on kernel version 6.5.13-1-pve, but after upgrading to 6.5.13-3-pve I started having problems to run gaming VM second time after host reboot (the display stops initializing). Pinning the kernel back to 6.5.13-1-pve...
  2. A

    VirtioFS support

    Would be very nice if the required tool (virtiofsd) went into QEMU 5.2 package that is going to be released next, it's already incorporated into debian packages qemu-system-common https://packages.debian.org/buster-backports/amd64/qemu-system-common/filelist Thanks for all the work put into...
  3. A

    VirtioFS support

    Hi, do you have any suggestions how to ensure virtiofsd runs before VM starts on pve and restarts every time VM is rebooted? Is there any pre/post start/stop hook I can access? Any plans this feature will make it into future Proxmox release along with newer QEMU versions?
  4. A

    [SOLVED] noVNC encountered an error on Chrome

    Thanks a lot, problem resolved. It was due to one of my recently installed extensions: Video Downloader by Skyload.
  5. A

    [SOLVED] noVNC encountered an error on Chrome

    Today upon login on my proxmox server when opening on every VM noVNC console I get the following error on Google Chrome [Version 86.0.4240.111 (Official Build) (64-bit)]. I have never seen such error before. I tried emptying browser cache and downloaded files, restarting the browser, to no...
  6. A

    IGD Passthrough setup broke with Proxmox 6.2

    Seems like the only option of successfully passing through is without specifying "addr=0x02", the windows then boots successfully, but we need second virtual card. Yikes, not good.
  7. A

    IGD Passthrough setup broke with Proxmox 6.2

    I resolved the issue of VM refusing to start by adding vfio-pci.ids=XXX to: /etc/default/grub GRUB_CMDLINE_LINUX="root=ZFS=rpool/ROOT/pve-1 boot=zfs kvm.ignore_msrs=1 intel_iommu=on video=vesafb:off,efifb:off vfio-pci.ids=8086:3e92,8086:a2c9,8086:a2a1,8086:a2f0,8086:a2a3,8086:24fd" The problem...
  8. A

    IGD Passthrough setup broke with Proxmox 6.2

    I have to correct my earlier statement, the VM started on 5.3.18-3-pve after changing booted kernel, but it is stuck on endless bootloop, 100% usage of 1 core, no output on hdmi. I did not rollback any packages to earlier version, just edited boot options. Contents of relevant boot files...
  9. A

    IGD Passthrough setup broke with Proxmox 6.2

    qemu-server config file: (IGD passthrough is done using legacy mode, worked perfectly on proxmox 6.1 with full 4K display) agent: 1,fstrim_cloned_disks=1 args: -device vfio-pci,host=00:02.0,addr=0x02,x-igd-gms=1 -device vfio-pci,host=00:1f.3 -cpu...
  10. A

    IGD Passthrough setup broke with Proxmox 6.2

    Unfortunately I have the same problem. Relevant startup line: -device vfio-pci,host=00:02.0,addr=0x02,x-igd-gms=1 And response: failed to open /dev/vfio/1: No such file or directory TASK ERROR: start failed: QEMU exited with code 1 I went back to 5.3.18-3-pve, but it didn't resolve the issue.

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!