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

[Xen-devel] BUG using xen-unstable with XSM + Flask


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Thomas DuBuisson <thomas.dubuisson@xxxxxxxxx>
  • Date: Tue, 7 Jul 2009 20:28:40 -0700
  • Delivery-date: Tue, 07 Jul 2009 20:29:07 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=lXk/GSklh4nU3YXeJYYlygZX2No9a4QB++Yf0CC6BxOU+2AlPfy7MtSF0jBgmMmnCI 1RiWBs0CCkBxZ2kZj314RtQSonQADPem9yoksFU+cD+pTflHYBMQznGcnU8FkbeDfhFd c6Mp2rTHKQDGmjfBtcpaY7QebnVNtcbm8+xaw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

While xen-unstable works OK for me normally, when I compile xen.gz
with XSM and Flask I can't boot - instead I get a panic from
domain_build.c line 1100.  That line is a "BUG_ON( rc != 0)" in the
function construct_dom0().

My system:
Thinkpad T61 (Intel core2 duo)

Software config:
Fedora 11 i686 (gcc 4.4.0), using current HEAD from xen-unstable.

Let me know what other info would help if you're interested.

Thomas

_______________________________________________
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®.