From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen4.2-rc1 test result
Date: Mon, 6 Aug 2012 11:31:24 -0400 [thread overview]
Message-ID: <20120806153124.GF8967@phenom.dumpdata.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A1013D698@SHSMSX101.ccr.corp.intel.com>
On Mon, Aug 06, 2012 at 02:34:35PM +0000, Ren, Yongjie wrote:
> Hi All,
> We did a round testing for Xen 4.2 RC1 (CS#25692) with Linux 3.4.7 dom0.
> We covered VT-d, SR-IOV, Power Management, TXT, IVB new features, HSW new features.
> We covered many cases for HVM guests (both Redhat Linux and MS Windows guest).
> We tested on Westmere-EP, SandyBridge-EP, IvyBridge desktop, and Haswell hardware platforms.
> We found no new issues, and verified 1 fixed bug.
Cool!
>
> Fixed bug (1):
> 1. parameter 'maxvcpus' causes hvm guest boots up with wrong vcpu number
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1825
> -- Fixed by Yang from Intel.
>
> The following are some of the old issues which we guess are something important.
> Some of the old issues:
> 1. long stop during the guest boot process (too slow bootup)
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
> 2. Poor performance when do guest save/restore and migration with linux 3.x dom0
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1784
> 3. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> 4. after detaching a VF from a guest, shutdown the guest is very slow
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> 5. Dom0 cannot be shutdown before PCI detachment from guest and when pci assignment conflicts
> (xl allows same PCI device to be assigned to multiple guests)
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
> 6. Guest hang after resuming from S3
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1828
So those that are Linux related are going to have to wait. I am ..swamped.
The merge window just closed and its time to deal with regressions. Is there
way for Intel engineers in helping to come up with a patch for some of
these issues?
prev parent reply other threads:[~2012-08-06 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 14:34 Xen4.2-rc1 test result Ren, Yongjie
2012-08-06 15:31 ` Konrad Rzeszutek Wilk [this message]
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=20120806153124.GF8967@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=yongjie.ren@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).