Search results

I hate the entire 4.15.x line of kernels. They suck like a vacuum-cleaner.

Just tested 4.15.17-1 and it's even worse. Constant reboots needed for VPN/LXC container.

Any news?

Remember this from 7 years ago... https://forum.proxmox.com/threads/future-of-virtualization.5756/page-2 I just had to regale my prophetic abilities here and say... I told you so :) Sam

I'm trying to get pfSense to provide IPv6 address to LXC containers using DHCP but for some reason I can't get it to work. Do I need to assign the host also with IPv6 address?

I just tested nested virtualization and migrated a whole KVM that had 10 (network attached) LXC containers in a few seconds. So I couldn't migrate LXC well but I could migrate KVM with many LXC well. It's an odd world...

Ok. It's not a picture but still... take a look how long it took to migrate LXC container (that is on a NAS so there is nothing to actually migrate). 2018-04-23 15:53:24 shutdown CT 144 2018-04-23 15:54:06 starting migration of CT 144 to node 'vh3' (10.168.100.103) 2018-04-23 15:54:07 volume...

This may relate to interesting feature on /etc/hosts file. If there is a "manually" inserted host called "server.com" before the automatic line like this: 10.11.12.13 server.com # --- BEGIN PVE --- 10.11.12.14 s1.server.com ... then Proxmox tries to add also s1 before the first "server.com"...

NFS (fstab) mount failure on LXC client start-up can enter the client in a "paused" unresponsive state. Only way to "un-pause" it is to reset the client.

I have been testing NFS mounts on LXC containers and they work mostly ok after you have modified App-Armour settings on the host. Problems arise when the LXC containers are moved or host-node restarts. LXC container does not always seem to honor the /etc/fstab settings which results in mounts...