Hi
I'm new to Proxmox having used ESXi Standalone Hypervisors in my home lab for the past 10 years.
Loving the experience except for one issue I'm having with my PC's losing their AMT connections once Proxmox has been shutdown - making it impossible to restart them again remotely.
I have 4 Hosts and all have the same issue, once the host has shutdown AMT goes offline and the host requires a physical button press to restart.
Hosts all have AMT static coded to a 192.168.200.x IP address and use VLAN200 native port on the UniFi switches
Management GUI traffic is via a 192.168.140.x IP address using VLAN140
VM Traffic is split across VLAN110 & VLAN140 depending on the VM purpose.
3 of the hosts are Micro PC's and therefore only have one network port for all this traffic. ESXi was able to handle this without issue.
The 4th has a dedicated network port for AMT traffic, a dedicated network port for Management traffic and a further port for all VM traffic.
Devices are
Lenovo TS140 - AMT is via Intel I217-LM, Machine Management and VM Network interfaces are on separate Intel card.
Dell Optiplex 7050 Micro - AMT is via Intel I219-LM.
Dell Optiplex 7010 Micro - AMT is via Intel I219-LM
HP EliteDesk 800 G6 Mini - AMT is via Intel I219-LM
I've read that there's a potential issue with the e1000e driver with the I217-LM and I219-LM network controllers, but I've not experienced any system halts or lock-ups during use over the last 6 months of running Proxmox environment.
It looks like during shutdown the Proxmox Kernel is switching off the network interface as the UniFi switch network activity light goes from Green (1GbE link) to completely off when shutting down the HP EliteDesk 800 G6 Mini. On the Dell Optiplex's the light goes from Green (1GbE link) to Amber (10/100Mb link) but IP ping is still unavailable.
I've tried a number of options proposed by Google Searches / AI Chatbots to force the network interface to remain up as the Proxmox Kernel shuts down, but none of them have worked.
It seems ESXi and Proxmox have implemented a different way of managing the network interfaces during the shutdown process and Proxmox is aggressively powering off the network interfaces, where as ESXi left them available.
Has anyone else experienced this issue with their Proxmox Hosts - either with the same network chipsets or others, and more importantly does anyone have a fix for this so I can keep Proxmox running on these PC's and not have to revert back to using ESXi
EDIT:
I'm running Proxmox 9.1.9 on all devices with all updates applied
This is the fping of the AMT interface (192.168.200.27) and the Proxmox interface (192.168.140.27) when a shutdown command is issued (at 10th ping). You can see the Proxmox interface goes offline a few pings (no. 24) before the AMT interface is also disabled (no. 28) and the PC completely shuts down.
fping -l -i 100 192.168.140.27 192.168.200.27
192.168.140.27 : [0], 64 bytes, 5.03 ms (5.03 avg, 0% loss)
192.168.200.27 : [0], 64 bytes, 6.24 ms (6.24 avg, 0% loss)
192.168.140.27 : [1], 64 bytes, 4.60 ms (4.82 avg, 0% loss)
192.168.200.27 : [1], 64 bytes, 3.88 ms (5.06 avg, 0% loss)
192.168.140.27 : [2], 64 bytes, 4.99 ms (4.87 avg, 0% loss)
192.168.200.27 : [2], 64 bytes, 12.5 ms (7.55 avg, 0% loss)
192.168.140.27 : [3], 64 bytes, 5.51 ms (5.03 avg, 0% loss)
192.168.200.27 : [3], 64 bytes, 5.80 ms (7.11 avg, 0% loss)
192.168.140.27 : [4], 64 bytes, 4.96 ms (5.02 avg, 0% loss)
192.168.200.27 : [4], 64 bytes, 4.72 ms (6.63 avg, 0% loss)
192.168.140.27 : [5], 64 bytes, 4.76 ms (4.97 avg, 0% loss)
192.168.200.27 : [5], 64 bytes, 5.12 ms (6.38 avg, 0% loss)
192.168.140.27 : [6], 64 bytes, 4.87 ms (4.96 avg, 0% loss)
192.168.200.27 : [6], 64 bytes, 5.59 ms (6.27 avg, 0% loss)
192.168.140.27 : [7], 64 bytes, 4.84 ms (4.94 avg, 0% loss)
192.168.200.27 : [7], 64 bytes, 5.56 ms (6.18 avg, 0% loss)
192.168.140.27 : [8], 64 bytes, 4.38 ms (4.88 avg, 0% loss)
192.168.200.27 : [8], 64 bytes, 5.10 ms (6.06 avg, 0% loss)
192.168.140.27 : [9], 64 bytes, 4.88 ms (4.88 avg, 0% loss)
192.168.200.27 : [9], 64 bytes, 6.13 ms (6.07 avg, 0% loss)
192.168.140.27 : [10], 64 bytes, 4.84 ms (4.88 avg, 0% loss)
192.168.200.27 : [10], 64 bytes, 5.95 ms (6.06 avg, 0% loss)
192.168.140.27 : [11], 64 bytes, 4.36 ms (4.83 avg, 0% loss)
192.168.200.27 : [11], 64 bytes, 5.17 ms (5.98 avg, 0% loss)
192.168.140.27 : [12], 64 bytes, 9.78 ms (5.21 avg, 0% loss)
192.168.200.27 : [12], 64 bytes, 6.10 ms (5.99 avg, 0% loss)
192.168.140.27 : [13], 64 bytes, 4.96 ms (5.20 avg, 0% loss)
192.168.200.27 : [13], 64 bytes, 5.24 ms (5.94 avg, 0% loss)
192.168.140.27 : [14], 64 bytes, 4.31 ms (5.14 avg, 0% loss)
192.168.200.27 : [14], 64 bytes, 8.50 ms (6.11 avg, 0% loss)
192.168.140.27 : [15], 64 bytes, 9.17 ms (5.39 avg, 0% loss)
192.168.200.27 : [15], 64 bytes, 5.21 ms (6.05 avg, 0% loss)
192.168.140.27 : [16], 64 bytes, 4.78 ms (5.35 avg, 0% loss)
192.168.200.27 : [16], 64 bytes, 4.92 ms (5.98 avg, 0% loss)
192.168.140.27 : [17], 64 bytes, 4.14 ms (5.29 avg, 0% loss)
192.168.200.27 : [17], 64 bytes, 6.61 ms (6.02 avg, 0% loss)
192.168.140.27 : [18], 64 bytes, 4.90 ms (5.26 avg, 0% loss)
192.168.200.27 : [18], 64 bytes, 5.38 ms (5.99 avg, 0% loss)
192.168.140.27 : [19], 64 bytes, 4.84 ms (5.24 avg, 0% loss)
192.168.200.27 : [19], 64 bytes, 5.47 ms (5.96 avg, 0% loss)
192.168.140.27 : [20], 64 bytes, 4.21 ms (5.19 avg, 0% loss)
192.168.200.27 : [20], 64 bytes, 5.12 ms (5.92 avg, 0% loss)
192.168.140.27 : [21], 64 bytes, 4.90 ms (5.18 avg, 0% loss)
192.168.200.27 : [21], 64 bytes, 6.10 ms (5.93 avg, 0% loss)
192.168.140.27 : [22], 64 bytes, 5.08 ms (5.18 avg, 0% loss)
192.168.200.27 : [22], 64 bytes, 5.05 ms (5.89 avg, 0% loss)
192.168.140.27 : [23], 64 bytes, 3.91 ms (5.12 avg, 0% loss)
192.168.200.27 : [23], 64 bytes, 5.75 ms (5.88 avg, 0% loss)
192.168.200.27 : [24], 64 bytes, 5.29 ms (5.86 avg, 0% loss)
192.168.140.27 : [24], timed out (5.12 avg, 4% loss)
192.168.200.27 : [25], 64 bytes, 4.83 ms (5.82 avg, 0% loss)
192.168.140.27 : [25], timed out (5.12 avg, 7% loss)
192.168.200.27 : [26], 64 bytes, 5.96 ms (5.83 avg, 0% loss)
192.168.140.27 : [26], timed out (5.12 avg, 11% loss)
192.168.200.27 : [27], 64 bytes, 82.7 ms (8.57 avg, 0% loss)
192.168.140.27 : [27], timed out (5.12 avg, 14% loss)
192.168.140.27 : [28], timed out (5.12 avg, 17% loss)
192.168.200.27 : [28], timed out (8.57 avg, 3% loss)
192.168.140.27 : [29], timed out (5.12 avg, 20% loss)
192.168.200.27 : [29], timed out (8.57 avg, 6% loss)
192.168.140.27 : [30], timed out (5.12 avg, 22% loss)
192.168.200.27 : [30], timed out (8.57 avg, 9% loss)
192.168.140.27 : [31], timed out (5.12 avg, 25% loss)
192.168.200.27 : [31], timed out (8.57 avg, 12% loss)
192.168.140.27 : [32], timed out (5.12 avg, 27% loss)
192.168.200.27 : [32], timed out (8.57 avg, 15% loss)
192.168.140.27 : [33], timed out (5.12 avg, 29% loss)
192.168.200.27 : [33], timed out (8.57 avg, 17% loss)
192.168.140.27 : [34], timed out (5.12 avg, 31% loss)
192.168.200.27 : [34], timed out (8.57 avg, 20% loss)
192.168.140.27 : [35], timed out (5.12 avg, 33% loss)
192.168.200.27 : [35], timed out (8.57 avg, 22% loss)
192.168.140.27 : [36], timed out (5.12 avg, 35% loss)
192.168.200.27 : [36], timed out (8.57 avg, 24% loss)
192.168.140.27 : [37], timed out (5.12 avg, 36% loss)
192.168.200.27 : [37], timed out (8.57 avg, 26% loss)
192.168.140.27 : [38], timed out (5.12 avg, 38% loss)
192.168.200.27 : [38], timed out (8.57 avg, 28% loss)
192.168.140.27 : [39], timed out (5.12 avg, 40% loss)
192.168.200.27 : [39], timed out (8.57 avg, 30% loss)
192.168.140.27 : [40], timed out (5.12 avg, 41% loss)
192.168.200.27 : [40], timed out (8.57 avg, 31% loss)
I'm new to Proxmox having used ESXi Standalone Hypervisors in my home lab for the past 10 years.
Loving the experience except for one issue I'm having with my PC's losing their AMT connections once Proxmox has been shutdown - making it impossible to restart them again remotely.
I have 4 Hosts and all have the same issue, once the host has shutdown AMT goes offline and the host requires a physical button press to restart.
Hosts all have AMT static coded to a 192.168.200.x IP address and use VLAN200 native port on the UniFi switches
Management GUI traffic is via a 192.168.140.x IP address using VLAN140
VM Traffic is split across VLAN110 & VLAN140 depending on the VM purpose.
3 of the hosts are Micro PC's and therefore only have one network port for all this traffic. ESXi was able to handle this without issue.
The 4th has a dedicated network port for AMT traffic, a dedicated network port for Management traffic and a further port for all VM traffic.
Devices are
Lenovo TS140 - AMT is via Intel I217-LM, Machine Management and VM Network interfaces are on separate Intel card.
Dell Optiplex 7050 Micro - AMT is via Intel I219-LM.
Dell Optiplex 7010 Micro - AMT is via Intel I219-LM
HP EliteDesk 800 G6 Mini - AMT is via Intel I219-LM
I've read that there's a potential issue with the e1000e driver with the I217-LM and I219-LM network controllers, but I've not experienced any system halts or lock-ups during use over the last 6 months of running Proxmox environment.
It looks like during shutdown the Proxmox Kernel is switching off the network interface as the UniFi switch network activity light goes from Green (1GbE link) to completely off when shutting down the HP EliteDesk 800 G6 Mini. On the Dell Optiplex's the light goes from Green (1GbE link) to Amber (10/100Mb link) but IP ping is still unavailable.
I've tried a number of options proposed by Google Searches / AI Chatbots to force the network interface to remain up as the Proxmox Kernel shuts down, but none of them have worked.
It seems ESXi and Proxmox have implemented a different way of managing the network interfaces during the shutdown process and Proxmox is aggressively powering off the network interfaces, where as ESXi left them available.
Has anyone else experienced this issue with their Proxmox Hosts - either with the same network chipsets or others, and more importantly does anyone have a fix for this so I can keep Proxmox running on these PC's and not have to revert back to using ESXi
EDIT:
I'm running Proxmox 9.1.9 on all devices with all updates applied
This is the fping of the AMT interface (192.168.200.27) and the Proxmox interface (192.168.140.27) when a shutdown command is issued (at 10th ping). You can see the Proxmox interface goes offline a few pings (no. 24) before the AMT interface is also disabled (no. 28) and the PC completely shuts down.
fping -l -i 100 192.168.140.27 192.168.200.27
192.168.140.27 : [0], 64 bytes, 5.03 ms (5.03 avg, 0% loss)
192.168.200.27 : [0], 64 bytes, 6.24 ms (6.24 avg, 0% loss)
192.168.140.27 : [1], 64 bytes, 4.60 ms (4.82 avg, 0% loss)
192.168.200.27 : [1], 64 bytes, 3.88 ms (5.06 avg, 0% loss)
192.168.140.27 : [2], 64 bytes, 4.99 ms (4.87 avg, 0% loss)
192.168.200.27 : [2], 64 bytes, 12.5 ms (7.55 avg, 0% loss)
192.168.140.27 : [3], 64 bytes, 5.51 ms (5.03 avg, 0% loss)
192.168.200.27 : [3], 64 bytes, 5.80 ms (7.11 avg, 0% loss)
192.168.140.27 : [4], 64 bytes, 4.96 ms (5.02 avg, 0% loss)
192.168.200.27 : [4], 64 bytes, 4.72 ms (6.63 avg, 0% loss)
192.168.140.27 : [5], 64 bytes, 4.76 ms (4.97 avg, 0% loss)
192.168.200.27 : [5], 64 bytes, 5.12 ms (6.38 avg, 0% loss)
192.168.140.27 : [6], 64 bytes, 4.87 ms (4.96 avg, 0% loss)
192.168.200.27 : [6], 64 bytes, 5.59 ms (6.27 avg, 0% loss)
192.168.140.27 : [7], 64 bytes, 4.84 ms (4.94 avg, 0% loss)
192.168.200.27 : [7], 64 bytes, 5.56 ms (6.18 avg, 0% loss)
192.168.140.27 : [8], 64 bytes, 4.38 ms (4.88 avg, 0% loss)
192.168.200.27 : [8], 64 bytes, 5.10 ms (6.06 avg, 0% loss)
192.168.140.27 : [9], 64 bytes, 4.88 ms (4.88 avg, 0% loss)
192.168.200.27 : [9], 64 bytes, 6.13 ms (6.07 avg, 0% loss)
192.168.140.27 : [10], 64 bytes, 4.84 ms (4.88 avg, 0% loss)
192.168.200.27 : [10], 64 bytes, 5.95 ms (6.06 avg, 0% loss)
192.168.140.27 : [11], 64 bytes, 4.36 ms (4.83 avg, 0% loss)
192.168.200.27 : [11], 64 bytes, 5.17 ms (5.98 avg, 0% loss)
192.168.140.27 : [12], 64 bytes, 9.78 ms (5.21 avg, 0% loss)
192.168.200.27 : [12], 64 bytes, 6.10 ms (5.99 avg, 0% loss)
192.168.140.27 : [13], 64 bytes, 4.96 ms (5.20 avg, 0% loss)
192.168.200.27 : [13], 64 bytes, 5.24 ms (5.94 avg, 0% loss)
192.168.140.27 : [14], 64 bytes, 4.31 ms (5.14 avg, 0% loss)
192.168.200.27 : [14], 64 bytes, 8.50 ms (6.11 avg, 0% loss)
192.168.140.27 : [15], 64 bytes, 9.17 ms (5.39 avg, 0% loss)
192.168.200.27 : [15], 64 bytes, 5.21 ms (6.05 avg, 0% loss)
192.168.140.27 : [16], 64 bytes, 4.78 ms (5.35 avg, 0% loss)
192.168.200.27 : [16], 64 bytes, 4.92 ms (5.98 avg, 0% loss)
192.168.140.27 : [17], 64 bytes, 4.14 ms (5.29 avg, 0% loss)
192.168.200.27 : [17], 64 bytes, 6.61 ms (6.02 avg, 0% loss)
192.168.140.27 : [18], 64 bytes, 4.90 ms (5.26 avg, 0% loss)
192.168.200.27 : [18], 64 bytes, 5.38 ms (5.99 avg, 0% loss)
192.168.140.27 : [19], 64 bytes, 4.84 ms (5.24 avg, 0% loss)
192.168.200.27 : [19], 64 bytes, 5.47 ms (5.96 avg, 0% loss)
192.168.140.27 : [20], 64 bytes, 4.21 ms (5.19 avg, 0% loss)
192.168.200.27 : [20], 64 bytes, 5.12 ms (5.92 avg, 0% loss)
192.168.140.27 : [21], 64 bytes, 4.90 ms (5.18 avg, 0% loss)
192.168.200.27 : [21], 64 bytes, 6.10 ms (5.93 avg, 0% loss)
192.168.140.27 : [22], 64 bytes, 5.08 ms (5.18 avg, 0% loss)
192.168.200.27 : [22], 64 bytes, 5.05 ms (5.89 avg, 0% loss)
192.168.140.27 : [23], 64 bytes, 3.91 ms (5.12 avg, 0% loss)
192.168.200.27 : [23], 64 bytes, 5.75 ms (5.88 avg, 0% loss)
192.168.200.27 : [24], 64 bytes, 5.29 ms (5.86 avg, 0% loss)
192.168.140.27 : [24], timed out (5.12 avg, 4% loss)
192.168.200.27 : [25], 64 bytes, 4.83 ms (5.82 avg, 0% loss)
192.168.140.27 : [25], timed out (5.12 avg, 7% loss)
192.168.200.27 : [26], 64 bytes, 5.96 ms (5.83 avg, 0% loss)
192.168.140.27 : [26], timed out (5.12 avg, 11% loss)
192.168.200.27 : [27], 64 bytes, 82.7 ms (8.57 avg, 0% loss)
192.168.140.27 : [27], timed out (5.12 avg, 14% loss)
192.168.140.27 : [28], timed out (5.12 avg, 17% loss)
192.168.200.27 : [28], timed out (8.57 avg, 3% loss)
192.168.140.27 : [29], timed out (5.12 avg, 20% loss)
192.168.200.27 : [29], timed out (8.57 avg, 6% loss)
192.168.140.27 : [30], timed out (5.12 avg, 22% loss)
192.168.200.27 : [30], timed out (8.57 avg, 9% loss)
192.168.140.27 : [31], timed out (5.12 avg, 25% loss)
192.168.200.27 : [31], timed out (8.57 avg, 12% loss)
192.168.140.27 : [32], timed out (5.12 avg, 27% loss)
192.168.200.27 : [32], timed out (8.57 avg, 15% loss)
192.168.140.27 : [33], timed out (5.12 avg, 29% loss)
192.168.200.27 : [33], timed out (8.57 avg, 17% loss)
192.168.140.27 : [34], timed out (5.12 avg, 31% loss)
192.168.200.27 : [34], timed out (8.57 avg, 20% loss)
192.168.140.27 : [35], timed out (5.12 avg, 33% loss)
192.168.200.27 : [35], timed out (8.57 avg, 22% loss)
192.168.140.27 : [36], timed out (5.12 avg, 35% loss)
192.168.200.27 : [36], timed out (8.57 avg, 24% loss)
192.168.140.27 : [37], timed out (5.12 avg, 36% loss)
192.168.200.27 : [37], timed out (8.57 avg, 26% loss)
192.168.140.27 : [38], timed out (5.12 avg, 38% loss)
192.168.200.27 : [38], timed out (8.57 avg, 28% loss)
192.168.140.27 : [39], timed out (5.12 avg, 40% loss)
192.168.200.27 : [39], timed out (8.57 avg, 30% loss)
192.168.140.27 : [40], timed out (5.12 avg, 41% loss)
192.168.200.27 : [40], timed out (8.57 avg, 31% loss)
Last edited: