From: "Łukasz Oleś" <lukaszoles@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "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: Mon, 12 Jul 2010 14:56:29 +0200 [thread overview]
Message-ID: <AANLkTilhG0Jby1EZXR8QBx_y9cCxAtIqHqC1tinr2STM@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1007091139550.21432@kaball-desktop>
W dniu 9 lipca 2010 12:46 użytkownik Stefano Stabellini
<stefano.stabellini@eu.citrix.com> napisał:
> On Fri, 9 Jul 2010, Łukasz Oleś wrote:
>> W dniu 9 lipca 2010 11:42 użytkownik Łukasz Oleś <lukaszoles@gmail.com> napisał:
>> > 2010/7/8 Łukasz Oleś <lukaszoles@gmail.com>:
>> >> On Thursday 08 July 2010 17:39:49 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.
>> >>
>> >> I have identical problem and tried with and without CONFIG_XEN_PLATFORM_PCI
>> >> option.
>> >>
>> >> I'll test xen/next-2.6.32 and see if it helps.
>> >>
>> >
>> > I tried xen/next-2.6.32 and there is no call trace but now it just hangs.
>> > I'm running this kernel as HVM domU, but it has enabled options for
>> > dom0. Should this work?
>> >
>> > Attached kernel config file and logs from xen/stable-2.6.32 xen/next-2.6.32
>> >
>>
>> Sending also output from xm log
>>
>> This line: "(XEN) hvm.c:3115:d15 Bad HVM op 9." appears when starting
>> domU with kernel from xen/next-2.6.32
>
> That line means that you are running on a Xen version that doesn't have
> HVMOP_pagetable_dying, like xen 4.0 testing for example. It shouldn't
> caouse any trouble per se.
> If you are running on xen 4.0, could you please apply to the hypervisor
> the patch I attached to this email and try one more time?
>
Could you rebase this patch for the latest xen-4.0-testing? I have
problems with running xen-4.0 on my computer.
--
Łukasz Oleś
next prev parent reply other threads:[~2010-07-12 12:56 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
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 ` Stefano Stabellini
2010-07-12 14:15 ` Bruce Edge
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ś [this message]
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=AANLkTilhG0Jby1EZXR8QBx_y9cCxAtIqHqC1tinr2STM@mail.gmail.com \
--to=lukaszoles@gmail.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 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).