Does it also fail the other way round (host2 -> host1)? If not, your
issue is likely fixed with 23102:1c7b601b1b35 on 4.1-testing (and
with you posting on xen-devel rather than xen-users I would really
have expected that you would have looked for similar reports or
eventual fixes before complaining).
It did happen host2->host1 and host1->host2 with xen4.1.1-
I did set up 2 servers with identical hardware now and in fact i dont
have any problems with them migrating machines.
I went on to upgrade all 3 servers (2x 32gb 1x96gb) to xen-4.1-testing.
Now i can migrate 32gbhost->32gbhost and 32gbhost->96gbhost but
96gbhost->32gbhost still fails.
BUG: unable to handle kernel paging request at fffffffffffffff8
with 2.6.39 and 3.1 guest kernels, 3.0 didnt produce any output on its
tty0 anymore.
This issue may be a little more then a memory size mismatch, since i
have 3 servers running xen4.2 with 96gb ram two Dell R610s and one R710,
where the R610s can migrate guests between each other just fine.
They can also migrate to the R710 and back.
But a host created on the R710 cant be migrated to a R610.
The same exact thing happens with 4.1-testing.
A guest created on a 32gb host can be migrated to the 96gb host and back
to any 32gb host.
But a guest created on the 96gb host can not be migrated to a 32gb host.
Here is my server list:
host1: Dell PE2950 32GB RAM 4.1.1/4.1-testing/4.2 available for testing
host2: Dell PE2950 32GB RAM 4.1.1/4.1-testing/4.2 available for testing
host3: Dell R710 96B RAM 4.1.1/4.1-testing/4.2 available for testing
host4: Dell R610 96B RAM xen4.2
host4: Dell R610 96B RAM xen4.2
--
Andreas Olsowski
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|