Re: [Xen-devel] need known working 64-bit upstream kernel config file for PV guest

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

On Thu, May 13, 2010 at 04:03:00PM -0700, Dan Magenheimer wrote:
> > > Any working x86_64 config file for any upstream kernel >=2.6.32
> > > would be fine.  I have a 32-bit config file that works fine for
> > 2.6.27
> > > up to 2.6.32 (and I think for 2.6.33... trying again now).
> > >
> > 
> > 2.6.33.0 is known to crash as Xen PV guest, I think 2.6.33.2 fixes
> > that.
> > So better use 2.6.33.latest update.
> > 
> > You could grab the Fedora 13 2.6.33.3 kernel and get the .config from
> > it?
> > That F13 kernel works for me.
> 
> Tried a 2.6.33.4 upstream kernel with the F13
> config-2.6.33.3-79.rc13.x86_64 and it also fails.
> 
> So there must be a kernel bug that the F13 kernel patches fix?
> 
> Here's the output... note still a system call failing...
> 

It looks like the root= parameter is wrong? 


> (early) Linux version 2.6.33.4 
> (root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 
> 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 18:10:25 EDT 2010
> (early) Command line: ro root=LABEL=/ earlyprintk=xen console=hvc0 
> Red Hat nash version 5.1.19.6 starting
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Setting up hotplug.
> Creating block device nodes.
> Loading xen-blkfront.ko module
> blkfront: xvda: barriers enabled
>  xvda: xvda1 xvda2 xvda3
> Loading xen-blkfront.ko module
> insmod: error inserting '/lib/xen-blkfront.ko': -1 File exists
> Loading xen-blkfront.ko module
> insmod: error inserting '/lib/xen-blkfront.ko': -1 File exists
> Loading xen-blkfront.ko module
> insmod: error inserting '/lib/xen-blkfront.ko': -1 File exists
> Scanning and configuring dmraid supported devices
> Trying to resume from LABEL=SWAP-VM
> Unable to access resume device (LABEL=SWAP-VM)
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'

Here..

> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> Kernel panic - not syncing: Attempted to kill init!

-- Pasi


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