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

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Mon, 12 Jul 2010, Łukasz Oleś wrote:
> 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.
> 
 
just pull from xen-4.0-testing: the patch in question has already been
applied as CS 21239.

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