xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "Liu, SongtaoX" <songtaox.liu@intel.com>,
	"Liu, RongrongX" <rongrongx.liu@intel.com>,
	"Wu, GabrielX" <gabrielx.wu@intel.com>,
	"Zhou, Chao" <chao.zhou@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: VMX status report. Xen:26127 & Dom0:3.6.5
Date: Wed, 2 Jan 2013 16:41:53 -0500	[thread overview]
Message-ID: <20130102214153.GC15833@phenom.dumpdata.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A1023ADFF@SHSMSX101.ccr.corp.intel.com>

On Mon, Dec 31, 2012 at 02:22:25AM +0000, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Saturday, December 22, 2012 5:28 AM
> > To: Wu, GabrielX
> > Cc: xen-devel@lists.xen.org; Ren, Yongjie; Liu, RongrongX; Liu, SongtaoX;
> > Zhou, Chao
> > Subject: Re: [Xen-devel] VMX status report. Xen:26127 & Dom0:3.6.5
> > 
> > On Mon, Nov 12, 2012 at 02:16:44AM +0000, Wu, GabrielX wrote:
> > > Hi all,
> > >
> > > This is the test report of xen-unstable tree, no new issue found and no
> > issue fixed.
> > >
> > > Version Info:
> > >
> > ============================================================
> > =====
> > > xen-changeset:   26127:bd78e5630a5b
> > > Dom0:          linux.git  3.6.5
> > >
> > ============================================================
> > =====
> > >
> > > New issue(0)
> > > ==============
> > >
> > > Fixed issue(0)
> > > ==============
> > >
> > > Old issues(9)
> > > ==============
> > > 1. [ACPI] Dom0 can't resume from S3 sleep
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > 
> > This should be fixed in v3.8.
> > 
> Fixes are already in Linus' linux.git tree, or not ?
> We did a test with that tree, and found there's no crash now, but dom0 vCPU increase didn't work.

Yup. Looks like I have a very old VMX status report. Sorry about that.

> 
> > >   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. after detaching a VF from a guest, shutdown the guest is very slow
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> > > 6. Poor performance when do guest save/restore and migration with
> > linux 3.x dom0
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1784
> > 
> > And this one as well.
> Yes, there should be no performance loss now for migration case.
> We already marked this bug as 'fixed' with kernel 3.6.7 Dom0.
> 
> > > 7. 'xl vcpu-set' can't decrease the vCPU number of a HVM guest
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
> > 
> > And this one too.
> > > 8. Dom0 cannot be shutdown before PCI device detachment from guest
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
> > 
> > > 9. xl pci-list shows one PCI device (PF or VF) could be assigned to two
> > different guests
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1834
> > >
> > > Best Regards,
> > > Ronghui Wu(Gabriel)
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xen.org
> > > http://lists.xen.org/xen-devel
> > >

      reply	other threads:[~2013-01-02 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12  2:16 VMX status report. Xen:26127 & Dom0:3.6.5 Wu, GabrielX
2012-12-21 21:27 ` Konrad Rzeszutek Wilk
2012-12-31  2:22   ` Ren, Yongjie
2013-01-02 21:41     ` 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=20130102214153.GC15833@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=chao.zhou@intel.com \
    --cc=gabrielx.wu@intel.com \
    --cc=rongrongx.liu@intel.com \
    --cc=songtaox.liu@intel.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).