From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [BUG] Problem Booting Xen 4.0.1 on 2.6.32.26/27 Date: Thu, 20 Jan 2011 14:26:01 -0500 Message-ID: <20110120192601.GB10001@dumpdata.com> References: <4D36E0200200002600018535@hibbing.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4D36E0200200002600018535@hibbing.edu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Don Brearley Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Wed, Jan 19, 2011 at 12:59:12PM -0600, Don Brearley wrote: > Hello, > > I'm attempting to boot Xen 4.0.1 on a SuperMicro H8DGi-F motherboard and > having not much luck. I can boot the > 2.6.32.26 (or .27) kernels alone, but when I add Xen into the mix, I get > consistent boot failure. > > I've tried Xen 4.0.1-release, 4.0.2-rc1-pre and 4.0.2-rc2-pre, all get > the same failure. > > xen/next-2.6.37 works and boots great, but since netback isn't included > in that yet, I am unable to actually use it > for anything yet. Whoa, it usually is the other way around.. > > Please feel free to contact me for further information. Email is > fine, I'm also on IRC in ##xen as "breardo". > > Here is a log of the boot failure: (Xen 4.0.1 on 2.6.32.26 / Debian > Squeeze beta2) > > (XEN) Xen version 4.0.1 (root@hibbing.edu) (gcc version 4.4.5 (Debian > 4.4.5-8) ) Wed Jan 19 12:23:59 CST 2011 > (XEN) Latest ChangeSet: Wed Aug 25 09:22:42 2010 +0100 > 21324:b536ebfba183 > (XEN) Bootloader: GRUB 1.98+20100804-11 > (XEN) Command line: dom0_mem=2048M loglvl=all guest_loglvl=all > lapic=debug apic_verbosity=debug apic=debug iommu=off com2=115200,8n1 > console=com2 Also add 'console_sync' (or was it sync_console?). That should give us more data and see whether the failure was .. .. > [ 0.036368] allo(XEN) CPU counter reports 4094 correctable hardware > errors that were not reported by the status MSRs here or later on.