I did a ZFS install of 5.1 a couple weeks ago and the I/O has been abysmal. I assume it was something related to ZFS because I have other systems with similar hardware running 4.4 with ext4 and it performs fine. I plan to re-do this 5.1 system as ext4 and see how it goes.
Is there a writeup on performance best practices when using ZFS instead of ext4. I seem to remember someone saying to use writeback instead of Default (no cache) for the VM disks but now I can't find it.
https://pve.proxmox.com/wiki/Performance_Tweaks does a good job explaining the options and...
The only way I've found to get Proxmox on ZFS @ OVH is to use their KVM/IP (IPMI) and mount the ISO over the WAN.
It's quite painful doing it over the WAN since my upload is only 6Mbps and I'm about 30ms (round trip) away from BHS.
Supposedly you can upload the ISO to them somewhere and mount...
If you have LXC on ext4 then it will not be able to do snapshot and will use suspend instead. That is just a known limitation. You can use ZFS instead for LXC if you need it to do snapshots.
More information here: https://pve.proxmox.com/wiki/Backup_and_Restore
snapshot (LXC): Use storage...
For what its worth I'm having a similar issue with LXC backups. The actual backup portion of the job seems to always complete, but when its supposed to start the container back up it is only successful about 75% of the time. I can then immediately power the container on myself and it starts...
Not to hijack the thread but I have a question about the "stop" method for LXC backups. I don't mind the brief downtime so I was thinking of going this route but the "stop" concerns me. Is it really a "stop" AKA pull the power cord out? Or is it more like "shutdown" AKA graceful?
There was a new update to pve-firewall that I just installed tonight... (2.0-16)
I'm not sure whether the newer version fixed something or simply the update process caused the service to be restarted, but either way it is working now.
Are you running KVM VMs or LXC Containers?
I'm having the same trouble (not blocking anything) with LXC Containers. https://forum.proxmox.com/threads/proxmox-ve-firewall-help-on-ovh.25880/
I do have the enable checked at the VM/container level but no dice.
I've got a new Proxmox VE Instance running on OVH.
I have the firewall enabled at the datacenter level and the rules that I write at that level are applying to the hypervisor correctly as I'd expect.
I don't seem to be able to get the firewall rules to apply to the LXC VMs at the moment. It...
It's not so much the GUI operation of pve-zsync.
I guess I misunderstood the point of pve-zsync. I assumed that it would replicate the VMs to a cold standby site so that they could be powered on when needed.
It looks like all this does is copy the ZFS datasets to wherever you want, and there's...
About the same thing happened. The sender said it sent the files to the receiver.
I can see that the files are present on the receiver:
root@proxmox-test1:~# zfs list -r rpool
NAME USED AVAIL REFER MOUNTPOINT
rpool 6.75G 233G...
The directions in the wiki make it sound like this is pretty straight forward, however I don't seem to be able to make it work.
Source - Before:
root@hv2:~# zfs list -r rpool
NAME USED AVAIL REFER MOUNTPOINT
rpool 51.1G 174G 96K /rpool
For what it's worth the backup process seems unable to delete the snapshot as well:
INFO: Starting Backup of VM 224 (lxc)
INFO: status = running
INFO: found old vzdump snapshot (force removal)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot snapshot
It works to create a new one, but not to remove the troublesome one.
root@hv2:/mnt/pve/nfs-backups/dump# pct delsnapshot 224 vzdump
root@hv2:/mnt/pve/nfs-backups/dump# pct listsnapshot 224
vzdump no-parent vzdump backup snapshot
I think that got me a little further, but no joy on a new snapshot yet.
root@hv2:/mnt/pve/nfs-backups/dump# pct unlock 224
root@hv2:/mnt/pve/nfs-backups/dump# lxc-snapshot -L --name 224
root@hv2:/mnt/pve/nfs-backups/dump# lxc-snapshot --name 224
Unable to take new snapshots/backups because there seems to be a snapshot in progress.
I've rebooted to the hypervisor, no change.
The snapshots tab shows a 'vzdump' snapshot with a status of 'prepare'
root@hv2:~# lxc-snapshot -L --name 224No snapshots
root@hv2:~# lxc-snapshot --name...