Mein Use-case war, eine VM zu haben, auf welcher ich dann über das browserfenster von Proxmox (also die Konsole) als beispiel steam öffnen und dort spiele starten und spielen kann.
Habe schon gelesen das es, sobald ich die iGPU durchreiche und...
Hi everyone,
I wanted to share a significant performance bottleneck I identified and resolved during the Garbage Collection Phase 2 process on a PBS setup using an XFS(NVMe drive r_await = 0.09, w_await = 0.02 when i traced processes)...
The way COW works, the 2:2 parity data is still on the zpool after you 'move it out', and still being used to calculate the total space of the pool. You need to actually replace that data with 2:4 parity data so it calculates with that. 1.35TB...
I changed shared flags, no I don't have shared local storage across all hosts. They're all independent. I did perform disk checks on all hosts. Journalctl shows nothing when these errors occur. Virtualbox VMs work flawlessly with all test images...
Here's the output:
root@pbs1:~# gdb --batch --ex 't a a bt' -p $(pidof proxmox-backup-proxy) > proxy.backtrace
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file...
Ok, thank you. System (boot) partition is ext4 and I would like to keep it that way. First I need upgrade to final version of 7 - I hope that issue would not be the case here already! Because I'm more affraid about NIC name changes (all NIC's are...
The boot manager is that part of the system which takes care to take over control over the hardware after the BIOS is finished with the initial startup. It launches the Linux kernel and afterwards the rest of ProxmoxVEs operating system. Since...
Can you please post the full /etc/network/interfaces within blocks? (or use the code format buttons of the editor. If you use the SDN, please also add the /etc/network/interfaces.d/sdn file too.
The way COW works, the 2:2 parity data is still on the zpool after you 'move it out', and still being used to calculate the total space of the pool. You need to actually replace that data with 2:4 parity data so it calculates with that. 1.35TB...
There is nothing in the systemd journal.
I just created a local datastore for testing and backups to this local datastore finish successfully:
INFO: starting new backup job: vzdump 500 --notification-mode notification-system --notes-template...
Hello again.
After some digging, it looks like the network issue is a side effect of not being able to mount /run. From the node's journal:
kernel: audit: type=1400 audit(1779270973.875:168): apparmor="DENIED" operation="mount" class="mount"...
But RAID5/6 probably does not give good performance (in terms of IOPS, which you need for multiple VMs trying to use the drives at the same time). I though I mentioned that in my post.
i did try to reproduce but couldn't, more information about your setup (ct/ceph config etc.) would be useful.
does this persist after you reboot your nodes?
Hi,
When backups are made to PBS I have the following warnings:
INFO: attaching TPM drive to QEMU for backup
WARN: unable to check guest fs freeze status - Agent error: Command guest-fsfreeze-status has been disabled: the command is not allowed...