Search results

Try to set the vm.min_free_kbytes , so there is always memory free for proxmox. I set that in every proxmox server and as I said, I don't have problems with crash or reboots. In your examples I think your ZFS ARC max is too much, Linux has his own cache too and even if that is released when...

I use Proxmox on consumer hardware (spinning disks, desktop motherboards, non-ECC RAM) always with ZFS and for a very limited number of VMs it has an OK speed. The best improvement I just started to do is move from spinning disks to SSD. Usually I use two consumer grade SSD (Samsung EVO serie)...

I think the message is self explanatory. There were some device of the pool that could not be found. Usually, if the disks are healthy, you could try with rootdelay=10 in grub config

Just use Veeam Agent installed in clients

You are missing the no-subscrition repository, read here: https://pve.proxmox.com/wiki/Package_Repositories#_proxmox_ve_no_subscription_repository

If you don't have a subscription, you should add the no-subscription repository

From the web interface, in the Hardware tab of the VM, you have the option to DETACH a virtual disk. After you click on detach, the disk is kept as unused, just double click the unused disk and add it as virtio-scsi with discard enabled

First you should install virtio-scsi drivers, adding a new virtio-scsi virtual disk and installing the driver. After that you can remove all the virtual disks and re-add them as virtio-scsi with the discard option enabled. From Windows 7 / Windows server 2008R1 up to Windows 10/Windows Server...

Windows or Linux VM ?

You should use virtio-scsi driver with discard option and inside the VM use the TRIM function (fstrim from linux, during the maintenance time in windows)

Are you sure you have the correct package repositories? https://pve.proxmox.com/wiki/Package_Repositories

I usually use this steps: - install Windows Server with SATA or IDE disk - after the installation is complete, create a second virtual disk with scsi - start the Windows VM - install virtio drivers for all the unknown devices - from disk management, initialize and format the new disk - power off...

Have you tried, as @Alwin said and like this http://tracker.ceph.com/issues/22464#note-48 , to lower the bluestore cache size ?

Check this bug in ceph tracker http://tracker.ceph.com/issues/22464 could be your (and mine) issue?

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Physical_.28running.29_Windows_server_to_Proxmox_VE_.28KVM.29_using_VMware_Converter Those steps are a bit outdated, when you have the vmdk file, you can import in a new VM in proxmox with qm importdisk After that, you should...

Install the latest windows qemu agent From Windows Powershell, what's the output of Get-Service balloonservice

Having mixed servers with Proxmox and VMWare, I can say that VMWare + Veeam Backup&Replication is the best backup solution that I can think of. Incremental backups of VMs from which I can recover the full VM, only some virtual disks or even only some files from the guest OS. I can replicate...

Neve use apt upgrade with proxmox, always apt dist-upgrade

I had the same problem https://forum.proxmox.com/threads/after-update-5-1-43-pvedaemon-and-pvestatd-reports-rados_connect-failed-operation-not-supported.43409/ Solved just as you said Thank you very much

Thank you very much for the link, I had the same exact problem of the linked thread and in the 4th post I found the solution Cephx is disabled so I removed the files in /etc/pve/priv/ceph , restarted pvestatd and pvedaemon and everything is back healthy Problems solved!