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: Konrad Rzeszutek Wilk <konrad@kernel.org>,
	'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: Thu, 6 Sep 2012 07:11:58 -0400	[thread overview]
Message-ID: <20120906111158.GF3668@phenom.dumpdata.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A10190E9D@SHSMSX101.ccr.corp.intel.com>

On Thu, Sep 06, 2012 at 08:18:16AM +0000, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: Konrad Rzeszutek [mailto:ketuzsezr@gmail.com] On Behalf Of
> > Konrad Rzeszutek Wilk
> > Sent: Saturday, September 01, 2012 1:24 AM
> > To: Ren, Yongjie
> > Cc: 'xen-devel'; 'Keir Fraser'; 'Ian Campbell'; 'Jan Beulich'; 'Konrad
> > Rzeszutek Wilk'
> > Subject: Re: [Xen-devel] Xen4.2-rc3 test result
> 
> > > 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?
> > 
> No, 'xl' doesn't allow me to do that. We can't assignment a device to different guests. 
> Sorry, the description of this bug is not accurate. I changed its title to "Dom0 cannot be shut down before PCI device detachment from a guest".
> If a guest (with a PCI device assigned) is running, Dom0 will panic when shutting down.

And does it panic if you use the 'irqpoll' option it asks for?
Xen-pciback has no involvment as:


[  283.747488] xenbus_dev_shutdown: backend/pci/1/0: Initialised != Connected, skipping

and the guest still keeps on getting interrupts.

What is the stack at the hang? 
> 
> > > 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).
> > 
> I tested a RHEL guest with Linux kernel 3.5.3 which already includes Jan's patches you mentioned.
> It will not fix this bug.
> If using kernel 3.5.3 in guest, the guest totally can't resume after running ' xl trigger $dom_ID s3resume'.
> There's some info (as following) in 'xl dmesg' when trying to resume the guest.
> (XEN) HVM10: S3 resume called 00fe 0x00099180
> (XEN) HVM10: S3 resume jump to 9918:0000
> But the guest can't resume.
> 
> > > 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
> > >

  parent reply	other threads:[~2012-09-06 11:11 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
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 [this message]
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=20120906111158.GF3668@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=konrad@kernel.org \
    --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).