[Xen-devel] VMX test report for Xen 4.4-unstable-C/S 27314

["Ren, Yongjie" <yongjie.ren@xxxxxxxxx>]

Hi All,
This is a report based on our testing for Xen 4.4-unstable on Intel platforms.
Test environment:
Xen: Xen 4.4-unstable with qemu-upstream-unstable.git
Changeset: 27314:e6ca87e13937
Dom0: Linux kernel 3.10.5
Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell systems

New bugs (3): 
1. Large file remote copy in Windows guest (no GPL PV driver) cause networking 
broken
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1862
2. device pass-through works even if VT-d is disabled in BIOS
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1866
3. "xl list" shows no guest vcpu status when setting maxcpus=1 in hypervisor 
grub line
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1867

Fixed bugs (7):
1. [ACPI] Dom0 can't resume from S3 sleep
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1707
2. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1822
3. Live migration fail when migrating the same guest for more than 2 times
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1845
4. dom0 call trace when running sriov hvm guest with igbvf
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1852
5. Guest could't find bootable device with memory more than 3600M
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1857
6.changing vCPU number of a HVM for several times will cause the guest panic
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1860
7. dom0 will panic when pcibacking a vt-d device on IVT-EP
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1868

Closed bug (1):
1. Sometimes Xen panic on ia32pae Sandybridge when restore guest
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1747
  -- no need to track this.

Old bugs (11):
1. [XL]"xl vcpu-set" causes dom0 crash or panic
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1730
2. Dom0 cannot be shutdown before PCI device detachment from guest
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1826
3. Guest hang after resume from S3
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1828
4. xl pci-list shows one PCI device (PF or VF) could be assigned to two 
different guests
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1834
5. [upstream qemu] Guest free memory with upstream qemu is 14MB lower than that 
with qemu-xen-unstable.git
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1836
6. [upstream qemu]'maxvcpus=NUM' item is not supported in upstream QEMU
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1837
7. [upstream qemu] Guest console hangs after save/restore or live-migration 
when setting 'hpet=0' in guest config file
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1838
8. [upstream qemu] 'xen_platform_pci=0' setting cannot make the guest use 
emulated PCI devices by default
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1839
9. sometimes failed to online cpu in Dom0
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
10. Booting multiple guests will lead Dom0 call trace
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853
11. After live migration, guest console continuously prints "Clocksource tsc 
unstable"
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854

Best Regards,
     Yongjie (Jay)


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel