All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Hu, Robert" <robert.hu@intel.com>
Cc: "Zhou, Chao" <chao.zhou@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: VMX test report for Xen 4.5-unstable-C/S 28634
Date: Mon, 4 Aug 2014 10:00:27 -0400	[thread overview]
Message-ID: <20140804140027.GA18425@laptop.dumpdata.com> (raw)
In-Reply-To: <9E79D1C9A97CFD4097BCE431828FDD318C5B76@SHSMSX103.ccr.corp.intel.com>

On Mon, Mar 31, 2014 at 08:52:54AM +0000, Hu, Robert wrote:
> Hi All,
> This is a report based on our testing for Xen 4.5-unstable on Intel platforms.
> Test environment:
> Xen: Xen 4.5-unstable with qemu-upstream-unstable.git
> Changeset: 28634:b75cbf39ebe4
> Dom0: Linux kernel 3.13.7
> Hardware: Intel Sandy Bridge, Ivy Bridge, Haswell
> 
> Newly-and-Open bugs (0): 
> 
> Reopened bug(1)
> 1. Guest hang after resume from S3
>   http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1828

Hey Hu,

Considering that Liu is no long working for Intel and in the past he
had been working on this bug:
 - Is there somebody else from Intel who is looking at this?
 - Is this still an issue? (It looks like yes - as you have to compile the guest
   without CONFIG_XEN_PVHVM? - but that implies a Linux issue not
   hypervisor - btw in 3.17 there will be an 'xen_nopv' bootline parameter
   that will disable the PV drivers/codepaths in HVM guests).

If this is an issue, could you post the details fully on xen-devel so
that we can open a tracker bug instead of using the bugzilla system?

Thank you!

  reply	other threads:[~2014-08-04 14:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31  8:52 VMX test report for Xen 4.5-unstable-C/S 28634 Hu, Robert
2014-08-04 14:00 ` Konrad Rzeszutek Wilk [this message]
2014-08-06  7:57   ` Hu, Robert
2014-08-08 18:22     ` Konrad Rzeszutek Wilk
2014-08-08 18:45       ` Processed: " xen

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=20140804140027.GA18425@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=chao.zhou@intel.com \
    --cc=robert.hu@intel.com \
    --cc=xen-devel@lists.xen.org \
    /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.