On 08/05/2009 05:23 AM, Xu, Jiajun wrote:
Hi All, There has been a long time we did not send out KVM testing resport. We will restart our biweekly report sending from this week. This Weekly KVM Testing Report against lastest kvm.git
Thanks, that's helpful.
0b972aaabb95808397c61483bd061f4e9ed10e11 and qemu-kvm.git f2593a0bf33ed609d87ad029ff003f1d50afb65e. There are two new bugs in lastest commit, one is for migration and another is vt-d issue after migration. Two New Issues: ================================================ 1. Guest will be no response after migration https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2832401&group_id=180599
What kind of guest is this?
Seven Old Issues: ================================================ 1. ltp diotest running time is 2.54 times than before https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
Most likely due to qcow2 switching to write through (from write back). Write back is faster but is unsafe.
4. failure to migrate guests with more than 4GB of RAM https://sourceforge.net/tracker/index.php?func=detail&aid=1971512&group_id=180599&atid=893831
Can you retest this? I was able to migrate a 6GB smp guest without problems.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
