Hi,
For your information, this matches the known [0] `ntfs3` file-restore limitation, and an `ntfs-3g` fallback patch [1] series has been proposed but is not released yet.
[0] https://bugzilla.proxmox.com/show_bug.cgi?id=7544
[1]...
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...
Glad to hear that you solved the issue yourself! good catch :) and thank you for posting the fix.
I will go ahead and set your thread as [SOLVED] to help other people who have similar issue.
Have a nice weekend.
Glad to hear that you solved yourself!
Thank you for sharing the solution as well. I will set your thread as [SOLVED] to help poeple who have the similar issue.
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...
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...
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...
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 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...
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...
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
Today we're introducing a dedicated repository for debug symbol packages, reachable at https://dbgsym.proxmox.com/.
Debug symbol packages (named <package>-dbgsym) contain the detached debug information for their matching binary package. They are...
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...
Today, we announce the availability of a new archive CDN dedicated to the long-term archival of our old and End-of-Life (EOL) releases.
Effective immediately, this archive hosts all repositories for releases based on Debian 10 (Buster) and older...
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...
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...