Last updated on DECEMBER 09, 2016
Applies to:Oracle VM - Version 3.2.8 to 3.2.11 [Release OVM32]
Information in this document applies to any platform.
The xend daemon becomes unresponsive, commands such as xm list or xm info will hang. Also, processes like the OVS Agent cannot gather information from xend either, preventing normal VM operations such as starting or rebooting. Disk and network I/O performance are severely degraded.
In this example, the following is illustrated:
1) VM OL5U9-1 is migrated to target host ovs10r1 from ovs12r1
2) Shutdown of VM OL5U9-0 on the same server ovs10r1 where the migration already running and wait for 20 seconds.
3) After the 20-second delay, migration of the second VM to target host ovs10r1 from ovs12r1 is attempted: VM OL5U6-2 on target host ovs10r1.
The xend daemon becomes stuck using 100% CPU or more on both Dom0. At this point, the xend daemon is unresponsive to any xm(8) commands.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms