Thank you for your attention. My problem is not with the settings. The VM simply does not boot, the VM does not load beyond the window with the Windows icon. I wanted to know, this is my problem or everyone else has this problem.
I can confirm that using x86-64-v2 on our lab-setup (old hardware) made the suspicious idle-usage dropping by 50%
I cannot turn off nested virtualization, so someone else have to confirm that this is a factor. Is not possible to disable...
How are the priorities and configuration of your actual rules? - what is Quarantine/Mark Spam (Level 6), what is your Whitelist rule?
(`pmgdb dump --rules active` provides a text overview)
I have a 3-node Proxmox cluster running on an HP C7000 chassis with three BL460 Gen10 blades. The shared storage is provided by an HPE 3PAR SAN. I've configured a shared LUN to host the virtual machines, and boot-from-SAN is working successfully...
I had the exact same issue (DMAR ERROR) installing 8.3.1 on a 12 year old Dell R710.
Adding "nomodeset intel_iommu=off" to the installer kernel command line solved it for me.
https://pve.proxmox.com/wiki/Installation#nomodeset_kernel_param
Thanks...
Hello elelayan! Ceph 17.2.8 is now be available for PVE 8 in the no-subscription repo.
You probably know already, but keep in mind that Ceph 17 is no longer maintained since January 2025, so please consider upgrading to Ceph 18 or 19. The wiki...
L40S seems to be supported by current driver version 18, so it should work. You can use it without licenses, i.e. to try if it works for you, but performance will be limited by the driver unless a Nvidia license is activated [1]
[1]...
We applied 17.2.8-pve2 Yesterday to our cluster: 19 hour uptime without any crash.
I'd say the patch is solid and fixes the issue.
Thank you again Laurențiu for releasing it
Thanks for the report! Due to the fact that there's no ETA from the upstream Ceph repository (especially because version 17 is EOL), we have cherry picked the fix ourselves and released the new version 17.2.8-pve2. It is currently available in...
We have a problem with our current backup(PBS-3.3.3-1).
We used to backup to two different Proxmox.
This worked fine despite the dirty bitmap.
After updating to 3.3 with the feature (backup: stat known chunks on backup finish) the problems...
For future readers: I faced this error message also, for one of my containers. Problem here was, that i edited the container config by hand:
root@pve:~# cat /etc/pve/lxc/105.conf
arch: amd64
cores: 1
features: nesting=1
hostname: testnode...