ΠΊΠΎΠ΄ ΠΎΡΠΈΠ±ΠΊΠΈ 32788 hyper v
ΠΠ’ ΠΠ°Π·Π° Π·Π½Π°Π½ΠΈΠΉ
ΠΠΎΠ»Π΅Π·Π½ΠΎ
β ΠΠ½Π»Π°ΠΉΠ½ Π³Π΅Π½Π΅ΡΠ°ΡΠΎΡ ΡΡΡΠΎΠΉΡΠΈΠ²ΡΡ ΠΏΠ°ΡΠΎΠ»Π΅ΠΉ
β ΠΠ½Π»Π°ΠΉΠ½ ΠΊΠ°Π»ΡΠΊΡΠ»ΡΡΠΎΡ ΠΏΠΎΠ΄ΡΠ΅ΡΠ΅ΠΉ
β Π ΡΠΊΠΎΠ²ΠΎΠ΄ΡΡΠ²ΠΎ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° FreePBX Π½Π° ΡΡΡΡΠΊΠΎΠΌ ΡΠ·ΡΠΊΠ΅
β Π ΡΠΊΠΎΠ²ΠΎΠ΄ΡΡΠ²ΠΎ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° Cisco UCM/CME Π½Π° ΡΡΡΡΠΊΠΎΠΌ ΡΠ·ΡΠΊΠ΅
β Π ΡΠΊΠΎΠ²ΠΎΠ΄ΡΡΠ²ΠΎ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° ΠΏΠΎ Linux/Unix
ΠΠ°Π²ΠΈΠ³Π°ΡΠΈΡ
Π‘Π΅ΡΠ²Π΅ΡΠ½ΡΠ΅ ΡΠ΅ΡΠ΅Π½ΠΈΡ
Π’Π΅Π»Π΅ΡΠΎΠ½ΠΈΡ
FreePBX ΠΈ Asterisk
ΠΠ°ΡΡΡΠΎΠΉΠΊΠ° ΠΏΡΠΎΠ³ΡΠ°ΠΌΠΌΠ½ΡΡ ΡΠ΅Π»Π΅ΡΠΎΠ½ΠΎΠ²
ΠΠΎΡΠΏΠΎΡΠ°ΡΠΈΠ²Π½ΡΠ΅ ΡΠ΅ΡΠΈ
ΠΡΠΎΡΠΎΠΊΠΎΠ»Ρ ΠΈ ΡΡΠ°Π½Π΄Π°ΡΡΡ
Hyper-V: ΠΈΡΠΏΡΠ°Π²Π»ΡΠ΅ΠΌ ΠΎΡΠΈΠ±ΠΊΡ 32788
Π§ΠΈΠ½ΠΈΠΌ Π²Π°ΡΡ Π²ΠΈΡΡΡΠ°Π»ΠΈΠ·Π°ΡΡ
ΠΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΠ΅Π»ΠΈ ΠΎΡΠ΅Π½Ρ ΡΠ°ΡΡΠΎ Π²ΡΡΡΠ΅ΡΠ°ΡΡΡΡ Ρ ΠΎΡΠΈΠ±ΠΊΠΎΠΉ 32788 Π² ΡΡΠ΅Π΄Π΅ Π²ΠΈΡΡΡΠ°Π»ΠΈΠ·Π°ΡΠΈΠΈ Hyper-V. ΠΡΠ»ΠΈ Π±ΡΡΡ ΡΠΎΡΠ½ΡΠΌ, ΡΠΎ ΠΏΠΎΠ»Π½Π°Ρ ΡΠΎΡΠΌΡΠ»ΠΈΡΠΎΠ²ΠΊΠ° ΠΎΡΠΈΠ±ΠΊΠΈ ΡΠ»Π΅Π΄ΡΡΡΠ°Ρ:
ΠΠ½Π»Π°ΠΉΠ½ ΠΊΡΡΡ ΠΏΠΎ Linux
ΠΡ ΡΠΎΠ±ΡΠ°Π»ΠΈ ΠΊΠΎΠ½ΡΠ΅Π½ΡΡΠ°Ρ ΡΠ°ΠΌΡΡ Π²ΠΎΡΡΡΠ΅Π±ΠΎΠ²Π°Π½Π½ΡΡ Π·Π½Π°Π½ΠΈΠΉ, ΠΊΠΎΡΠΎΡΡΠ΅ ΠΏΠΎΠ·Π²ΠΎΠ»ΡΡ ΡΠ΅Π±Π΅ Π½Π°ΡΠ°ΡΡ ΠΊΠ°ΡΡΠ΅ΡΡ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° Linux, ΡΠ°ΡΡΠΈΡΠΈΡΡ ΡΠ΅ΠΊΡΡΠΈΠ΅ Π·Π½Π°Π½ΠΈΡ ΠΈ ΡΠ΄Π΅Π»Π°ΡΡ ΡΠ²Π΅ΡΠ΅Π½Π½ΡΠΉ ΡΠ°Π³ ΠΊ DevOps
The application encountered an error while attempting to change the state of %ΠΈΠΌΡ_Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΠΎΠΉ_ΠΌΠ°ΡΠΈΠ½Ρ%.
%ΠΈΠΌΡ_Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΠΎΠΉ_ΠΌΠ°ΡΠΈΠ½Ρ% failed to change state. The operation cannot be performed while the object is in use with error code 32788
ΠΡΠ³Π»ΡΠ΄ΠΈΡ ΡΡΠΎ Β«Π½Π΅ΠΏΡΠΈΡΡΠ½ΠΎΠ΅Β» popup ΠΎΠΊΠ½ΠΎ ΠΏΡΠΈΠΌΠ΅ΡΠ½ΠΎ Π²ΠΎΡ ΡΠ°ΠΊ:
ΠΡΠΈΠ±ΠΊΠ° ΠΏΠΎΡΠ²Π»ΡΠ΅ΡΡΡ, ΠΊΠΎΠ³Π΄Π° ΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΠ΅Π»Ρ ΠΏΡΡΠ°Π΅ΡΡΡ Π·Π°ΠΏΡΡΡΠΈΡΡ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΡ ΠΌΠ°ΡΠΈΠ½Ρ. ΠΡΠ°ΠΊ, ΠΏΠΎΠ³Π½Π°Π»ΠΈ ΡΠ°Π·Π±ΠΈΡΠ°ΡΡΡΡ. ΠΠ°Π½Π½ΡΠΉ Π³Π°ΠΉΠ΄ ΠΏΠΎΠ΄ΠΎΠΉΠ΄Π΅Ρ Π΄Π»Ρ Hyper-V Π²Π΅ΡΡΠΈΠΉ 2012 R2 ΠΈ 2016.
ΠΡΠ°ΡΠΊΠ°Ρ ΠΌΠ°ΡΡΠ°ΡΡΡ
ΠΡΠΈΠ±ΠΊΠ° Π²ΠΎΠ·Π½ΠΈΠΊΠ°Π΅Ρ, ΠΈΠ· Π·Π° ΡΠΎΠ³ΠΎ, ΡΡΠΎ Π²ΠΈΡΡΡΠ°Π»ΠΈΠ·Π°ΡΠΈΡ ΡΡΠΎ Π½Π΅ΡΠΊΠΎΠ»ΡΠΊΠΎ Π±ΠΎΠ»Π΅Π΅ ΡΠ»ΠΎΠΆΠ½Π°Ρ ΡΡΡΠΊΠ°, ΡΠ΅ΠΌ ΠΏΡΠΎΡΡΠΎ ΡΠΎΠ·Π΄Π°Π½ΠΈΠ΅ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΡ Π²ΡΡΠΈΡΠ»ΠΈΡΠ΅Π»ΡΠ½ΡΡ ΠΌΠ°ΡΠΈΠ½ ΠΏΠΎΠ²Π΅ΡΡ ΡΠΈΠ·ΠΈΡΠ΅ΡΠΊΠΎΠ³ΠΎ ΡΡΡΡΠΎΠΉΡΡΠ²Π°. ΠΠ½ΡΡΡΠΈ ΠΊΠ°ΠΆΠ΄ΠΎΠΉ Π΅ΡΡΡ ΠΎΠΏΠ΅ΡΠ°ΡΠΈΠΎΠ½Π½ΡΠ΅ ΡΠΈΡΡΠ΅ΠΌΡ, ΡΠ΅ΡΠ΅Π²ΡΠ΅ Π°Π΄Π°ΠΏΡΠ΅ΡΡ, Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΠ΅ ΠΊΠΎΠΌΠΌΡΡΠ°ΡΠΎΡΡ, ΡΡΡΡΠΎΠΉΡΡΠ²Π° Π΄Π»Ρ Ρ ΡΠ°Π½Π΅Π½ΠΈΡ, ΠΈΠ½ΡΠ΅ΡΡΠ΅ΠΉΡΡ Π²Π·Π°ΠΈΠΌΠΎΠ΄Π΅ΠΉΡΡΠ²ΠΈΡ ΠΈ Π΄ΡΡΠ³ΠΈΠ΅.
Π‘Π°ΠΌ ΠΈΠ½ΡΠ΅ΡΡΠ΅ΠΉΡ Hyper-V β ΡΡΠΎ Π»ΠΈΡΡ ΠΊΠΎΠ½ΡΠΎΠ»Ρ ΡΠΏΡΠ°Π²Π»Π΅Π½ΠΈΡ. Π£ΡΡΠ°ΡΠ΅Π²ΡΠ°Ρ ΠΈ Π½Π΅Π°ΠΊΡΡΠ°Π»ΡΠ½Π°Ρ ΠΊΠΎΠ½ΡΠΈΠ³ΡΡΠ°ΡΠΈΡ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΡ ΠΌΠ°ΡΠΈΠ½ ΠΏΡΠΈΠ²ΠΎΠ΄ΠΈΡ ΠΊ Π²ΠΎΠ·Π½ΠΈΠΊΠ½ΠΎΠ²Π΅Π½ΠΈΡ ΠΎΡΠΈΠ±ΠΎΠΊ. Π ΡΠΎΠΌ ΡΠΈΡΠ»Π΅, ΠΈ ΠΎΡΠΈΠ±ΠΊΠ΅ 32788.
ΠΡΠ½ΠΎΠ²Π½ΡΠ΅ ΠΏΡΠΈΡΠΈΠ½Ρ ΠΎΡΠΈΠ±ΠΊΠΈ 32788
Π‘Π°ΠΌΡΠ΅ Π³Π»Π°Π²Π½ΡΠ΅ ΠΏΡΠΈΡΠΈΠ½Ρ ΠΎΡΠΈΠ±ΠΊΠΈ 32788, ΠΊΠΎΡΠΎΡΡΠ΅ ΠΌΡ Π²ΠΎΡΠΏΡΠΎΠΈΠ·Π²ΠΎΠ΄ΠΈΠ»ΠΈ Π½Π° ΠΎΠΏΡΡΠ΅:
ΠΡΠΏΡΠ°Π²Π»ΡΠ΅ΠΌ ΠΎΡΠΈΠ±ΠΊΡ 32788
ΠΡΠ°ΠΊ, ΡΡΠΎΠ±Ρ ΠΈΡΠΏΡΠ°Π²ΠΈΡΡ ΠΎΡΠΈΠ±ΠΊΡ, Π½ΡΠΆΠ½ΠΎ:
ΠΠΎΡ ΠΎΠ½Π°, ΠΏΡΠΈΡΠΈΠ½Π° ΠΎΡΠΈΠ±ΠΊΠΈ 32788 Π² Π½Π°ΡΠ΅ΠΉ ΡΠ»ΡΡΠ°Π΅ β ΡΡΡΠ°ΡΠ΅Π²ΡΠΈΠ΅ Π½Π°ΡΡΡΠΎΠΉΠΊΠΈ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΠΎΠ³ΠΎ ΠΊΠΎΠΌΠΌΡΡΠ°ΡΠΎΡΠ°. ΠΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎ, Π΅Π³ΠΎ ΠΊΡΠΎ ΡΠΎ ΡΠ΄Π°Π»ΠΈΠ», ΠΈΠ»ΠΈ ΠΈΠ·ΠΌΠ΅Π½ΠΈΠ» Π΅Π³ΠΎ ΠΈΠΌΡ.
Π Π»ΡΠ±ΠΎΠΌ ΡΠ»ΡΡΠ°Π΅, Π½Π°ΠΌ Π½ΡΠΆΠ½ΠΎ ΠΈΡΠΏΡΠ°Π²ΠΈΡΡ ΡΡΠΎ. Π‘ΠΎΠ·Π΄Π°Π΅ΠΌ Π½ΠΎΠ²ΡΠΉ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΠΉ ΠΊΠΎΠΌΠΌΡΡΠ°ΡΠΎΡ (Virtual Switch) ΡΠΈΠΏΠ° Internal, Π΄Π»Ρ Π²Π½ΡΡΡΠ΅Π½Π½Π΅Π³ΠΎ ΠΈΡΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°Π½ΠΈΡ:
ΠΠΎΡΠ»Π΅ Π²Π½Π΅ΡΠ΅Π½ΠΈΠ΅ Π²ΡΠ΅Ρ ΠΈΠ·ΠΌΠ΅Π½Π΅Π½ΠΈΠΉ ΠΏΠ΅ΡΠ΅Π·Π°Π³ΡΡΠ·ΠΈΡΠ΅ (Π²ΡΠΏΠΎΠ»Π½ΠΈΡΠ΅ ΡΠ΅ΡΡΠ°ΡΡ) Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΡ ΠΌΠ°ΡΠΈΠ½Ρ.
ΠΠ½Π»Π°ΠΉΠ½ ΠΊΡΡΡ ΠΏΠΎ Linux
ΠΡ ΡΠΎΠ±ΡΠ°Π»ΠΈ ΠΊΠΎΠ½ΡΠ΅Π½ΡΡΠ°Ρ ΡΠ°ΠΌΡΡ Π²ΠΎΡΡΡΠ΅Π±ΠΎΠ²Π°Π½Π½ΡΡ Π·Π½Π°Π½ΠΈΠΉ, ΠΊΠΎΡΠΎΡΡΠ΅ ΠΏΠΎΠ·Π²ΠΎΠ»ΡΡ ΡΠ΅Π±Π΅ Π½Π°ΡΠ°ΡΡ ΠΊΠ°ΡΡΠ΅ΡΡ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° Linux, ΡΠ°ΡΡΠΈΡΠΈΡΡ ΡΠ΅ΠΊΡΡΠΈΠ΅ Π·Π½Π°Π½ΠΈΡ ΠΈ ΡΠ΄Π΅Π»Π°ΡΡ ΡΠ²Π΅ΡΠ΅Π½Π½ΡΠΉ ΡΠ°Π³ ΠΊ DevOps
ΠΠ’ ΠΠ°Π·Π° Π·Π½Π°Π½ΠΈΠΉ
ΠΠΎΠ»Π΅Π·Π½ΠΎ
β ΠΠ½Π»Π°ΠΉΠ½ Π³Π΅Π½Π΅ΡΠ°ΡΠΎΡ ΡΡΡΠΎΠΉΡΠΈΠ²ΡΡ ΠΏΠ°ΡΠΎΠ»Π΅ΠΉ
β ΠΠ½Π»Π°ΠΉΠ½ ΠΊΠ°Π»ΡΠΊΡΠ»ΡΡΠΎΡ ΠΏΠΎΠ΄ΡΠ΅ΡΠ΅ΠΉ
β Π ΡΠΊΠΎΠ²ΠΎΠ΄ΡΡΠ²ΠΎ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° FreePBX Π½Π° ΡΡΡΡΠΊΠΎΠΌ ΡΠ·ΡΠΊΠ΅
β Π ΡΠΊΠΎΠ²ΠΎΠ΄ΡΡΠ²ΠΎ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° Cisco UCM/CME Π½Π° ΡΡΡΡΠΊΠΎΠΌ ΡΠ·ΡΠΊΠ΅
β Π ΡΠΊΠΎΠ²ΠΎΠ΄ΡΡΠ²ΠΎ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° ΠΏΠΎ Linux/Unix
ΠΠ°Π²ΠΈΠ³Π°ΡΠΈΡ
Π‘Π΅ΡΠ²Π΅ΡΠ½ΡΠ΅ ΡΠ΅ΡΠ΅Π½ΠΈΡ
Π’Π΅Π»Π΅ΡΠΎΠ½ΠΈΡ
FreePBX ΠΈ Asterisk
ΠΠ°ΡΡΡΠΎΠΉΠΊΠ° ΠΏΡΠΎΠ³ΡΠ°ΠΌΠΌΠ½ΡΡ ΡΠ΅Π»Π΅ΡΠΎΠ½ΠΎΠ²
ΠΠΎΡΠΏΠΎΡΠ°ΡΠΈΠ²Π½ΡΠ΅ ΡΠ΅ΡΠΈ
ΠΡΠΎΡΠΎΠΊΠΎΠ»Ρ ΠΈ ΡΡΠ°Π½Π΄Π°ΡΡΡ
Hyper-V: ΠΈΡΠΏΡΠ°Π²Π»ΡΠ΅ΠΌ ΠΎΡΠΈΠ±ΠΊΡ 32788
Π§ΠΈΠ½ΠΈΠΌ Π²Π°ΡΡ Π²ΠΈΡΡΡΠ°Π»ΠΈΠ·Π°ΡΡ
ΠΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΠ΅Π»ΠΈ ΠΎΡΠ΅Π½Ρ ΡΠ°ΡΡΠΎ Π²ΡΡΡΠ΅ΡΠ°ΡΡΡΡ Ρ ΠΎΡΠΈΠ±ΠΊΠΎΠΉ 32788 Π² ΡΡΠ΅Π΄Π΅ Π²ΠΈΡΡΡΠ°Π»ΠΈΠ·Π°ΡΠΈΠΈ Hyper-V. ΠΡΠ»ΠΈ Π±ΡΡΡ ΡΠΎΡΠ½ΡΠΌ, ΡΠΎ ΠΏΠΎΠ»Π½Π°Ρ ΡΠΎΡΠΌΡΠ»ΠΈΡΠΎΠ²ΠΊΠ° ΠΎΡΠΈΠ±ΠΊΠΈ ΡΠ»Π΅Π΄ΡΡΡΠ°Ρ:
ΠΠ½Π»Π°ΠΉΠ½ ΠΊΡΡΡ ΠΏΠΎ Linux
ΠΡ ΡΠΎΠ±ΡΠ°Π»ΠΈ ΠΊΠΎΠ½ΡΠ΅Π½ΡΡΠ°Ρ ΡΠ°ΠΌΡΡ Π²ΠΎΡΡΡΠ΅Π±ΠΎΠ²Π°Π½Π½ΡΡ Π·Π½Π°Π½ΠΈΠΉ, ΠΊΠΎΡΠΎΡΡΠ΅ ΠΏΠΎΠ·Π²ΠΎΠ»ΡΡ ΡΠ΅Π±Π΅ Π½Π°ΡΠ°ΡΡ ΠΊΠ°ΡΡΠ΅ΡΡ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° Linux, ΡΠ°ΡΡΠΈΡΠΈΡΡ ΡΠ΅ΠΊΡΡΠΈΠ΅ Π·Π½Π°Π½ΠΈΡ ΠΈ ΡΠ΄Π΅Π»Π°ΡΡ ΡΠ²Π΅ΡΠ΅Π½Π½ΡΠΉ ΡΠ°Π³ ΠΊ DevOps
The application encountered an error while attempting to change the state of %ΠΈΠΌΡ_Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΠΎΠΉ_ΠΌΠ°ΡΠΈΠ½Ρ%.
%ΠΈΠΌΡ_Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΠΎΠΉ_ΠΌΠ°ΡΠΈΠ½Ρ% failed to change state. The operation cannot be performed while the object is in use with error code 32788
ΠΡΠ³Π»ΡΠ΄ΠΈΡ ΡΡΠΎ Β«Π½Π΅ΠΏΡΠΈΡΡΠ½ΠΎΠ΅Β» popup ΠΎΠΊΠ½ΠΎ ΠΏΡΠΈΠΌΠ΅ΡΠ½ΠΎ Π²ΠΎΡ ΡΠ°ΠΊ:
ΠΡΠΈΠ±ΠΊΠ° ΠΏΠΎΡΠ²Π»ΡΠ΅ΡΡΡ, ΠΊΠΎΠ³Π΄Π° ΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΠ΅Π»Ρ ΠΏΡΡΠ°Π΅ΡΡΡ Π·Π°ΠΏΡΡΡΠΈΡΡ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΡ ΠΌΠ°ΡΠΈΠ½Ρ. ΠΡΠ°ΠΊ, ΠΏΠΎΠ³Π½Π°Π»ΠΈ ΡΠ°Π·Π±ΠΈΡΠ°ΡΡΡΡ. ΠΠ°Π½Π½ΡΠΉ Π³Π°ΠΉΠ΄ ΠΏΠΎΠ΄ΠΎΠΉΠ΄Π΅Ρ Π΄Π»Ρ Hyper-V Π²Π΅ΡΡΠΈΠΉ 2012 R2 ΠΈ 2016.
ΠΡΠ°ΡΠΊΠ°Ρ ΠΌΠ°ΡΡΠ°ΡΡΡ
ΠΡΠΈΠ±ΠΊΠ° Π²ΠΎΠ·Π½ΠΈΠΊΠ°Π΅Ρ, ΠΈΠ· Π·Π° ΡΠΎΠ³ΠΎ, ΡΡΠΎ Π²ΠΈΡΡΡΠ°Π»ΠΈΠ·Π°ΡΠΈΡ ΡΡΠΎ Π½Π΅ΡΠΊΠΎΠ»ΡΠΊΠΎ Π±ΠΎΠ»Π΅Π΅ ΡΠ»ΠΎΠΆΠ½Π°Ρ ΡΡΡΠΊΠ°, ΡΠ΅ΠΌ ΠΏΡΠΎΡΡΠΎ ΡΠΎΠ·Π΄Π°Π½ΠΈΠ΅ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΡ Π²ΡΡΠΈΡΠ»ΠΈΡΠ΅Π»ΡΠ½ΡΡ ΠΌΠ°ΡΠΈΠ½ ΠΏΠΎΠ²Π΅ΡΡ ΡΠΈΠ·ΠΈΡΠ΅ΡΠΊΠΎΠ³ΠΎ ΡΡΡΡΠΎΠΉΡΡΠ²Π°. ΠΠ½ΡΡΡΠΈ ΠΊΠ°ΠΆΠ΄ΠΎΠΉ Π΅ΡΡΡ ΠΎΠΏΠ΅ΡΠ°ΡΠΈΠΎΠ½Π½ΡΠ΅ ΡΠΈΡΡΠ΅ΠΌΡ, ΡΠ΅ΡΠ΅Π²ΡΠ΅ Π°Π΄Π°ΠΏΡΠ΅ΡΡ, Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΠ΅ ΠΊΠΎΠΌΠΌΡΡΠ°ΡΠΎΡΡ, ΡΡΡΡΠΎΠΉΡΡΠ²Π° Π΄Π»Ρ Ρ ΡΠ°Π½Π΅Π½ΠΈΡ, ΠΈΠ½ΡΠ΅ΡΡΠ΅ΠΉΡΡ Π²Π·Π°ΠΈΠΌΠΎΠ΄Π΅ΠΉΡΡΠ²ΠΈΡ ΠΈ Π΄ΡΡΠ³ΠΈΠ΅.
Π‘Π°ΠΌ ΠΈΠ½ΡΠ΅ΡΡΠ΅ΠΉΡ Hyper-V β ΡΡΠΎ Π»ΠΈΡΡ ΠΊΠΎΠ½ΡΠΎΠ»Ρ ΡΠΏΡΠ°Π²Π»Π΅Π½ΠΈΡ. Π£ΡΡΠ°ΡΠ΅Π²ΡΠ°Ρ ΠΈ Π½Π΅Π°ΠΊΡΡΠ°Π»ΡΠ½Π°Ρ ΠΊΠΎΠ½ΡΠΈΠ³ΡΡΠ°ΡΠΈΡ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΡ ΠΌΠ°ΡΠΈΠ½ ΠΏΡΠΈΠ²ΠΎΠ΄ΠΈΡ ΠΊ Π²ΠΎΠ·Π½ΠΈΠΊΠ½ΠΎΠ²Π΅Π½ΠΈΡ ΠΎΡΠΈΠ±ΠΎΠΊ. Π ΡΠΎΠΌ ΡΠΈΡΠ»Π΅, ΠΈ ΠΎΡΠΈΠ±ΠΊΠ΅ 32788.
ΠΡΠ½ΠΎΠ²Π½ΡΠ΅ ΠΏΡΠΈΡΠΈΠ½Ρ ΠΎΡΠΈΠ±ΠΊΠΈ 32788
Π‘Π°ΠΌΡΠ΅ Π³Π»Π°Π²Π½ΡΠ΅ ΠΏΡΠΈΡΠΈΠ½Ρ ΠΎΡΠΈΠ±ΠΊΠΈ 32788, ΠΊΠΎΡΠΎΡΡΠ΅ ΠΌΡ Π²ΠΎΡΠΏΡΠΎΠΈΠ·Π²ΠΎΠ΄ΠΈΠ»ΠΈ Π½Π° ΠΎΠΏΡΡΠ΅:
ΠΡΠΏΡΠ°Π²Π»ΡΠ΅ΠΌ ΠΎΡΠΈΠ±ΠΊΡ 32788
ΠΡΠ°ΠΊ, ΡΡΠΎΠ±Ρ ΠΈΡΠΏΡΠ°Π²ΠΈΡΡ ΠΎΡΠΈΠ±ΠΊΡ, Π½ΡΠΆΠ½ΠΎ:
ΠΠΎΡ ΠΎΠ½Π°, ΠΏΡΠΈΡΠΈΠ½Π° ΠΎΡΠΈΠ±ΠΊΠΈ 32788 Π² Π½Π°ΡΠ΅ΠΉ ΡΠ»ΡΡΠ°Π΅ β ΡΡΡΠ°ΡΠ΅Π²ΡΠΈΠ΅ Π½Π°ΡΡΡΠΎΠΉΠΊΠΈ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΠΎΠ³ΠΎ ΠΊΠΎΠΌΠΌΡΡΠ°ΡΠΎΡΠ°. ΠΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎ, Π΅Π³ΠΎ ΠΊΡΠΎ ΡΠΎ ΡΠ΄Π°Π»ΠΈΠ», ΠΈΠ»ΠΈ ΠΈΠ·ΠΌΠ΅Π½ΠΈΠ» Π΅Π³ΠΎ ΠΈΠΌΡ.
Π Π»ΡΠ±ΠΎΠΌ ΡΠ»ΡΡΠ°Π΅, Π½Π°ΠΌ Π½ΡΠΆΠ½ΠΎ ΠΈΡΠΏΡΠ°Π²ΠΈΡΡ ΡΡΠΎ. Π‘ΠΎΠ·Π΄Π°Π΅ΠΌ Π½ΠΎΠ²ΡΠΉ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΠΉ ΠΊΠΎΠΌΠΌΡΡΠ°ΡΠΎΡ (Virtual Switch) ΡΠΈΠΏΠ° Internal, Π΄Π»Ρ Π²Π½ΡΡΡΠ΅Π½Π½Π΅Π³ΠΎ ΠΈΡΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°Π½ΠΈΡ:
ΠΠΎΡΠ»Π΅ Π²Π½Π΅ΡΠ΅Π½ΠΈΠ΅ Π²ΡΠ΅Ρ ΠΈΠ·ΠΌΠ΅Π½Π΅Π½ΠΈΠΉ ΠΏΠ΅ΡΠ΅Π·Π°Π³ΡΡΠ·ΠΈΡΠ΅ (Π²ΡΠΏΠΎΠ»Π½ΠΈΡΠ΅ ΡΠ΅ΡΡΠ°ΡΡ) Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΡ ΠΌΠ°ΡΠΈΠ½Ρ.
ΠΠ½Π»Π°ΠΉΠ½ ΠΊΡΡΡ ΠΏΠΎ Linux
ΠΡ ΡΠΎΠ±ΡΠ°Π»ΠΈ ΠΊΠΎΠ½ΡΠ΅Π½ΡΡΠ°Ρ ΡΠ°ΠΌΡΡ Π²ΠΎΡΡΡΠ΅Π±ΠΎΠ²Π°Π½Π½ΡΡ Π·Π½Π°Π½ΠΈΠΉ, ΠΊΠΎΡΠΎΡΡΠ΅ ΠΏΠΎΠ·Π²ΠΎΠ»ΡΡ ΡΠ΅Π±Π΅ Π½Π°ΡΠ°ΡΡ ΠΊΠ°ΡΡΠ΅ΡΡ Π°Π΄ΠΌΠΈΠ½ΠΈΡΡΡΠ°ΡΠΎΡΠ° Linux, ΡΠ°ΡΡΠΈΡΠΈΡΡ ΡΠ΅ΠΊΡΡΠΈΠ΅ Π·Π½Π°Π½ΠΈΡ ΠΈ ΡΠ΄Π΅Π»Π°ΡΡ ΡΠ²Π΅ΡΠ΅Π½Π½ΡΠΉ ΡΠ°Π³ ΠΊ DevOps
ΠΠΎΠ΄ ΠΎΡΠΈΠ±ΠΊΠΈ 32788 hyper v
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor). When I try to start it with more than 4GB of RAM it fails with this error. I tried creating a new VM, using a different VHD file, all create the same error. Before I updated Hyper-V it used to report insufficient memory. What am I missing?
Answers
>> I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor).
>> Before I updated Hyper-V it used to report insufficient memory.
Have you tried to use performance monitor with counter «hyper-v dynamic memory balancer system balancer » to check if there is free memory larger than 4GB :
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
All replies
>> I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor).
>> Before I updated Hyper-V it used to report insufficient memory.
Have you tried to use performance monitor with counter «hyper-v dynamic memory balancer system balancer » to check if there is free memory larger than 4GB :
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
This happened to me just now. 12/7/17. I restored a Win 2012 R2 VM using DPM to a physical Windows 2012 R2 HV host like I always do. This time the VM would not start and I received error 32788 when I started the VM.
I forgot to assign the VM a network adapter in HV settings after it was restored but before starting it. I needed the VM it to have an internal network adapter in my case. Changed the VM NIC to an internal switch and VM started right up.
This is due a problem with the virtual switch
I have just had exactly the same issue on my machine, I had to create a new virtual switch and assign all of my virtual machines to this switch. Everything works fine now
This worked for me.
This can be a virtual memory issue also, so maybe check how much disk space is available on the disk where the VM files are stored (e.g. C: instead of D:).
restarting the host computer fixed it for me. I feel it was more likely caused by not enough free memory in my case, since I tried restarting two running services related to Hyper-V, which did not help.
But I really don’t understand what type of memory is not enough just looking at the performance tab of task manager, instead, the available memory on it was a little bit more then memory for my saved VM.
I get this error again today, my VM need 6000MB memory, the Available number on Task manager is 8G.
I tried Stop Service in Hyper-V manager, which does not fix.
Then, I closed Edge browser and JustDecompile, I see a memory usage drop in Task manager and I can start the VM after that.
Same issue on my side (starting with more than 4GB or RAM fails the start).
I guess there is some bug with hyper-v implementation.
this time, I use RAMMAP to help with troubleshoot, now my VM need 9000M memory. The first screenshot is what I get after clicked every item in Emty menu in RAMMAP. The second is what I get after restart computer. I wonder how can I get enough free memory without restart computer.
guess I need to first find out which process hold the large amount of modified memory which cannot be released by «Empty»
From the answers I understand this maybe a generic error that appears under several occasions.
In my case it was due to the available memory and in fact when I tried a second restart of the machine the error message was about the memory instead of the 32788.
I am running 2 linux VMs on a 16G PC each with 6G of RAM.
When I start the first one it shows that it occupies the 6G of RAM I set in settings.
During this time I cannot start the second virtual machine.
After some time the consumed memory drops at about 2G or maybe less, it seems the memory is allocated dynamically and released when not needen by the VM.
When this happens I can start the second VM and the run both quite happy.
Whenever they need more memory they are given memory and the usual memory consumption for each of the 2 VMs is about 4G.
So, all I have to do in order to start the second VM is to wait, for about 1 minute or so, the first to release some memory and then I start the second.
It is possible that if I change some settings of the VMs I wont have to wait at all, I ‘ll try it some time.
ΠΠΎΠ΄ ΠΎΡΠΈΠ±ΠΊΠΈ 32788 hyper v
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor). When I try to start it with more than 4GB of RAM it fails with this error. I tried creating a new VM, using a different VHD file, all create the same error. Before I updated Hyper-V it used to report insufficient memory. What am I missing?
Answers
>> I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor).
>> Before I updated Hyper-V it used to report insufficient memory.
Have you tried to use performance monitor with counter «hyper-v dynamic memory balancer system balancer » to check if there is free memory larger than 4GB :
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
All replies
>> I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor).
>> Before I updated Hyper-V it used to report insufficient memory.
Have you tried to use performance monitor with counter «hyper-v dynamic memory balancer system balancer » to check if there is free memory larger than 4GB :
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
This happened to me just now. 12/7/17. I restored a Win 2012 R2 VM using DPM to a physical Windows 2012 R2 HV host like I always do. This time the VM would not start and I received error 32788 when I started the VM.
I forgot to assign the VM a network adapter in HV settings after it was restored but before starting it. I needed the VM it to have an internal network adapter in my case. Changed the VM NIC to an internal switch and VM started right up.
This is due a problem with the virtual switch
I have just had exactly the same issue on my machine, I had to create a new virtual switch and assign all of my virtual machines to this switch. Everything works fine now
This worked for me.
This can be a virtual memory issue also, so maybe check how much disk space is available on the disk where the VM files are stored (e.g. C: instead of D:).
restarting the host computer fixed it for me. I feel it was more likely caused by not enough free memory in my case, since I tried restarting two running services related to Hyper-V, which did not help.
But I really don’t understand what type of memory is not enough just looking at the performance tab of task manager, instead, the available memory on it was a little bit more then memory for my saved VM.
I get this error again today, my VM need 6000MB memory, the Available number on Task manager is 8G.
I tried Stop Service in Hyper-V manager, which does not fix.
Then, I closed Edge browser and JustDecompile, I see a memory usage drop in Task manager and I can start the VM after that.
Same issue on my side (starting with more than 4GB or RAM fails the start).
I guess there is some bug with hyper-v implementation.
this time, I use RAMMAP to help with troubleshoot, now my VM need 9000M memory. The first screenshot is what I get after clicked every item in Emty menu in RAMMAP. The second is what I get after restart computer. I wonder how can I get enough free memory without restart computer.
guess I need to first find out which process hold the large amount of modified memory which cannot be released by «Empty»
From the answers I understand this maybe a generic error that appears under several occasions.
In my case it was due to the available memory and in fact when I tried a second restart of the machine the error message was about the memory instead of the 32788.
I am running 2 linux VMs on a 16G PC each with 6G of RAM.
When I start the first one it shows that it occupies the 6G of RAM I set in settings.
During this time I cannot start the second virtual machine.
After some time the consumed memory drops at about 2G or maybe less, it seems the memory is allocated dynamically and released when not needen by the VM.
When this happens I can start the second VM and the run both quite happy.
Whenever they need more memory they are given memory and the usual memory consumption for each of the 2 VMs is about 4G.
So, all I have to do in order to start the second VM is to wait, for about 1 minute or so, the first to release some memory and then I start the second.
It is possible that if I change some settings of the VMs I wont have to wait at all, I ‘ll try it some time.
ΠΠΎΠ΄ ΠΎΡΠΈΠ±ΠΊΠΈ 32788 hyper v
ΠΠΎΠΏΡΠΎΡ
I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor). When I try to start it with more than 4GB of RAM it fails with this error. I tried creating a new VM, using a different VHD file, all create the same error. Before I updated Hyper-V it used to report insufficient memory. What am I missing?
ΠΡΠ²Π΅ΡΡ
>> I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor).
>> Before I updated Hyper-V it used to report insufficient memory.
Have you tried to use performance monitor with counter «hyper-v dynamic memory balancer system balancer » to check if there is free memory larger than 4GB :
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
ΠΡΠ΅ ΠΎΡΠ²Π΅ΡΡ
>> I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor).
>> Before I updated Hyper-V it used to report insufficient memory.
Have you tried to use performance monitor with counter «hyper-v dynamic memory balancer system balancer » to check if there is free memory larger than 4GB :
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
This happened to me just now. 12/7/17. I restored a Win 2012 R2 VM using DPM to a physical Windows 2012 R2 HV host like I always do. This time the VM would not start and I received error 32788 when I started the VM.
I forgot to assign the VM a network adapter in HV settings after it was restored but before starting it. I needed the VM it to have an internal network adapter in my case. Changed the VM NIC to an internal switch and VM started right up.
This is due a problem with the virtual switch
I have just had exactly the same issue on my machine, I had to create a new virtual switch and assign all of my virtual machines to this switch. Everything works fine now
This worked for me.
This can be a virtual memory issue also, so maybe check how much disk space is available on the disk where the VM files are stored (e.g. C: instead of D:).
restarting the host computer fixed it for me. I feel it was more likely caused by not enough free memory in my case, since I tried restarting two running services related to Hyper-V, which did not help.
But I really don’t understand what type of memory is not enough just looking at the performance tab of task manager, instead, the available memory on it was a little bit more then memory for my saved VM.
I get this error again today, my VM need 6000MB memory, the Available number on Task manager is 8G.
I tried Stop Service in Hyper-V manager, which does not fix.
Then, I closed Edge browser and JustDecompile, I see a memory usage drop in Task manager and I can start the VM after that.
Same issue on my side (starting with more than 4GB or RAM fails the start).
I guess there is some bug with hyper-v implementation.
this time, I use RAMMAP to help with troubleshoot, now my VM need 9000M memory. The first screenshot is what I get after clicked every item in Emty menu in RAMMAP. The second is what I get after restart computer. I wonder how can I get enough free memory without restart computer.
guess I need to first find out which process hold the large amount of modified memory which cannot be released by «Empty»
From the answers I understand this maybe a generic error that appears under several occasions.
In my case it was due to the available memory and in fact when I tried a second restart of the machine the error message was about the memory instead of the 32788.
I am running 2 linux VMs on a 16G PC each with 6G of RAM.
When I start the first one it shows that it occupies the 6G of RAM I set in settings.
During this time I cannot start the second virtual machine.
After some time the consumed memory drops at about 2G or maybe less, it seems the memory is allocated dynamically and released when not needen by the VM.
When this happens I can start the second VM and the run both quite happy.
Whenever they need more memory they are given memory and the usual memory consumption for each of the 2 VMs is about 4G.
So, all I have to do in order to start the second VM is to wait, for about 1 minute or so, the first to release some memory and then I start the second.
It is possible that if I change some settings of the VMs I wont have to wait at all, I ‘ll try it some time.