OK das pve03-Log ist eindeutig. "Failed to receive the leave message. failed: 1 2" um 20:06:15 heißt: beide Hosts sind hart weggebrochen, kein sauberes Shutdown. Muss der Watchdog oder ein Panic gewesen sein.
Das "watchdog closed (disabled)" von...
Der fio-Test hat einen Haken: --sync=1 erzwingt synchrone Writes durch den ZIL, deshalb bringt auch iodepth=32 nix, der ZIL serialisiert das einfach. Deine VM hat aber cache=writeback in der Config, d.h. QEMU bestätigt Writes sofort ohne sync an...
OK, iptables ist sauber. Wenn curl hängt ohne Antwort, deutet das auf ein Routing- oder MTU-Problem hin.
Poste mal die Ausgabe aus dem CT:
ip a
ip r
curl -4 -v https://api.ipify.org 2>&1 | head -20
ping -c 3 -s 1400 -M do 192.168.1.1
Das curl -v...
Also auf 1 und 2 läuft die Version, die oben im Screenshot zu sehen ist (von der er beim Update kommt), auf allen dreien waren die gleichen Versionen und ich wollte erstmal den 3. aktualisieren.
Um 20:04 schreibt der Node 1, dass Node 3 durch...
Hello together,
it seems either to activate IO Thread or to change the controller to VirtIO SCSI Single has solved the freezing issue. The affected VMs are running now since five days without any issue. To find the exact solution reason I'll do...
if downtime isn't critical, if whole reading source isn't too long, the safest is
schedule shutdown guest, then backup offline, then start guest after Backup done using hook script
Hi,
weder wenn ich die IOdepth noch die Größe ändere kommen nennenswert andere Ergebnisse raus:
io --ioengine=libaio --direct=1 --sync=1 --rw=write --bs=4K --numjobs=1 --iodepth=32 --runtime=60 --time_based --name seq_read --file...
Reminder : during backup, I/O writes are sent to PBS before within guest itself, it's a "copy-before-write" méthode.
There is fleecing option to mitigate.
If it's the same thing, then...Please disable KSM (Kernel SamePage Merging).
You should be able to disable it in the virtual machine's memory settings.
https://pve.proxmox.com/wiki/Kernel_Samepage_Merging_(KSM)
In the meantime, I have understood that these log messages are a consequence of the firewall policy REJECT and MAC learning. To better diagnose my failed connections, I set bridge-disable-mac-learning 1. I also looked at the contents of the...
Thanks for the great work! Updating PDM suddenly insists on installing the proxmox-default-kernel (which fails in my unprivileged container). Is there a way to prevent that (like there is for PBS) when running it in a container?
EDIT: apt-mark...
update: it looks like in my case its caused by some corrupted VM because when I moved all important services to other node, the other node started crashing instead and the original one is running just fine now
now I need to find the VM causing it
You can switch to no-subscription repository, do apt update, install the desired kernel doing apt install proxmox-kernel-6.xx (input your kernel version here), then go back to enterprise repository and do apt update again. Make sure you only...
Jetzt bin ich mal dazu gekommen fio zu installieren und laufen zu lassen:
fio --ioengine=libaio --direct=1 --sync=1 --rw=write --bs=4K --numjobs=1 --iodepth=1 --runtime=60 --time_based --name seq_read --filename=/ZFS-NVMe/vm-201-disk-1 --size=8M...