![]() ![]() I have opened a bug in the Proxmox bugzilla, but it was closed by as a "load issue" while is clearly a bug in the kernel or QEMU/KVM code: (Also people fail to read the starter post of this thread, therefore the discussion gets quickly derailed) Unfortunately, neither the Proxmox nor the KVM developers acknowledge the issue, let alone own (and investigate) it, so no one works on a solution. Regardless of several times higher system IO capacity, websites hosted on KVM guests on this node timed out for minutes. ![]() The issue even appeared to me a few days ago on a fuilly updated Proxmox 5 node when restoring a VM from Ceph to local-zfs, even though I set a restore limit of 100 MB/s on a 4 disk RAIDZ1 SATA SSD pool. The problem happens (at least) since Proxmox 3, and affects many hardware and software configurations and filesystems (ext4 on LVM, ZFS, etc.). Unfortunately putting the swap partition to a different SSD than the array being restored to does not solve the problem. 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 blocked, leading to CPU hangs / lockups in KVM guests which sometimes result in guest kernel panics. The problem is most likely a Linux kernel / KVM issue. This looks exactly like the problem that I (and many others) reported for years in this thread and others. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |