xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: New release candidate for Xen 4.0.0 (RC9)
Date: Wed, 31 Mar 2010 15:52:23 -0400	[thread overview]
Message-ID: <20100331195223.GA15322@phenom.dumpdata.com> (raw)
In-Reply-To: <C7D96209.ED95%keir.fraser@eu.citrix.com>

On Wed, Mar 31, 2010 at 08:33:13PM +0100, Keir Fraser wrote:
> On 31/03/2010 20:10, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
> 
> >> This is almost certainly the last RC, and will become the 4.0.0 release
> >> around the middle of next week. Please test!
> > 
> > I don't have a fix, but I did this (this is with xen/stable-2.6.32.x
> > latest and also rolled back to git commit
> > 47bd9cad11b1a723c6e5d1127aebe570a3e34f34
> > with a cherry pick of d3b9e35a81e31ff4edb4666f9c36eb5b2032f4da - just in case
> > the problem was due to the PAT changes):
> 
> Is it a regression?

I haven't tried this type of operation before so I can't comment. I can
spin out a Xen hypervisor - what version back do you want me to compare
to?


Interestingly, on Intel it makes the machine crawl and gets CPU#0 stuck,
while on AMD I get that nice crash.



> 
>  -- Keir
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-03-31 19:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  9:27 New release candidate for Xen 4.0.0 (RC9) Keir Fraser
2010-03-31 10:07 ` Joanna Rutkowska
2010-03-31 10:54   ` Keir Fraser
2010-03-31 11:00     ` Joanna Rutkowska
2010-03-31 11:13       ` Keir Fraser
2010-03-31 12:38       ` Ian Pratt
2010-03-31 14:20         ` Dan Magenheimer
2010-03-31 14:32           ` Keir Fraser
2010-03-31 14:44           ` Ian Pratt
2010-03-31 19:55           ` Grant McWilliams
2010-03-31 15:02 ` Bastian Blank
2010-03-31 15:09   ` Keir Fraser
2010-03-31 15:44     ` Bastian Blank
2010-03-31 16:38       ` Keir Fraser
2010-03-31 18:03         ` Konrad Rzeszutek Wilk
2010-03-31 18:18           ` Keir Fraser
2010-03-31 20:40             ` Jeremy Fitzhardinge
2010-03-31 19:10 ` Konrad Rzeszutek Wilk
2010-03-31 19:33   ` Keir Fraser
2010-03-31 19:52     ` Konrad Rzeszutek Wilk [this message]
2010-03-31 20:07       ` Keir Fraser
2010-03-31 21:07         ` Konrad Rzeszutek Wilk
2010-05-19 12:10           ` Keir Fraser
2010-05-26 15:02             ` 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=20100331195223.GA15322@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=keir.fraser@eu.citrix.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).