Recent content by Moayad

Thank you! [ 759.647977] i915 0000:00:02.0: driver does not support SR-IOV configuration via sysfs [ 812.413565] i915 0000:00:02.0: driver does not support SR-IOV configuration via sysfs [ 916.467261] i915 0000:00:02.0: driver does not support SR-IOV configuration via sysfs [ 1000.807451]...

Could you remove the `i915.enable_gvt=1` from the kernel CLI and then try the `echo 1 > /sys/bus/pci/devices/0000:00:02.0/sriov_numvfs` again? If still print error, please the output of `dmesg` You have to initramfs afterwards or reboot the Proxmox VE node.

Thank you! Could you remove the PCI device from the VM 100 and then run `echo 1 > /sys/bus/pci/devices/0000:00:02.0/sriov_numvfs`? make sure that the VM is stop. Then post the output of `cat /sys/bus/pci/devices/0000:00:02.0/sriov_numvfs` and `lspci -nnk`

Oh forget that you posted already! Could you please post the output of: cat /sys/bus/pci/devices/0000:00:02.0/sriov_totalvfs cat /sys/bus/pci/devices/0000:00:02.0/sriov_numvfs

Thank you for testing! Now could you please provide us the VM config `qm config <VMID>`?

Thank you for log! If the `8086:4626` is added to `/etc/modprobe.d/vfio.conf ` please also remove it, then update initramfs and reboot the node, then check that `lspci -nnk` shows `i915` instead of `vfio-pci`.

Thank you for the output! I would undo the `i915` blacklist binding so `00:02.0` is handled by node driver again, then post `cat /sys/bus/pci/devices/0000:00:02.0/sriov_totalvfs` and `cat /sys/bus/pci/devices/0000:00:02.0/sriov_numvfs`. Have you checked the Error 43 [0] in our wiki guide...

Hi, Could you please post the output of the following: pveversion -v qm config <VMID> lspci -nnk I would also check if the `/sys/bus/pci/devices/0000:00:02.0/sriov_totalvfs` exists, you can do `ls -la /sys/bus/pci/devices/0000:00:02.0/sriov_totalvfs` from your Proxmox VE node.

Hi, If you are use mdraid for `/boot` I would suggest migrating or reinstalling a supported layout, e.g., ZFS. Because mdraid is not supported [0]. [0] https://pve.proxmox.com/wiki/Software_RAID

I would also check the temperature when the issue happened.

I would focus on the power path first, PSU, UPS, as well as the power cables. Because this is not a Proxmox VE issue from the logs you've provided I saw. Or if possible, test with another PSU or temporarily reduce the load by disconnecting some Hardware like GPU etc..

Hi, have you checked the syslog when the VM shutdown? you can check using journalctl with specific time if you know the exact time e.g: journalctl --since "2026-07-09 13:00" --until "2026-07-09 14:00" > /tmp/$(hostname)-syslog.txt Modify the date/time in the above command. I would also check...

The logs run normally then immediately starts a new boot, without the usual systemd, pve-guests, or shutdown messages. I would check the hardware. So please check the UPS log and any BIOS, IPMI, or iDRAC event logs around that time. The LXC error for container 103 is likely a separate. However...

You can open an enhancement request in our BugZilla [0] [0] https://bugzilla.proxmox.com/

yeah, full clone only setups reduce the risk, but templates can back linked clones, so the API stays conservative. Editing config files may work, but it bypasses normal checks and it unsupported.