Topic: Proxmox settings

[beast]

Hi everyone,

I wanted to share a working configuration for running Koozali SME Server 11 rc1 on Proxmox VE, after battling severe installer crashes (Anaconda PayloadError), drive dropouts, and GRUB boot loops.

The underlying enterprise kernel in SME 11 struggles with aggressive paravirtualized hardware emulation under heavy disk load. Moving to a standard SATA bus and mapping the CPU directly fixes this I think.

Here are my VM settings:

OS: Linux (Standard 6.x - 2.6 Kernel profile)

BIOS: OVMF (UEFI). SME 11 formats larger disks with GPT during installation. SeaBIOS will sometimes drop you into a 'grub>' prompt; UEFI fixes this. (Remember to add an EFI Disk on your storage).

CPU Type: 'host'. Avoid the default kvm64 emulation. Letting the SME kernel see the real host CPU flags completely stops the installer kernel panics.

Memory: 4096 MB or 8192 MB. Disable "Ballooning Device" (Unchecked) to prevent the guest kernel from crashing during heavy operations.

Disks Bus/Device: SATA. Set Async IO to Default (io_uring). Keep "Discard" and "IO Thread" unchecked. Moving from VirtIO SCSI to a standard SATA bus provides better stability.

What are others using?

/Benny

[ReetP]

Remember this is not a Koozali issue but the underlying OS eg Debian/Prox, and the core v11 ie Rocky 8/RHEL8.

We don't really mess with any of that stuff.

Almost all Koozali stuff sits above the core OS - hence you can install a base Rocky 8 first, and then add Koozali packages after.

Yup it sets a few defaults for most on install, but you can choose your own poisonif required.

Personally run various virtualised CPUs now they can emulate AVX so x86-64-v3 or v4, virtio scsi, default seabios.

I don't run anything intensive but have run these sort of settings for v11 for probably 8+ months with no issues, and previously on v9 & v10 on Prox for over a decade.

If you have problems then you should check, Proxmox foros, Rocky & RHEL for best advice.

They'll know more than us about specific issues eg ballooning which is a Prox thing, not Koozali.

We have told you multiple times that most of the experience with Prox hangs out on Rocket, not here.

You should ask there.

[Jean-Philippe Pialasse]

the most important: do NOT use balooning memory