VM Live Migration Fails from Server with Lower microcode_ctl version to Server with Higher microcode_ctl version
Last updated on APRIL 08, 2018
Applies to:Oracle VM - Version 3.4.4 to 3.4.4 [Release OVM34]
Information in this document applies to any platform.
Live migration of a guest fails from a non-upgraded server to an upgraded server but live migration in the other direction is working fine and migration of a non-running guest is fine in both directions.
We see in the file /var/log/xend.log on the target server: xc: error: error setting the HVM context (1 = Operation not permitted)
The source server has microcode_ctl-1.17-126.96.36.199.el6_9.x86_64 installed.
The target (updated) server has microcode_ctl-1.17-188.8.131.52.el6_9.x86_64 or microcode_ctl-1.17-184.108.40.206.el6_9.x86_64 or microcode_ctl-1.17-220.127.116.11.el6_9.x86_64 installed.
This can be checked with the command:
This shows for example (depending on the cpu model):
On the source server: microcode : 0x42a
On the target server : microcode : 0x428
This shows the microcode version on the upgraded target server is lower than on the source server.
Target server has been updated and a new microcode_ctl package was installed.
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