Search results

I also found this explination;

@KoenDG I was looking into this today also. The Cluster I manage has been upgraded over the years from V3.. to the current V8. The quote you have referenced is from this page; https://pve.proxmox.com/wiki/Separate_Cluster_Network#bindnetaddr or https://linux.die.net/man/5/corosync.conf However...

Hi Achim, I assume that you have proceeded since your post 2 weeks ago. Here is some gerneral Advice; ZFS is recommended with ECC RAM and typically requires 1GB RAM per 1TB Storage. You have a Xeon so that is a possibility but not a Given. VM's on ProxMox work best when there is High...

Still looking good. Slower growth than before occuring (15.83GB --> 16.59GB over ~ 12 days)

From the Change log: qemu-server (6.2-19) pve; urgency=medium * fix #3113: unbreak drive hotplug * qmeventd: add handling for -no-shutdown QEMU instances, to avoid errors if the guest OS shuts down the VM during a backup job. -- Proxmox Support Team <support@proxmox.com> Thu, 05 Nov...

5 days on, so far so good.

Hi, Thanks for trying to help but this is not related to the guest machine and worked previously. The Guest Machine needs to shut down and stopped to be able to attached the HotPlug disk. This occurs on a New Disk, hence no file system.

I get this error propted when I try to attach a hard drive to a VM. This may have also occured on Proxmox 6.2-14 400 Parameter verification failed. virtio0: hotplug problem - Can't use string ("x86_64") as a HASH ref while "strict refs" in use at /usr/share/perl5/PVE/QemuServer/PCI.pm line...

Update to nfs-common, I'm upgrading to Proxmox 6.2-14 (from 6.2-6) to test if this resolves the issue. nfs-utils (1:1.3.4-2.5+deb10u1) buster; urgency=medium * statd: take user-id from /var/lib/nfs/sm (CVE-2019-3689) (Closes: #940848) * Don't make /var/lib/nfs owned by statd. Only sm...

I wonder if this could be a solution to this issue? NFS over RDMA RoCE

A simple BASH script helps to indicate wich KVM sessions are using more RAM; for OUTPUT in $(pgrep kvm); do ps p $OUTPUT --no-headers o pid,rss,sz,command; done 13212 2158180 719145 /usr/bin/kvm -id 910 -name ... 13225 0 0 [kvm-nx-lpage-re] 13269 0 0 [kvm-pit/13212] 15564...

PVENode 2: (7 Guest vm, configured with 6 x 2GB RAM, 1x 512MB) Tasks: 257 total, 1 running, 256 sleeping, 0 stopped, 0 zombie %Cpu(s): 30.7 us, 9.5 sy, 0.0 ni, 55.0 id, 0.0 wa, 0.0 hi, 4.8 si, 0.0 st MiB Mem : 28120.2 total, 1881.9 free, 25401.3 used, 837.0 buff/cache MiB...

Hi All, I would like to find a solution to the slow memory Leak / Growth problem I have with some PVE Nodes I manage. I have PVE 6.2-6 installed (Issue occured with previous versions also). Almost all nodes are using the same QNAP Storage pool for VMs via NFS V4 protocol. Almost all Guest...

I'm on ProxMox 6.2-6 now and my problem with migrations has gone away. I'm not sure why I had a Bandwidth limit on Migrations but I removed it around the same time as the upgrade, not sure if that helped.

I've noticed a simlar problem with the cluster I look after. I see a slow unexplainable memory growth 10GB to 50GB above VM allocation over 2 to 4 weeks which disapears by migrating the VM between hosts. I'm also using NFS for the storage but using RAW format, however most of my Guest machines...

I've Been experiencing this issue also. Virtual Environment 6.1-7 I dropped HA configuration and changed the NAS Mapping from NFS to CIFS because of the NFS memory ballooning. Migration appears to work okay now. However it worked fine when we first configured the cluster with V6 and used NFS.

Thankyou for the suggestion, I have created a Bug. Yes I meant a different Node in the cluster with a different time zone. (I'll update the original post)

Now reading the documentaion more carefully and not knowing where to change it, I had the default "Conditional " policy. What I can't see in the documentation is how to change this policy. I've now found in ProxMox under Datacenter--> Options --> HA Settings This lead me to find more...

You have indicated; However this documentaiton and My testing has proved it will not migrate on reboot. https://pve.proxmox.com/pve-docs/chapter-ha-manager.html#ha_manager_shutdown_policy

SamirD The reason to run as a cluster is to have a single user interface for all the ProxMox machines. The ability to migrate machines between nodes should it be needed. (i.e. keep a guest machine up while you restart a host machine) The ability to Manually load / performance balance guests...