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

Re: [Xen-ia64-devel] Problems Booting


  • To: "Alex Williamson" <alex.williamson@xxxxxx>
  • From: "David Brown" <dmlb2000@xxxxxxxxx>
  • Date: Mon, 20 Nov 2006 12:18:03 -0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 20 Nov 2006 12:18:12 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rEki6t+3g8a7K+0pdLbnl1IwvNl1cwTsUOP9m+3i5zbMM1A+cVNA/cGW6NQ4cxnrUyi0khfOelzCb2rtaJ7+49+n1RoeyfV68yyN8t4e0qRiFx72004+GefXNhWtQ3FRqKV1ncc3gdbdax7ajAW26hLOC/Dhv4wSojUYQTI07X0=
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>

   XEN_DISABLE_SERIAL simply disables dom0s serial driver.  Xen still
supports serial and allows dom0 access to it through the xencons driver.
This config option is simply to prevent both Xen and dom0 from trying to
claim the same piece of physical UART hardware as their own.  Serial
consoles are still fully supported with XEN_DISABLE_SERIAL.

Okay the config help did explain a little more, seems like a bad
naming then, cause that sounded like a bad thing at first glance.

   Ouch, that looks old.  There was a mismatch over how the version was
reported for a while, so don't trust the "1.2c" version.  Instead, go to
an EFI shell and run 'info fw'.  Thanks,

Yup updating did the trick with the firmware I can now see the output
and watch the kernel go through the init process.

Thanks for the help

- David Brown

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


 


Rackspace

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