Recent content by are

It requires specific alignment values like described in comment 19 (https://bugzilla.proxmox.com/show_bug.cgi?id=3446#c19) and in rest of this bug report. Other values will fail to start.

Don't rely on that "must be aligned to 2048 for hotplugging" - that message just lies and doesn't reflect what is being checked in the code. There is a patch that calculates closes possible values and presents these in a error message (for some older proxmox version but should be easy do...

This time it seems to be a package that's required but missing on the proxmox "ftp"/web server:

# apt-get clean; apt-get update; apt -o Debug::pkgProblemResolver=yes install --reinstall pve-manager Hit:1 http://security.debian.org/debian-security bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease...

Not possible since domains are in registry not supporting API. So you can't renew automatically (with DNS validation) and fetch cert/key into proxmox. Allowing 80/443 on firewall for time of renewal validation would be good option and would solve the problem.

I assume that you also tested if it gets correctly applied (via cat /sys/module/vhost/parameters/max_mem_regions) and if values like 512 work...

Did you set max_mem_regions as described earlier?

Third post in this thread had *working solution* (for me): https://forum.proxmox.com/threads/problem-with-hotplug-and-64gb-ram.73621/#post-329329 and later it was repeated https://forum.proxmox.com/threads/problem-with-hotplug-and-64gb-ram.73621/page-2#post-544025 so # cat...

Here dist-upgrade worked after apt-get install pve-kernel-6.2 (with bookworm in paths and no ceph).

I have another machine (different Xeon cpu, different vendor etc) where I put 7.1 and the issue also shows up there. My method of reproduction is to start building kernel. i/o hangs quite fast with that, in 1-2min of building. That's it. With default "io_uring" hangs, with "threads" I'm...

Updated one machine to 7.1 and on host kernel 5.13.19-1-pve VMs (linux based) are working for few minutes and then end up stuck on disk access. restarting VM and after few minutes problem is back. restarting host - the same. Back to 5.11.22-7-pve and problem is gone. Note that when running 5.13...

I'm looking at why corosync isn't automatically restarted on a failure (like when OOM kills corosync). The options (Restart and RestartSec) are commented out and mention "corosync with enabled watchdog service". Well, these options are actually unrelated to watchdog and IMO would be good if...

@marius: did you find a reason why watchdog-mux failed to update watchdog in 10s? I'm seeing ipmi_watchdog not getting ping from watchdog-mux on single hardware setup and thus ugly reset happens. watchdog-mux doesn't use mlock() (while regular watchdog does that...