Hi All, This is KVM upstream test result against kvm.git next branch and qemu.git master branch. kvm.git next branch: 7cbb39d4d4d530dff12f2ff06ed6c85c504ba91a based on kernel 3.14.0 qemu.git master branch: 5913815a17387a5e9825c734ccab760588471ee5 We found two new bugs and two fix bugs in the past three weeks. We closed a bug with invalid New issues (2): 1. KVM create a win7 guest with Qemu, it boots up fail. https://bugs.launchpad.net/qemu/+bug/1297651 2. Nested Virtualization,L2 cannot boot up on Ivybridge and Haswell. https://bugzilla.kernel.org/show_bug.cgi?id=73331 Fixed issues (2): 1. Host call trace when create guest. https://bugzilla.kernel.org/show_bug.cgi?id=71521 2. KVM create a win7 guest with Qemu, it boots up fail. https://bugs.launchpad.net/qemu/+bug/1297651 closed issue with invalid(1): 1. save guest running time is more than 450s with AVX running. https://bugs.launchpad.net/qemu/+bug/1261268 Old issues (7): ---------------------------------------------------------------------------------------------------------- 1. guest panic with parameter "-cpu host" in qemu command line (about vPMU issue). https://bugs.launchpad.net/qemu/+bug/994378 2. Nested Virt: VMX can't be initialized in L1 Xen ("Xen on KVM") https://bugzilla.kernel.org/show_bug.cgi?id=45931 3. Guest hang when doing kernel build and writing data in guest. https://bugs.launchpad.net/qemu/+bug/1096814 4. with 'monitor pty', it needs to flush pts device after sending command to it https://bugs.launchpad.net/qemu/+bug/1185228 5. [Nested] Windows XP Mode can not work https://bugzilla.kernel.org/show_bug.cgi?id=60782 6. [Nested]L2 guest failed to start in VMware on KVM https://bugzilla.kernel.org/show_bug.cgi?id=61411 7. [Nested]L1 call trace when create windows 7 guest as L2 guest https://bugzilla.kernel.org/show_bug.cgi?id=72381 Test environment: ================================================================== Platform IvyBridge-EP Sandybridge-EP Haswell-EP CPU Cores 32 32 56 Memory size 64GB 32GB 32GB Best Regards, Robert Ho -- 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