Thanks for the replies.
I want to add another datapoint.
I gave a backup of one of my affected AlmaLinux 8 VMs to a colleague, and he restored/tested it on two of his own Proxmox hosts.
Also, on the problematic AlmaLinux 8 servers, fsck has...
When host is used, there can be quirks that are not present with virtual models. I'm not betting on it resolving the issue, since multiple physical models are affected, but there is a chance and it is a valuable data point for the investigation.
Are you expected that 'non-host' / x86-64-v2-AES/x86-64-v3 should be less error prone than host? I would have suggested, that this is unexpected, but i follow your advice, if that is the case
The v3 model does include flags for avx, use v4 if you need the avx512 flags too, and a vendor-specific one close to your physical model will support those flags too.
@fabian we update our packages daily, within the VMs and on the proxmox server. So we updated to whatever was available to debian12 at this moment, including what is available for PVE.
The reason that this is cleary proxmox and not 'vm software'...
Hi,
@PVasileff are you also using the host CPU type for your VMs?
@ both, could you try with a different model like x86-64-v2-AES/x86-64-v3 or a vendor-specific one close to your physical model?
did you upgrade just the PVE packages, or also those inside the guest? which package updates exactly coincide with the start of the problems (keep in mind that kernel upgrades require a reboot, and pve-qemu-kvm updates will only affect newly...
We have the very same issue, while we rather use debian12 VMs in this regard. Segmentation faults are happening for different processes.
What we have tried:
latest PVE 7.x or 6.x kernel - happens on both - currently running 6.17.13-9-pve
we...
I would like to add one more important detail to the original post.
On the main Proxmox server where the random segmentation faults are observed in AlmaLinux 8 VMs, I also have other Linux virtual machines which do not show the same problem.
On...
Hello,
I am investigating an issue with AlmaLinux 8 virtual machines running on Proxmox VE. The symptom is not a full host freeze, but random segmentation faults inside the guest VMs. The segfaults happen in different applications and services...
Hallo zusammen,
bei Fsas / Fujitsu haben wir auch ein Whitepaper:
https://docs.ts.fujitsu.com/dl.aspx?id=c1444f2e-0146-4463-9bfd-9ec6a540a57d
mit den getesteten Konfigurationen.
Hier ist der CP300 ganz klar auch nur für RAID getestet.
Wir haben...
Hi Jürgen, eigentlich spricht ja nichts dagegen für das OS den kleinen Raid Controller mit den 2 NVMe drin zu lassen. Dai Dinger habe ich bei HPE und DELL Servern auch immer drin. Da einfach mit ext4 installieren und gut. Kommen ja eh keine VMs...
@Upstairs_Cycle384 Not sure why Windows still detects it, maybe querying the CPUID leaf directly still works or something. Regarding the other question, there is a custom CPU model editor coming with the next Proxmox VE 9.2 point release. There...
Is there any way to re-enable cet-ss? We have AMD processors in our shop and had no boot issues on Windows with VBS.
Besides reverting those Perl scripts that Fiona touched, I was wondering if there was a better way, perhaps through the VMs...
A patch: [1], thanks to @fiona, to "disable cet-ibt and cet-ss flags for modern Windows by default" is in qemu-server 9.1.12: [2], which already is available in pve-no-subscription.
[1]...
@fw1976 I should probably continue this discussion in the thread you started, but there are still some issues with Qemu11.
Boot loops and startup failures are still occurring on virtual machines with HVCI and RDS roles added.
*This also happens...
https://forum.proxmox.com/threads/windows-server-2025-standard-startet-nach-heutigem-update-nicht-mehr.183503/
@proxmox Support: 22 x Intel(R) Core(TM) Ultra 9 185H (1 Socket) ist my Host. If you need more information, please let me know exactly...