© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Here's an interesting addition to this problem:
In my cluster, one system is based on a core2duo CPU, while the other is based on an i7 920 CPU. When the VM is originally started on the i7, migration doesn't work. When it's originally started on the core2, it does. From this, I'm guessing that the VM tries to use more CPU features available on the newer CPU when starting, and then when it tries to migrate to the older CPU some of those instructions fail, and that causes the lock ups I've been seeing.
I imagine this is also why this hasn't been reported a ton, since for people with matched systems they wouldn't see the problem.
Can anyone else still experiencing this confirm / deny mismatched CPUs?