Search results

Tried it and it works...

Read about a lot of changes in the installer...i'm back from vacation right now, will have a look at it this week ;)

But it might be easier to install PVE to a small unencrypted disk and then encrypt the storage where data and vms are being stored. I'll have a LUKS device for each disk, the unlocked device mapper devices then are forming a ZFS device, so it's ZFS on top of LUKS

https://github.com/zfsonlinux/zfs/wiki/Debian-Jessie-Root-on-ZFS On Stretch, you can skip the backports step...

vSphere with Docker leverages a minimal VM for each Container.

Also, Vendor lockin sucks...if you stick with VMware, it's only fun if you use the expensive vSphere Center, vSAN and so on.l

Compiled a slide some months ago for the same reason ;) (PVE only, as my people already knew VMware and i just want to show whats better *g*) https://speakerdeck.com/morph027/proxmox-ve Some things changed (Ceph is up to date now, ...) If you're interested, i can share the markdown files.

Do you have websockets and sticky sessions enabled in nginx config? Or probably use HAProxy: https://forum.proxmox.com/threads/pxve-nginx-websocket-proxy.20886/#post-139486

Thats true. Really weird issue anyway. I'm regularily putting decent load at my lap server and did not observe any crash like this. What are the last messages in journalctl -lf when the reboot occurs?

Also, if you're using E3-1230V2, which has TDP of 69 W (Microserver only can handle a TDP of 35W), the whole system might just get too hot and triggers a NMI. You can watch your ILO for info on sensors.

Also running multiple MariaDBs in LXC on ZFS without any problems here.

Sure ;) Any chance to get the kernel logs when this is happening? dmesg? journalctl?

Na, might be something different. I'm running 2 Microservers without any issues.

We do have a PowerEdge R730xd with Tesla card and Passthrough works (4.4 and latest Beta 5).

Jip, but i can live with that ;)