код ошибки 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.

Источник