Search results
-
S
[SOLVED] PVE-Container segfault
Latest update to PVE broke my containers. I had installed a simplified Debian containers from LinuxContainer.org (for example: https://us.images.linuxcontainers.org/images/debian/buster/amd64/default/20191119_05:24/rootfs.tar.xz) and have a "bind mount" to ZFS directory in lxc configuration...- sigo
- Thread
- Replies: 15
- Forum: Proxmox VE: Installation and configuration
-
S
[SOLVED] Latest systemd/udev breaks network device naming!!
After updating to latest systemd* packages: libsystemd0:amd64 (232-25+deb9u9, 232-25+deb9u11), udev:amd64 (232-25+deb9u9, 232-25+deb9u11), libudev1:amd64 (232-25+deb9u9, 232-25+deb9u11), systemd-sysv:amd64 (232-25+deb9u9, 232-25+deb9u11), libpam-systemd:amd64 (232-25+deb9u9, 232-25+deb9u11)...- sigo
- Thread
- boot failed network interface systemd udev
- Replies: 10
- Forum: Proxmox VE: Installation and configuration
-
S
Mistake in DHCP option (firewall) by default
I have been create a LXC container with enabled 'firewall' (attached image) and all other options by default(!). My VM.fw next: root@pve:~# cat /etc/pve/firewall/120.fw [OPTIONS] enable: 1 Now, i am checking firewall rules for interfaces in this VM: exists veth120i0-IN...- sigo
- Thread
- Replies: 1
- Forum: Proxmox VE: Networking and Firewall