Search results

Hi I have see on my "zpool01" in Summary Tab this space usage: if i check on "VM Disks" The total summary is 468,67 GB, so I don't get back the space occupied in the "summary" tab. Thanks :)

I use the latest version of VirtIO, anyway i uninstall from control panel and reinstall the qemu agent but still the problema as you can see:

Here:

Yes i already enable like this: I poweroff and poweron few times but nothing changed.

No i can't see the IP Address in the Overview tab

I have a Windows 10 VM, customer call me that can't able to connect with RDP, i check in PVE WebUI and the VM is running but the console have a black screen and if i type spacebar for example nothing happened. We have some log file for understand why the VM not Responding? Thanks.

Any news?

Hi @fiona I've already shutdown and start again the vm and reinstall the agent but it's still saying "Qemu guest agent not running", this is the state on Windows Services i attached the screenshot

Hi Everyone i have install qemu guest agent and in the windows services is up and running, but in GUI of Proxmox says "Qemu guest agent not running" i try to disable and renable the Qemu agent from the option of the VM but nothing changed.

i create directly on "rpool", thanks

is better create a dataset? or i leave in /mnt/backup

I want to set zfs quotas for my datastore to avoid problem when it's full, this is my proxmox backup server installation: I add a datastore in this path: This is the output of zfs list -t all: In my case i need for set quota i need to do this command right? zfs set quota=712G rpool (80%)

Hi just fixed in the answer below

Any update?

Hi all I have bought this ups Zinto 1500 from this website: https://www.online-ups.it/, they have this software at: https://www.generex.de/support/downloads/software,from the manual it seems that on proxmox you should use RCCMD and not UPSMAN. Or just use NUT? Thanks

Hi But i don't understand what can i do for it?

Hi everyone I notice in the monitor connected to my proxmox server this line of errors: [1721985.459782] x86/split lock detection: #AC: CPU 0/KVM/40131 took a split_lock trap at address: 0xfffff804526c45e3 [1724969.917710] x86/split lock detection: #AC: CPU 5/KVM/40136 took a split_lock trap at...

Ok Thx for the answer :)

Yes i saw that the last one not have any errors, but if the number of errors not increase the hard drive are good in your opinion, the long test smart is reliable for determine if the drive are good or not? This is a secondary server non the primary is only for emergency if the primary has...