This might actually be unrelated, the timestamp in the VM is 20:03 EST, this server had a running backup and the backup had failed due to a hardware problem with the backup server at around the same time. This behaviour isn't really ideal :p (no iothread, VirtIO SCSI controller)
INFO: 69%...
I'm not seeing anything interesting in the host, I should have grabbed logs from the guest but in an attempt to minimize downtime I didn't think of that. However, I did briefly go through the error messages on the VM console, and they were along the lines of sd hung task I believe. Perhaps this...
This is actually not from the large single VMs where the issue was rampant, this is from another hypervisor where I didn't notice issues before. iothread isn't enabled as well, and controller is VirtIO SCSI.
Interesting, thank you, I know this problem occurs on other applications when things get busy as the defaults are low, never really even thought that this would have been a problem on Proxmox. Maybe Proxmox should ship with higher defaults in future, such as 1048576?
Thank you very much for your reply. Unfortunately in most cases the guest console got spammed with systemd messages stating the disk was readonly. I was able to grab the error right after in one or two instances, I don't have a screenshot but it was something like this:
validate_block_bitmap...
I have been observing VM disks going readonly randomly (every 5-7 days, it's not a regular pattern). This appears to only be happening to VMs with very large disks, such as 4TB or more. I have a fairly large deployment with over 50 hypervisors.
The VMs have a local RAID 1/RAID 10 disk, I have...
My storage is regular raw files on a EXT4 partition. I'm primarily curious if disk writes are hijacked to write to both the backup and the actual disk, as limited bandwidth seems to aggravate this.
When trying to backup a large VM to a remote server using vzdump (snapshot mode), the writes on the VM appear to be slowed down greatly. Are disk writes affected (maybe writes are slowed down during a backup) when a backup is in progress, to maintain consistency?
I upgraded one of my test nodes to try out PVE 7, and I noticed that one VM was not starting. The error was
TASK ERROR: start failed: org.freedesktop.DBus.Error.InvalidArgs: Value specified in CPUWeight is out of range
It seems that this is due to cgroups v2, where the max limit of this is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.