Win 2016 R2 Hyper - V - Problem mit NIC - wachsendes allocated memory führt zu ungeplantem Reboot
Hallo liebe Community,
wir haben auf einem Windows 2016 R2 Server mehrerere virtuelle Maschinen laufen. Seit einigen Wochen kommt es immer wieder zu einem ungeplantem Neustart der Mutterkiste.
Im Event Log tauchen vorher immer folgende Einträge auf:
Memory allocated for packets in a vRss queue (on CPU 0) on switch F79B4ACA-CB81-4369-ADEB-1D74E2AC3CE5 (Friendly Name: XXX) due to low resource on the physical NIC has increased to 256MB. Packets will be dropped once queue size reaches 512MB.
5 Minuten später:
Memory allocated for packets in a vRss queue (on CPU 0) on switch F79B4ACA-CB81-4369-ADEB-1D74E2AC3CE5 (Friendly Name: XXX) due to low resource on the physical NIC has increased to 69636MB. Packets will be dropped once queue size reaches 512MB.
--> ungeplanter Reboot des Hyper-V-Servers
Schließlich kurz nach dem Reboot:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Vor dem Beginn der Probleme mit dem allocated memory taucht immer der gleiche Eintrag zur selben MAC auf.
Level Date and Time Source Event ID Task Category
Information 01.03.2018 00:59:39 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External) to port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX).
Information 01.03.2018 00:59:39 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX) to port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External).
Information 01.03.2018 00:59:39 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External) to port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX).
Information 01.03.2018 00:59:37 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX) to port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External).
Information 01.03.2018 00:59:37 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External) to port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX).
Information 01.03.2018 00:59:36 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX) to port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External).
Hat dieses Phänomen schon irgendjemand beobachtet bzw. hat einen Tipp für die Lösung?
Vielen Dank,
Gerald
wir haben auf einem Windows 2016 R2 Server mehrerere virtuelle Maschinen laufen. Seit einigen Wochen kommt es immer wieder zu einem ungeplantem Neustart der Mutterkiste.
Im Event Log tauchen vorher immer folgende Einträge auf:
Memory allocated for packets in a vRss queue (on CPU 0) on switch F79B4ACA-CB81-4369-ADEB-1D74E2AC3CE5 (Friendly Name: XXX) due to low resource on the physical NIC has increased to 256MB. Packets will be dropped once queue size reaches 512MB.
5 Minuten später:
Memory allocated for packets in a vRss queue (on CPU 0) on switch F79B4ACA-CB81-4369-ADEB-1D74E2AC3CE5 (Friendly Name: XXX) due to low resource on the physical NIC has increased to 69636MB. Packets will be dropped once queue size reaches 512MB.
--> ungeplanter Reboot des Hyper-V-Servers
Schließlich kurz nach dem Reboot:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Vor dem Beginn der Probleme mit dem allocated memory taucht immer der gleiche Eintrag zur selben MAC auf.
Level Date and Time Source Event ID Task Category
Information 01.03.2018 00:59:39 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External) to port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX).
Information 01.03.2018 00:59:39 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX) to port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External).
Information 01.03.2018 00:59:39 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External) to port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX).
Information 01.03.2018 00:59:37 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX) to port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External).
Information 01.03.2018 00:59:37 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External) to port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX).
Information 01.03.2018 00:59:36 Microsoft-Windows-Hyper-V-VmSwitch 25 (1018) The MAC address 0C-C4-7A-DA-C9-52 has moved from port 28ED24A4-057C-4FEB-A731-1A6175025715 (Friendly Name: XXX) to port E3282501-DA8C-40A4-AA0A-22C91E0E48D5 (Friendly Name: XXX_External).
Hat dieses Phänomen schon irgendjemand beobachtet bzw. hat einen Tipp für die Lösung?
Vielen Dank,
Gerald
Bitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 366574
Url: https://administrator.de/forum/win-2016-r2-hyper-v-problem-mit-nic-wachsendes-allocated-memory-fuehrt-zu-ungeplantem-reboot-366574.html
Ausgedruckt am: 25.12.2024 um 14:12 Uhr
3 Kommentare
Neuester Kommentar
Moin,
hast Du die Google Tipps schon mal durchgetestet?
https://social.technet.microsoft.com/wiki/contents/articles/31357.hyper- ...
https://social.technet.microsoft.com/Forums/windowsserver/en-US/681708f1 ...
Gruss
hast Du die Google Tipps schon mal durchgetestet?
https://social.technet.microsoft.com/wiki/contents/articles/31357.hyper- ...
https://social.technet.microsoft.com/Forums/windowsserver/en-US/681708f1 ...
Gruss