> -----Original Message----- > From: Paolo Bonzini [mailto:paolo.bonzini@xxxxxxxxx] On Behalf Of Paolo > Bonzini > Sent: Thursday, May 30, 2013 5:27 AM > To: Ren, Yongjie > Cc: kvm@xxxxxxxxxxxxxxx > Subject: Re: KVM Test report, kernel e47a5f5f... qemu b5803aa3... > > Il 29/05/2013 10:12, Ren, Yongjie ha scritto: > > Hi All, > > > > This is KVM upstream test result against kvm.git next branch and > qemu-kvm.git uq/master branch. > > kvm.git next branch: > e47a5f5fb715b90b40747e9e235de557c6abd56c based on kernel > 3.10.0-rc1 > > qemu-kvm.git uq/master branch: > b5803aa3583e82e5133f7621121bc15ee694f4a1 > > > > We found 5 new bugs and verified 1 fixed bug this month. > > We also closed a bug as invalid because it's a known issue that some > Windows version is not supported for I350 NIC. > > > > New issues (5): > > 1. guest cannot boot up when Intel 82572 NIC assigned > > https://bugs.launchpad.net/qemu/+bug/1182716 > > -- this may already been fixed in qemu.git tree but it still exists in > qemu-kvm.git uq/master branch. > > > > 2. with 'monitor pty', it needs to flush pts device after sending command > to it > > https://bugs.launchpad.net/qemu/+bug/1185228 > > > > 3. [nested virt] L2 Windows guest can't boot up ('-cpu host' to start L1) > > https://bugzilla.kernel.org/show_bug.cgi?id=58921 > > > > 4. SMP x64 Windows 2003 guest can't boot up > > https://bugzilla.kernel.org/show_bug.cgi?id=58931 > > Can you reproduce this with "modprobe kvm_intel > emulate_invalid_guest_state=0"? > Yes. This bug still exists with "modprobe kvm_intel emulate_invalid_guest_state=0". The VNC console of a SMP x64 Window 2003 guest is always blank (nothing is displayed). But UP (1 vCPU) Windows 2003 guest can work fine. Best regards, Jay > Thanks, > > Paolo > > > 5. [nested virt] L2 has NMI error when creating L1 with "-cpu host" > parameter > > https://bugzilla.kernel.org/show_bug.cgi?id=58941 > > -- this may have some relationship with the above bug #58921. -- 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
