Search results

I am continuing to have tons of errors with backups. Despite my earlier report I can't say there's any improvement at this point. Below are two VMS that failed just today. It actually broke both centOS VMs, which jumped to huge CPU usage and required a stop and reboot. It's also often causing...

So, the update to the pve kernel to 5.11.22-3-pve seems as well as updates to proxmox-backup-server and proxmox-backup-client yesterday have improved things. I have been able to get through VM backups mostly without errors. However, on a server 2019, the following error is happening every time...

Same error occurring for me. I backed up and did fresh installs of all nodes to proxmox 7 last week. All nodes are fullly updated. This issue has been plaguing me ever since the upgrade. Some days worse than others. I have to redo the backups and even have had to restart nodes to get a backup...

FYI - the balloon driver works in the current non-subscription kernel 5.4.103-1-pve#1 There still is an occasional error that breaks this and requires a host reboot to correct it, but it is relatively stable now.

@bbarclay The server that I am running on the pvetest repository is still working with several windows VM and the balloon driver is working correctly. You could try runing talos on a machine updated to the test repository and see if the memory leak is still present. I'm sure others would find it...

So, I switched one server to the pvetest repository in order to see if this is being worked on. At first no change, but after the latest round of updates, I reinstalled the balloon driver in a Windows 2012 R2 VM and a Windows Server 2016 one and one hour on -- no memory leaks. It would appear...

I'll also add that ballooning works correctly with FREEBSD based pfsense right out of the box. The guests use only as much memory as they need and it reported correctly to the Proxmox host. Does anyone know what is going on with qemu that is causing this with the windows virtio clients? This...

Change your drive type to ide instead of scsi. You may have to do another reinstall. Once you have completed first boot install all virito drivers. You can add a second temporary viritio HDD to make sure that it is recognized and then shutdown. Change all drives and ethernet to Virito once the...

@ Proxmox Team Can you please give some response to at least that you have noticed this current bug with ballooing on windows guests? Even if there is no current path to a solution, better to know where we stand. For now, ensuring the windows guests do not have the balloon driver is the only...

Just to sumarize as I think earlier posts are confusing. 1. This issue affects both the windows VM and the proxmox host. However, the trouble is more noticed in the windows VM! Once the ballon driver is installed in the windows VM and the balloon service is started, a memory leak starts...

I am having the memory leak issue with Server 2012R2 and any virito baloon driver I try in Proxmox 6.3.3 If I intall the baloon driver - v 1.9.0 1.85 or as a test 1.71, this particular VM develops a memory leak and uses all of its memory within 1 hour and crashes. The VM is set as a...

Does anyone know how to create an additional zpool that is thin provisioned?

I just attempted the experiment on another Proxmox host to confirm. If I create a new zpool with the command: zpool create POOL_NAME mirror drive1 drive 2 The new pool uses up all 70GB for a lightly used disk on a CENTOS VM. In proxmox, I have selected thin provisioning and moved the disk to...

Greetings. Out of the box on Proxmox 5.x installs, the RPOOL volume is enabled with thin provisioning. Specific application: I use NFS volumes as export shares from the RPOOL. So, for example I share out /var/lib/vz which is part of the rpool. My nodes can then create VMS in that storage...

When will PVE-zsync-gui be introduced? I still don't see any sign of it in BETA2. Thank you!

Is it possible to join a machine running Proxmox 5 to an existing Proxmox 4.4 cluster? When will ZFS-SYNC Gui be in the beta?