[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] 2.6.32.16: hvm domU boot - oops at add_pin_to_irq_node_nopanic


  • To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
  • From: Łukasz Oleś <lukaszoles@xxxxxxxxx>
  • Date: Mon, 12 Jul 2010 14:56:29 +0200
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 12 Jul 2010 05:57:26 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jziy62uihXcbSzDyMfTvWoAyPE0/6JoMAlI8DTpr6ERtSHkQf9/g2SsRstbYse0KiJ 9Z9R4sJo3/mNCmZrvZ5FZl0KeBIzyhPMEFTVPBQ/z5hVkSbcqgMqjo/WCFJdAgDIri9F zIo6BlXUG0Vwm1e+qY67PLTK67o7DzvstJz6o=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

W dniu 9 lipca 2010 12:46 użytkownik Stefano Stabellini
<stefano.stabellini@xxxxxxxxxxxxx> napisał:
> On Fri, 9 Jul 2010, Łukasz Oleś wrote:
>> W dniu 9 lipca 2010 11:42 użytkownik Łukasz Oleś <lukaszoles@xxxxxxxxx> 
>> napisał:
>> > 2010/7/8 Łukasz Oleś <lukaszoles@xxxxxxxxx>:
>> >> 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ś

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.