Virtual server troubleshooting
This section provides information about problems and workarounds related to virtual servers.
- Virtual server relocation fails in a mixed management environment
This problem might occur when a host system is being managed by two IBM® Flex System Manager servers. - Incorrect information displayed for Hyper-V virtual servers
This problem affects the Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2 virtual servers, when operations are performed on the virtual servers by using the vendor software rather than by using IBM Flex System Manager VMControl. - Event filters that use extended details to monitor the creation of a virtual server
This problem can affect any virtualization environment. - Incorrect power state displayed for Hyper-V virtual servers
This problem affects the Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2 virtual servers, when power operations are performed on the virtual servers by using the vendor software rather than by using IBM Flex System Manager. - Virtual server devices are missing
This problem can affect virtual servers that are managed by IBM Flex System Manager. - Virtual server power operations behave unexpectedly
This problem affects virtual server power operations in a VMware vCenter environment. - Unable to relocate virtual servers that are managed by the Hardware Management Console
This problem affects the relocation of virtual servers that are managed by the Hardware Management Console (HMC). - Unable to recover LPAR after a remotely restarted virtual server fails
This problem deals with recovering a virtual server when a virtual server that is remotely restarted fails. - Unable to power on a KVM virtual server that uses an IBM Flex System Manager Network Control VEPA logical network
This problem affects powering on a KVM virtual server after deploying a virtual appliance. - Problems when using a non-default partition profile
This problem affects Power Systems™ with virtual servers in the IBM Flex System Manager VMControl environment. - WorkloadInstance relationship with virtual server might be impacted if out-of-band actions are taken on the virtual server
When a WorkloadInstance is created, the IBM Flex System Manager along with VMControl must manage its virtual server. This is especially important when relocating the virtual server or assigning it to maintenance mode. Because of this management dependency, before performing any out-of-band actions on the virtual server, make sure that you remove the related WorkloadInstance. If any out-of-band actions are taken on the virtual server and you have not removed the WorkloadInstance, the WorkloadInstance might lose its integrity, its relationship with the virtual server might be lost and the WorkloadInstance might be deleted. - Unable to delete virtual server service partition
A virtual server must have the service mode set to Unassigned before you can delete a service partition on the virtual server. - Unable to locate virtual disk
This problem affects virtual disks that are associated with hosts that are managed by VMware vCenter. The virtual disks were created through VMControl. - Host definitions on storage not deleted when deleting virtual server
This problem affects the Permanently Delete Virtual Server task when it is targeted to a virtual server with NPIV-attached disk. - Unable to permanently delete a virtual server
Inventory must be up to date before you can permanently delete a virtual server. - Unable to power on a Hyper-V virtual server on a computer that is running Windows 2008 Release 2
You are unable to power on a Hyper-V virtual server on a computer that is running Microsoft Windows 2008 Release 2 on which a CPU that supports the Advanced Vector Extensions (AVX) feature is installed. - Unable to view details of active problems for workloads
On VMControl > Workloads tab, you are unable to view the problem details for workloads.
Parent topic: Troubleshooting and support