All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hu, Robert" <robert.hu@intel.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "Zhou, Chao" <chao.zhou@intel.com>
Subject: VMX test report for Xen 4.5-unstable-C/S 28634
Date: Mon, 31 Mar 2014 08:52:54 +0000	[thread overview]
Message-ID: <9E79D1C9A97CFD4097BCE431828FDD318C5B76@SHSMSX103.ccr.corp.intel.com> (raw)

Hi All,
This is a report based on our testing for Xen 4.5-unstable on Intel platforms.
Test environment:
Xen: Xen 4.5-unstable with qemu-upstream-unstable.git
Changeset: 28634:b75cbf39ebe4
Dom0: Linux kernel 3.13.7
Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell

Newly-and-Open bugs (0): 

Reopened bug(1)
1. Guest hang after resume from S3
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1828

Fixed bugs (12):
1. 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
2. [upstream qemu]'maxvcpus=NUM' item is not supported in upstream QEMU
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1837
3. [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
4. [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
5. 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
6. device pass-through works even if VT-d is disabled in BIOS
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1866
7. Dom0 will panic when passthrough igb/ixgbe device to HVM guest
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1873
8. Win8 guest boot up failed on SNB-EP when setting 'hpet=0' in HVM guest configuration file
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1874
9. VT-D/SRIOV cannot work fine on rhel6u4 guest with more than 1 vcpu
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1875
10. Dom0's CPU offline leads Dom0 panic
  http://bugzilla-archived.xenproject.org/bugzilla/show_bug.cgi?id=1876
11. windows 2008 R2 guest with VF cannot get IP
  http://bugzilla-archived.xenproject.org/bugzilla/show_bug.cgi?id=1879
12. "xl vcpu-set " fail to add guest vcpu number
  http://bugzilla-archived.xenproject.org/bugzilla/show_bug.cgi?id=1882

Closed invalid bug(1)
1. "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

Old bugs (6):
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. [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
4. sometimes failed to online cpu in Dom0
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
5. Booting multiple guests will lead Dom0 call trace
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853
6. After live migration, guest console continuously prints "Clocksource tsc unstable"
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1854


Best Regards,
Robert Ho

             reply	other threads:[~2014-03-31  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31  8:52 Hu, Robert [this message]
2014-08-04 14:00 ` VMX test report for Xen 4.5-unstable-C/S 28634 Konrad Rzeszutek Wilk
2014-08-06  7:57   ` Hu, Robert
2014-08-08 18:22     ` Konrad Rzeszutek Wilk
2014-08-08 18:45       ` Processed: " xen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9E79D1C9A97CFD4097BCE431828FDD318C5B76@SHSMSX103.ccr.corp.intel.com \
    --to=robert.hu@intel.com \
    --cc=chao.zhou@intel.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.