Re: [Xen-users] XEN 4.0 boot error

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Thu, Apr 08, 2010 at 10:43:57PM +0100, Ian Tobin wrote:
> Hey guys,
> 
> Sorry for the delay, been manic today.
> 
> I actually resolved this issue by messing around in the bios and enabling 
> ACPI HPET Table 
> 
> Im not sure what that does but it booted straight away after that.
> 
> Maybe someone could shed some light on what it does.
>

HPET is High Precision Event Timer, afaik.
That shouldn't affect kernel finding root disk/device..

Maybe the setting affected some ACPI IRQ routing stuff aswell.. 

-- Pasi

> Cheers
> 
> Ian
> 
> 
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Pasi Kärkkäinen
> Sent: 08 April 2010 19:54
> To: Konto usnetu
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] XEN 4.0 boot error
> 
> On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu wrote:
> >    2010/4/8 Pasi Kärkkäinen <[1]pasik@xxxxxx>
> > 
> >      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
> >      >    Hey all,
> >      >
> >      >    Just downloaded the new Xen 4.0 and ran
> >      >
> >      >    Make xen
> >      >    Make tools
> >      >    Make stubdom
> >      >
> >      >    Copied the new files from dist/install
> >      >    Im already running pv_ops 2.6.31.6 kernel.
> >      >
> >      >    When I boot i get
> >      >
> >      >    (XEN) Panic on CPU 0:
> >      >    (XEN) IO-APIC +  timer doesn't work!
> >      >
> >      >    I have tried booting with noapic boot option but makes no
> >      difference.  The
> >      >    system worked fine on 3.4.2
> >      >
> >      >    CPU is AMD.
> >      >
> >      >    Any ideas?
> >      >
> > 
> >      Well.. can you post a full serial console log of the boot process?
> > 
> >      See here for help: [2]http://wiki.xensource.com/xenwiki/XenParavirtOps
> > 
> >    I have the same problem to boot xen 4.0 on debian lenny 5.0,  under I
> >    paste a some error:
> > 
> >    41.017078]   Magic number: 6:876:244
> >    [   41.061177] md: Waiting for all devices to be available before
> >    autodetect
> >    [   41.142579] md: If you don't use raid, use raid=noautodetect
> >    [   41.211225] md: Autodetecting RAID arrays.
> >    [   41.260417] md: Scanned 0 and added 0 devices.
> >    [   41.313729] md: autorun ...
> >    [   41.347281] md: ... autorun DONE.
> >    [   41.387150] Root-NFS: No NFS server available, giving up.
> >    [   41.451921] VFS: Unable to mount root fs via NFS, trying floppy.
> >    [   41.524664] VFS: Cannot open root device "sda1" or unknown-block(2,0)
> 
> 
> So the disk was not detected, or did you pass wrong root= parameter? 
> 
> Please post the _full_ log.
> 
> -- Pasi
> 
> >    [   41.601913] Please append a correct "root=" boot option; here are the
> >    available partitions:
> >    [   41.702180] 0b00         1048575 sr0 driver: sr
> >    [   41.756691] Kernel panic - not syncing: VFS: Unable to mount root fs 
> > on
> >    unknown-block(2,0)
> >    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
> >    [   41.921708] Call Trace:
> >    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
> >    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
> >    [   42.049483]  [<c191ec2d>] mount_block_root+0x163/0x172
> >    [   42.111158]  [<c1002930>] ? hypercall_page+0x930/0x1005
> >    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
> >    [   42.227178]  [<c191ee05>] prepare_namespace+0x145/0x16c
> >    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
> >    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
> >    [   42.402764]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> > 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 

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