Search results

Run "qm list" & post its results?

Have you disabled hardware checksum offload on the VM?

Yes, if there are snapshots on one side, but not the other, it won't work. Remove the snapshots on the source side, then it will work to the remote side. There might be a better way, but not one as simple.

Does it exist both on the original and the destination servers?

@wolfgang - Turning off write-back did make a significant difference. Thank you.

If you go into the hardware settings for the virtual machine and edit the settings for the hard disk, you can choose a caching method.

Thanks @wolfgang. Yes, I do use write-back - I'd seen a few recommendations for it. I'll turn it off on the next reboot cycle, and also hard code the ARC size.

I wouldn't do RAID-Z, I'd set up mirrored vdevs, and stripe them.

Thanks Wolfgang. As part of troubleshooting, I have zfs_arc_max currently set as either 25% or 50% of the system memory. zfs_arc_min is dynamic. The systems have plenty of free memory. This is the same behavior that drove me to upgrade from consumer SSDs to enterprise ones. Things improved a...

Thanks @wolfgang 1) 128GB RAM - 32 allocated for ARC, 64 for virtual machines, 32 left free 2) Swapping is kept to a minimum on both host and vm's. Swappiness of 1 set. I did just turn off swap on the Proxmox hosts as I saw recommended elsewhere as it was the default rpool/SWAP, but haven't...

Any suggestions @tom @wolfgang @fabian ? Thanks.

The write endurance is pretty weak.

Help! :) I have four servers with 3x drive bays and have them populated with either 2x Samsung SM863 or 2x Intel S3610. The drives are set up as a ZFS mirrored vdev with both ROOT and data being on the pair. One bay is open on each server. Normally I/O load on each server is low - iowait is...

Also make sure you're not allocating the 'missing' 4GB to onboard graphics in your BIOS Settings.

Try: "echo 1 > /proc/sys/vm/drop_caches" to do a relatively safe and quick cache flush. You'll be able to start the VM after that. Proxmox is a touch dumb about not starting a VM when OS memory caches are full, but there's plenty of memory.

There are two of you? *Flailing Muppet Arms* :)

So long as the MB supports it, ECC works fine on Ryzen/Threadripper. See: https://www.reddit.com/r/Amd/comments/6f7s28/what_is_the_state_of_ryzen_and_ecc/ I just wish there was a Threadripper MB with IPMI. I don't need the PCI-E lanes of Epyc, just raw CPU power.

Do you have PTI enabled? Turn it off and see if that fixes it. We took a 30% hit when we enabled Spectre/Meltdown mitigation. Same symptoms you're seeing.

If you're using ZFS, you could just snapshot the root and send it elsewhere for backups.

If you're using ZFS, you can use pve-zsync. It's working well for me along with having iothreads enabled. https://pve.proxmox.com/wiki/PVE-zsync