Why saving network configuration of hypervisors causes host to go non responsive followed by migration of VMs
Issue
- Changing any network configuration of the host causes host to go non responsive. This only happens if
save network configurationis checked. - Saving a network configuration of the host from RHEV-M which contains large number of vlans is taking much time in RHEV hypervisor compared to RHEL hypervisor.
Environment
- Red Hat Enterprise Virtualization 3.6
- RHEV-H hypervisor
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
