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

RE: [Xen-users] How do I find out why Dom0 crashes on guest startup?


  • To: "Schober Walter" <Walter.Schober@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Fri, 18 May 2007 13:21:33 +0200
  • Delivery-date: Fri, 18 May 2007 04:20:08 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AceZNGQtpOgvLZEkThicpe24YZEJjAAADQQAAACVxBAAAFrTcAAAMR6gAAD7RcA=
  • Thread-topic: [Xen-users] How do I find out why Dom0 crashes on guest startup?

[snip big log]
> (XEN) Xen call trace:
> (XEN)    [<ffff830000142da7>] vlapic_range+0x7/0x30

So, the code here does very few things (at least in the current version,
but I doubt that the older code is MUCH different). This in turn means
that it's pretty easy to determine what could be wrong:
1. VCPU = NULL - quite likely, as it's one of the first steps. 
2. vlapic field in vcpu = NULL - even more likely. 

I'd try running your guest with "apic=0" to see if that makes any
difference. [That will of course screw up SMP on your guest, but at
least it will hopefully tell us if it's APIC that is a problem or not]

I doubt that having installed a newer QEMU would make any difference. 

--
Mats



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


 


Rackspace

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