Search results

Do you think that due to the presence of Percona on the VM - a sign of a large number of unremovable small memory blocks ?

Do you have any ideas about a whole lot of unremovable small blocks ?

RAM usage(node stat) 41.04% (103.22 GiB of 251.49 GiB) :)

While testing, I came across a situation - I can’t add more memory to VM “P” than 47 GB. I add 65536, but it cuts to 47 GB and gives an error: Parameter verification failed. (400) memory: hotplug problem - VM 127 qmp command 'device_add' failed - a used vhost backend has no free memory slots...

Let me show you the differences. For example, a VM with the Percona will be VM “P”, and a VM without the Percona will be VM “W” P: CPU - 8 RAM - 32 SCSI Controller - VirtIO SCSI HARD DISK(virtio0) - vmdata:vm-101.... HARD DISK(virtio1) - vmdata:vm-101.... HARD DISK(virtio2) - vmdata:vm-101...

The issue is that I cannot reproduce the problem on a similar VM in a test environment. The error occurred on those production cluster VMs on which the hotplug was enabled. But it is not reproduced on a single VM in a test environment with the hotplug enabled and in another production cluster...

You can see an example lsmem above. Is this what you are talking about?

Could this be related? On this VM lsmem gives me this list: # lsmem RANGE SIZE STATE REMOVABLE BLOCK 0x0000000000000000-0x0000000007ffffff 128M online no 0 0x0000000008000000-0x000000000fffffff 128M online yes 1...

Yes, I thought about the same thing, but how can I overcome this? Just when it's enabled. As soon as I disable the hotplug ops, percona works without errors

Hello! I'm facing hot-unplug issue in Debian VM Operating System: Debian GNU/Linux 10 (buster) Kernel: Linux 4.19.0-25-cloud-amd64 Which is on Proxmox proxmox-ve: 7.3-1 (running kernel: 5.15.107-2-pve) pve-manager: 7.4-17 (running version: 7.4-17/513c62be) In the "Options" of the VM in...

Thanks a lot ! you are my savior. I did everything you advised and the node really returned to the cluster. Now everything is working normally!

Please help me understand how this can happen and why. How to return the Proxmox node to its original state?! The Proxmox node has a hostname for example "node7" and is in the cluster for 7 nodes. Has zfs-RAID10. 2 virtual machines (vm3 and vm4) installed with the help of terraform worked on...