KVM Test report, kernel e47a5f5f... qemu b5803aa3...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

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.

Fixed issue (1):
1. [nested virt] L1 CPU Stuck when booting a L2 guest
  https://bugzilla.kernel.org/show_bug.cgi?id=56971

Closed issue with invalid(1):
1. [SR-IOV] Intel I350 NIC VF cannot work in a Windows 2008 guest.
  https://bugzilla.kernel.org/show_bug.cgi?id=56981
  -- Intel driver team said I350 is supported in Win2k8 R2 version (not supported Win2k8).

Old issues (6):
----------------------------------------------------------------------------------------------------------
1. guest panic with parameter "-cpu host" in qemu command line (about vPMU issue).
  https://bugs.launchpad.net/qemu/+bug/994378
2. Can't install or boot up 32bit win8 guest.
  https://bugs.launchpad.net/qemu/+bug/1007269
3. vCPU hot-add makes the guest abort. 
  https://bugs.launchpad.net/qemu/+bug/1019179
4. Nested Virt: VMX can't be initialized in L1 Xen ("Xen on KVM")
  https://bugzilla.kernel.org/show_bug.cgi?id=45931
5. Guest has no "xsave" feature with parameter "-cpu qemu64,+xsave" in qemu command line.
  https://bugs.launchpad.net/qemu/+bug/1042561
6. Guest hang when doing kernel build and writing data in guest.
  https://bugs.launchpad.net/qemu/+bug/1096814


Test environment:
==================================================================
  Platform                   IvyBridge-EP        Sandybridge-EP
  CPU Cores                   32                32
  Memory size                 64GB              32GB


Regards
  Yongjie Ren  (Jay)

--
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




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux