All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.1 rc5 outstanding bugs
Date: Wed, 9 Mar 2011 12:10:58 -0500	[thread overview]
Message-ID: <20110309171058.GF8049@dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103081706420.2968@kaball-desktop>

On Tue, Mar 08, 2011 at 05:13:46PM +0000, Stefano Stabellini wrote:
> On Tue, 8 Mar 2011, Konrad Rzeszutek Wilk wrote:
> > On Fri, Feb 18, 2011 at 06:59:55PM +0000, Stefano Stabellini wrote:
> > > Hi all,
> > > I went through the list of bugs affecting the latest Xen 4.1 RC and
> > > I made a list of what they seem to be the most serious.
> > 
> > What is the status of these? I know you made some strides in fixing
> > most if not all of them both in the hypervisor and Linux kernel.
> > 
> 
> we have fixed most of them, see below

Indeed!

.. snip..
> > >  *  PCI hot-unplug causes a guest crash
> > > also know as "fail to detach NIC from guest"
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1736
> 
> I cannot repro this bug, I think someone at Intel is working on it.

Ok, asked the Intel submitter to see if your assumptions are correct.

      reply	other threads:[~2011-03-09 17:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 18:59 Xen 4.1 rc5 outstanding bugs Stefano Stabellini
2011-02-21  8:32 ` Jan Beulich
2011-02-21 11:05   ` Stefano Stabellini
2011-02-21 11:25     ` Jan Beulich
2011-02-21 17:29     ` Anthony PERARD
2011-02-22  6:17       ` Zhang, Yang Z
2011-02-23 18:58         ` Stefano Stabellini
2011-03-08 15:43 ` Konrad Rzeszutek Wilk
2011-03-08 17:13   ` Stefano Stabellini
2011-03-09 17:10     ` 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=20110309171058.GF8049@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@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 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.