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...
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...
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?
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...
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.
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...
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...
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...
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.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.