Search results

bug in "pve-container_3.2-3", after downgraded to "pve-container_3.2-2", backup working again!

see PVE version above...

Hi folks, i got following error (unable to parse volume ID) after pve update: Task Log: INFO: starting new backup job: vzdump 100 --remove 0 --storage backups --compress zstd --node pve --mode snapshot INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp11973_100 for temporary...

you said: "I see will be fixed in the next release thanks for sharing" and i'm just tested! ;)

configs are already there: https://forum.proxmox.com/threads/new-mobile-app-for-proxmox-ve.76327/post-340604

same error in version 1.0.2...

see on attached screenshots...

yes, installed from google play, version 1.0.1

another deserializing error LXC config file examples (new feature request: copy text from error message ;)):

It is Hard Disk not SSD (2x2Disk (4k))!

Hi, can you please explain why 16k and while not 8k?

4k NTFS ZVOL on RAID10 2x2Disk (4k), witch volblocksize: 8k or 16k option is better?

bei mir immer in Top 2 Verbraucher sind: pvedaemon und pve-firewall Wie sieht es bei Euch aus? (echo "COMM PID SWAP"; for file in /proc/*/status ; do awk '/^Pid|VmSwap|Name/{printf $2 " " $3}END{ print ""}' $file; done | grep kB | grep -wv "0 kB" | sort -k 3 -n -r) | column -t COMM...

on pfSense 2.2 and later the VirtIO Driver Support enabled by default: "The following instructions are not necessary on pfSense 2.2 and later, which have the proper drivers built into the kernel."

same situation with pfSense 2.4.3 (FreeBSD 11.1-RELEASE-p7):

Hallo zusammen, ich habe Ballooning probleme bei eine migrierte Windows 2012R2 (Hyper-V zu Proxmox VE): ich habe folgendes gemacht: alle verstekte und inaktive Geräte aus Geräte Manager entfernt https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Hidden_nonpresent_devices...