xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Edge <bruce.edge@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: 2.6.32.16: hvm domU boot - oops at add_pin_to_irq_node_nopanic
Date: Thu, 8 Jul 2010 09:59:11 -0700	[thread overview]
Message-ID: <AANLkTin2rWSOMj9HuuLgJayELTwlatJe9XxsxpaxZjVk@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1007081753040.21432@kaball-desktop>


[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]

On Thu, Jul 8, 2010 at 9:55 AM, Stefano Stabellini <
stefano.stabellini@eu.citrix.com> wrote:

> On Thu, 8 Jul 2010, Bruce Edge wrote:
> > This is the same problem as this post:
> > http://lists.xensource.com/archives/html/xen-devel/2010-06/msg01114.html
> >
> > Stefano suggested I retry after Jeremy's pull.
> >
> > Sync'd with 2.6.32.16 last night and it looks like the identical problem.
> >
> > I can boot Ubuntu 10.04 with it's own native kernel, but not with a
> pv-ops kernel.
> >
> > This is with # CONFIG_XEN_PLATFORM_PCI is not set, .config is attached.
> >
>
> I think that Jeremy didn't merge the up-to-date PV on HVM branch in
> stable-2.6.32.x but only in next.
>
>
I thought that the PV on HVM code was only used
if CONFIG_XEN_PLATFORM_PCI=y.
Is that not the case?

I'll try xen/next.

Thanks

-Bruce

[-- Attachment #1.2: Type: text/html, Size: 1375 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2010-07-08 16:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 15:39 2.6.32.16: hvm domU boot - oops at add_pin_to_irq_node_nopanic Bruce Edge
2010-07-08 16:55 ` Stefano Stabellini
2010-07-08 16:59   ` Bruce Edge [this message]
2010-07-08 17:04     ` Stefano Stabellini
2010-07-08 17:56       ` Bruce Edge
2010-07-09 10:37         ` Stefano Stabellini
2010-07-10 21:11           ` Bruce Edge
2010-07-12 11:22             ` Stefano Stabellini
     [not found]               ` <alpine.DEB.2.00.1007121351070.21432@kaball-desktop>
2010-07-12 13:41                 ` Bruce Edge
2010-07-12 14:15                   ` Bruce Edge
2010-07-12 14:15                   ` Stefano Stabellini
2010-07-12 17:09                   ` Ian Jackson
2010-07-12 21:34                 ` Bruce Edge
2010-07-13 10:40                   ` Stefano Stabellini
2010-07-08 18:39     ` Jeremy Fitzhardinge
2010-07-09 16:50       ` Bruce Edge
2010-07-08 19:25 ` Łukasz Oleś
2010-07-09  9:42   ` Łukasz Oleś
2010-07-09  9:54     ` Łukasz Oleś
2010-07-09 10:46       ` Stefano Stabellini
2010-07-09 14:00         ` Bruce Edge
2010-07-09 14:26           ` Stefano Stabellini
2010-07-12 12:56         ` Łukasz Oleś
2010-07-12 13:01           ` Stefano Stabellini
2010-07-15 10:49             ` Łukasz Oleś
2010-07-09 13:30       ` Bruce Edge

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=AANLkTin2rWSOMj9HuuLgJayELTwlatJe9XxsxpaxZjVk@mail.gmail.com \
    --to=bruce.edge@gmail.com \
    --cc=jeremy@goop.org \
    --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 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).