From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: 'Konrad Rzeszutek Wilk' <konrad.wilk@oracle.com>,
'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-rc3 test result
Date: Fri, 31 Aug 2012 13:24:11 -0400 [thread overview]
Message-ID: <20120831172410.GA19756@localhost.localdomain> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A1018AF31@SHSMSX101.ccr.corp.intel.com>
On Fri, Aug 31, 2012 at 07:27:51AM +0000, Ren, Yongjie wrote:
> Hi All,
> We did a round testing for Xen 4.2 RC3 (CS# 25784) with Linux 3.5.2 dom0.
> We found no new issue, and verified 1 fixed bug.
>
> Fixed bug (1):
> 1. long stop during the guest boot process with qcow image
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
> -- Fixed by reverting a bad commit about "O_DIRECT to open IDE block device".
>
> The following are some of the old issues which we guess are something important.
> Some of the old issues:
> 1. Fail to probe NIC driver to HVM domU (with 3.5/3.6 Linux as Dom0)
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1824
> -- We already know the corrupt commit in Linux tree. Konrad will try to fix it.
> 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
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
Um, so you are assigning the same VF to two guests. I am surprised that
the tools even allowed you to do that. Was 'xm' allowing you to do that?
> 6. Guest hang after resuming from S3
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1828
Jan posted some patches to fix that. Can you test with an up-to-date
guest? (so not RHEL6U1 which does not have the fix).
> 7. Dom0 S3 resume fails
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
Yeah, that one is mine. Have some patches for that I will post soonish.
>
> Best Regards,
> Yongjie (Jay)
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2012-08-31 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 7:27 Xen4.2-rc3 test result Ren, Yongjie
2012-08-31 15:18 ` Ian Campbell
2012-09-06 5:59 ` Ren, Yongjie
2012-09-06 7:31 ` Ian Campbell
2012-09-06 11:08 ` Konrad Rzeszutek Wilk
2012-08-31 17:24 ` Konrad Rzeszutek Wilk [this message]
2012-09-03 7:45 ` Jan Beulich
2012-09-03 10:18 ` Konrad Rzeszutek Wilk
2012-09-06 8:18 ` Ren, Yongjie
2012-09-06 8:28 ` Ian Campbell
2012-09-07 1:58 ` Ren, Yongjie
2012-09-06 11:11 ` Konrad Rzeszutek Wilk
2012-09-07 8:01 ` Ren, Yongjie
2012-09-07 13:55 ` Konrad Rzeszutek Wilk
2012-09-25 5:57 ` Ren, Yongjie
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=20120831172410.GA19756@localhost.localdomain \
--to=konrad@kernel.org \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--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).