On 08/21/2009 10:14 AM, Xu, Jiajun wrote:
I found the migration failure is caused by a configuration mistake on our
testing machine. Now 64-bit migration works well.
But I found on PAE host, migration will cause host kernel call trace.
Pid: 12053, comm: qemu-system-x86 Tainted: G
On Wednesday, August 19, 2009 4:09 PM Avi Kivity wrote:
On 08/19/2009 05:14 AM, Xu, Jiajun wrote:
I tried this with latest commit, sometimes linux guest can
do migration with more than 4G memory.
But sometimes I found guest will hang after migration and on
host console it will print Unknown
On Monday, August 17, 2009 8:18 PM Avi Kivity wrote:
On 08/17/2009 04:32 AM, Xu, Jiajun wrote:
5. failure to migrate guests with more than 4GB of RAM
https://sourceforge.net/tracker/index.php?func=detailaid=19715
12group_id=180599atid=893831
Now that I have a large host, I tested this,
On 08/17/2009 04:32 AM, Xu, Jiajun wrote:
5. failure to migrate guests with more than 4GB of RAM
https://sourceforge.net/tracker/index.php?func=detailaid=1971512group_id=180599atid=893831
Now that I have a large host, I tested this, and it works well. When
was this most recently tested?
