| FPU context can't be restored. The processor is incompatible. [message #48796] |
Wed, 05 December 2012 01:17  |
wetpaste
Messages: 1
Registered: December 2012
|
Junior Member |
|
|
Hi all,
I've been trying out the live migration abilities of openvz and I ran into an interesting error in which google has not been helpful.
[root@HN .ssh]# vzmigrate -r no --online -v 10.1.1.105 1
Starting live migration of CT 1 to 10.1.1.105
OpenVZ is running...
Loading /etc/vz/vz.conf and /etc/vz/conf/1.conf files
Check IPs on destination node: 10.1.1.103 10.1.1.15
Preparing remote node
Copying config file
1.conf 100% 1335 1.3KB/s 00:00
No changes in CT configuration, not saving
Creating remote container root dir
Creating remote container private dir
Syncing private
Live migrating container...
Suspending container
Setting up checkpoint...
suspend...
get context...
Checkpointing completed successfully
Dumping container
Setting up checkpoint...
join context..
dump...
Checkpointing completed successfully
Copying dumpfile
dump.1 100% 177MB 29.4MB/s 00:06
Syncing private (2nd pass)
Undumping container
Restoring container ...
Container is mounted
undump...
Adding IP address(es): 10.1.1.103 10.1.1.15
Setting CPU units: 1000
Error: undump failed: Bad address
Restoring failed:
Error: FPU context can't be restored. The processor is incompatible.
Container restore failed
Container is unmounted
Error: Failed to undump container
Resuming...
Both source and destination machines are already running containers without issue. At least the site is still live, just not migrated.
The source kernel is: 2.6.32-042stab062.2
Dest: 2.6.32-042stab063.2
Any idea what the issue could be? It looks like the CPU checkpointing is not working on one of the machines, maybe some instruction is being used on the newer machine, is being checkpointed, and cannot be interpreted by the old machine? Is that common?
Source: Intel(R) Xeon(R) CPU E5-2430L
Dest: Intel(R) Xeon(R) CPU 3040
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
