Search results
-
T
Permission Problem Stretch
Same here -- this seems to be systemd-related. Is your Container unprivileged ?- tahala
- Post #2
- Forum: Proxmox VE: Installation and configuration
-
T
Wired network behavior (packet loss/timeout)
Update: I just changed the network configuration to only one IP address since networking in VM/CT is working nevertheless (they get IP addresses) I will monitor if this setup is more stable in relation to the original behavior.- tahala
- Post #4
- Forum: Proxmox VE: Networking and Firewall
-
T
[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or la
Das Problem hatte ich auch. Kernel: 4.13.4-1-pve #1 SMP PVE 4.13.4-26 (Mon, 6 Nov 2017 11:23:55 +0100) x86_64 GNU/Linux Lösung verschafft die Installation des Debian Packages 'intel-microcode' auf dem 'non-free' Repository. Der microcode ist halt properitär. Dann taucht folgendes im Log auf...- tahala
- Post #4
- Forum: Proxmox VE (Deutsch/German)
-
T
Wired network behavior (packet loss/timeout)
Thanks for reviewing the config. I have already tried different network options, including giving the ip address directly to a single network card as im used to to it under linux. ip a now shows: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000...- tahala
- Post #3
- Forum: Proxmox VE: Networking and Firewall
-
T
Wired network behavior (packet loss/timeout)
Dear Proxmox Community, I just migrated my homelab from esxi6 to proxmox5. Unfortunately I have got some issues with the network already on the Host itself. Currently I have two Network Cards attached and the an adapted setup from the wiki. auto lo iface lo inet loopback auto enp0s25 inet...- tahala
- Thread
- Replies: 3
- Forum: Proxmox VE: Networking and Firewall