All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Zhou, Chao" <chao.zhou@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: VMX status report. Xen:24911 & Dom0: d93dc5c4...
Date: Tue, 13 Mar 2012 12:55:16 -0400	[thread overview]
Message-ID: <20120313165516.GG19228@phenom.dumpdata.com> (raw)
In-Reply-To: <40352EBA8B4DF841A9907B883F22B59B0FCC58DE@SHSMSX102.ccr.corp.intel.com>

On Tue, Mar 13, 2012 at 09:18:27AM +0000, Zhou, Chao wrote:
> Hi all,
> 
> This is the test report of xen-unstable tree. We've switched our Dom0 to upstream Linux 3.1-rc7 instead of Jeremy's 2.6.32.x tree.

Nice! Thanks for doing that. Thought some of the issues reported below I think
are fixed in 3.3.. Especially the 'xl vcpu-set' one - which I think is also
back-ported to the 3.x stable kernel.

> We've also upgraded our nightly test system from RHEL5.5 to RHEL6.2.
> We found four new issues and one old issue got fixed.
> 
> Version Info
> =================================================================
> xen-changeset:  24911:d7fe4cd831a0
> Dom0: linux.git  3.1-rc7 (commit: d93dc5c4...)
> =================================================================
> 
> 
> New issues(4)
> ==============
> 1. when detaching a VF from hvm guest, "xl dmesg" will show some warning information
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1809
> 2. Dom0 hang when bootup a guest with a VF(the guest has been bootup with a different VF before)
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1810
> 3. RHEL6.2/6.1 guest runs quite slow
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1811
> 4. after detaching a VF from a guest, shutdown the guest is very slow
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> 
> Fixed issue(1)
> ==============
> 1. Dom0 crash on power-off
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1740
>     ----kernel3.1.0 doesn't have this issue now
> 
> Old issues(5)

These old ones are with 3.1.x?
> ==============
> 1. [ACPI] System cann't resume after do suspend
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> 2. [XL]"xl vcpu-set" causes dom0 crash or panic
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> 3. [VT-D]fail to detach NIC from guest
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
> 4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> 5. [VT-D] device reset fail when create/destroy guest
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
> 
> 
> Thanks
> Zhou, Chao
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2012-03-13 16:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13  9:18 VMX status report. Xen:24911 & Dom0: d93dc5c4 Zhou, Chao
2012-03-13 11:33 ` Jan Beulich
2012-03-14  6:08   ` Ren, Yongjie
2012-03-15 10:12     ` Jan Beulich
2012-03-21 11:07       ` Ping: " Jan Beulich
2012-03-22 10:59         ` Stefano Stabellini
2012-03-23  9:33     ` Jan Beulich
2012-03-26  7:06       ` Ren, Yongjie
2012-03-13 15:38 ` VMX status report. Xen:24911 & Dom0: d93dc5c4... Nested VMX testing? Pasi Kärkkäinen
2012-03-14  8:00   ` Ren, Yongjie
2012-03-14 11:21     ` Pasi Kärkkäinen
2012-06-19 20:44     ` Pasi Kärkkäinen
2012-06-20  5:46       ` Ren, Yongjie
2012-03-13 16:55 ` Konrad Rzeszutek Wilk [this message]
2012-03-14  8:54   ` VMX status report. Xen:24911 & Dom0: d93dc5c4 Ren, Yongjie
2012-03-14 21:37     ` Konrad Rzeszutek Wilk

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=20120313165516.GG19228@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=chao.zhou@intel.com \
    --cc=xen-devel@lists.xensource.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 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.