All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Neobiker <neo1106@neobiker.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: XEN boot hangs at ACPI: PCI Root Bridge [PCI0] (0000:00)
Date: Wed, 17 Nov 2010 11:48:06 -0500	[thread overview]
Message-ID: <20101117164806.GA19835@dumpdata.com> (raw)
In-Reply-To: <1289938196336-3267936.post@n5.nabble.com>

On Tue, Nov 16, 2010 at 12:09:56PM -0800, Neobiker wrote:
> 
> 
> Konrad Rzeszutek Wilk wrote:
> > 
> > 
> >> Xen may be back to stay as a virtualisation standard if kernel 2.6.38
> >> will
> >> be able to start as dom0 (as 2.6.37 will) and to be able to drive domUs
> >> (missing in upcoming 2.6.37). I think that's really really (!) important
> >> for
> >> XEN future. And: XEN 4.0.x must be as rock stable as 3.4.2 as soon as
> >> possible... i personnally don't think about using 4.0.x for production
> >> systems at this point...
> > 
> > Uh, even 4.0.1? What are the issues you are worried about?
> > 
> > 
> I'm worried about stability, changes in behaviour, changes in kernel /
> parameters, problems with compiling some orig xen kernel, problems running

All of those, except stability, are issues you are going to encounter with
a new kernel...

Can you be more specific about the stability? Have you seen it crash?

> 2.6.18 kernel like above,  dependencies like pvops version .32 for > 4.0.1,
> .31 for < 4.0.1, bugs in 4.0.0, less bugs in 4.0.1, missing features like

PVUSB.. well we would love if somebody volunteered to do the driver.

> pvusb, windows in vhd didn't like the GPLPV drivers (blue screen), signed

Uhh, no idea. I am actually using the Novell GPL drivers in Windows 2000
and they seem to work fine.

> Citrix PV drivers only work with version 5.5, not 5.6, pvops kernel works on
> my hardware with debian pvops xen 4.0.1 kernel, but xen pvops kernel
> compiled according to wiki fc13 page has errors with agpart loading and so
> on..... so i'm waiting for 4.0.3 ;-)

Hm, the agpart loading I thought was fixed. When did you observe this behavior?

  reply	other threads:[~2010-11-17 16:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 17:11 XEN boot hangs at ACPI: PCI Root Bridge [PCI0] (0000:00) Jens Friedrich
2010-11-11 16:18 ` Konrad Rzeszutek Wilk
2010-11-11 17:16   ` Neobiker
2010-11-12 22:19     ` Konrad Rzeszutek Wilk
2010-11-12 23:20       ` Sander Eikelenboom
2010-11-15 16:47         ` Konrad Rzeszutek Wilk
2010-11-15 16:58           ` Sander Eikelenboom
2010-11-13 10:14       ` Neobiker
2010-11-15 16:49         ` Konrad Rzeszutek Wilk
2010-11-16 20:09           ` Neobiker
2010-11-17 16:48             ` Konrad Rzeszutek Wilk [this message]
2010-11-26 19:45               ` Neobiker
2010-11-26 19:58                 ` Neobiker
2010-11-29 17:07                 ` Konrad Rzeszutek Wilk
2011-03-12 18:54                 ` agpgart-intel 0000:00:00.0: can't get memory for scratch page dnyaneshgate
2011-03-14 14:44                   ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2010-11-17 20:52 AW: Re: XEN boot hangs at ACPI: PCI Root Bridge [PCI0] (0000:00) Neobiker
2010-11-18 12:31 ` Pasi Kärkkäinen

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=20101117164806.GA19835@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=neo1106@neobiker.de \
    --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.