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:24446 & Dom0: 20a27c1e...
Date: Thu, 29 Dec 2011 12:32:08 -0500 [thread overview]
Message-ID: <20111229173208.GA18032@phenom.dumpdata.com> (raw)
In-Reply-To: <40352EBA8B4DF841A9907B883F22B59BDD99@SHSMSX102.ccr.corp.intel.com>
On Thu, Dec 29, 2011 at 08:42:17AM +0000, Zhou, Chao wrote:
> Hi all,
>
> This is the test report of xen-unstable tree. There is one issue which has existed in xen upstream since CS #22415 but was found recently.
> After we hotplug a VF or NIC to guest for several times(about 10 times) the guest can't get ip address. The old CS #22402 doesn't have this issue, but it exists in latest xen upstream.
>
>
> Version Info
> =================================================================
> xen-changeset: 24446:2863b2f43a3b
> pvops git: Jeremy's tree
> commit 20a27c1e25b8550066902c9d6ca91631e656dfa3
When are you guys planning to switch to the upstream kernel?
> =================================================================
>
> New issue(1)
> ==============
> 1. VF doesn't work after hot-plug for many times
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1798
>
>
> Old issues(6)
> ==============
> 1. [ACPI] System cann't resume after do suspend
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1707
> 2.[XL]"xl vcpu-set" causes dom0 crash or panic
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1730
> 3.[VT-D]fail to detach NIC from guest
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1736
> 4.Dom0 crash on power-off
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1740
> 5.Sometimes Xen panic on ia32pae Sandybridge when restore guest
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1747
> 6.[VT-D] device reset fail when create/destroy guest
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1752
>
>
>
>
> Thanks,
> Zhou, Chao
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-12-29 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 8:42 VMX status report. Xen:24446 & Dom0: 20a27c1e Zhou, Chao
2011-12-29 17:32 ` Konrad Rzeszutek Wilk [this message]
2012-01-03 17:20 ` Konrad Rzeszutek Wilk
2012-01-04 1:04 ` Ren, Yongjie
2012-01-02 8:33 ` Jan Beulich
2012-01-04 6:00 ` 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=20111229173208.GA18032@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 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).