This looks related to CPU freeze issue that many of us are experiencing when backing up or restoring VMs, that is unresolved for many years:
Here is my newly reopened bugreport...
Good point @mmenaz ! Unfortunately none of the new features solved this problem completely, also his observation about this being a load issue is superficial in light of the facts.
I have reopened the bugreport and commented our latest experience. I encourage everyone to do the same.
Read my previous posts... this is a several years old bug in the kernel scheduler or KVM (or both), and nobody cares about solving it. Proxmox devs killed my bugreport, KVM devs do not even acknowledge the bugreport.
What happens is that during heavy IO load on the host (disk or network), KVM...
This looks exactly like the problem that I (and many others) reported for years in this thread and others. The problem is most likely a Linux kernel / KVM issue.
What seems to happen is when local disks are busy due to a restore operation, probably the dirty page IO of the host system is...
I have tried to install Ubuntu 18.04 LTS Server in a KVM machine on a recently updated Proxmox 5.4 host, but after entering the IPv4 address manually, and hitting "Save" the installer instantly restarts. Tried different hardware configurations (E1000 vs. VirtIO-net, disconnecting the adapter...
When creating a regular (RBD) Ceph pool, there are options in both the GUI and in pveceph to determine the size (replication count) and the min. size (online replicas for read) of the pool. However, when creating a CephFS pool, neither the GUI, not pveceph provides an option to create one with a...
Let's say my username is "pveuser@pve". If I query ACCESS/USERS, I get all the user data I'm allowed to see, among it my own, but ACCESS/USERS/PVEUSER@PVE gives a 403 Forbidden error.
Problem is I can't GET (or POST) ACCESS/USERS/PVEUSER@PVE to read (or write) my own data, unless I have the...
Hi Morbious, can you please post some more info?
- host HW configuration (CPU and memory type and amount, how many NVMe disks)
- host SW configuration (kernel versions on both machines, storage type and filesystem used), how many VMs
- VM configs of the VMs you get errors on (cpu number, memory...
Unfortunately the Proxmox developers @tom @fabian @dcsapak never acknowledged this as a problem or bug on it's own, rather they try to blame hardware or software configuration, and they even killed the bugreport I filed that started to accumulate many user reports...
It looks like the problem got solved after I restarted all the Proxmox services:
service corosync restart
After another apt-get update, apt-get dist-upgrade works again...
I have found this thread with a similar problem:
However the command @fabian suggested does not show any packages held:
# apt-mark showhold
Anybody seen this?
I am upgrading our cluster, node by node from PVE 4.4 to 5 following the wiki:
Several nodes upgraded perfectly, however on one node I get the following errors:
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree...
Yes, this problem is still massively affecting many Proxmox users, unfortunately no one has any idea what could be causing it. Actually the Proxmox developers didn't even acknowledge so far that this bug exists (my bugreport is still in NEW status), so I wouldn't hold my breath that this gets...