WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] SCSI support, kernel panic on boot

Here's what i've done :

- "mkinitrd /boot/initxen.img 2.6.16-xen"
Then, a lot of FATAL ERROR came out, saying there's no modules.dep, so
i've created one :
- "depmod 2.6.16-xen"
After that, i could execute my mkinitrd, and load it properly into my
menu.lst :


//title Xen 3.0 / XenLinux 2.6
//root (hd0,0)
//kernel /boot/xen-3.0.gz dom0_mem=100000
//module /boot/vmlinuz-2.6-xen root=/dev/sda1 ro console=tty0
//module /boot/initxen.img


Reboot ... and few seconds after seeing that the SCSI were load (kernel
tainted, but sound supported), a wonderfull freez that forced me to
reboot physicaly the machine (glrup :s) Last line said there's vga
framebuffer. I said ok, let's add "nofb" on my kernel cmd line, and then
came out .... (correct !!) a new kernel panic

"Kernel panic - not syncing: Attempted to kill init!
 ERROR opening /dev/console"

Apparently it's an error from a corrupt initrd file ... i'm totally
desesperate, can't find a way out to fix it once for good. Need help my
xen-friends :)

Thx in advance



Le mardi 06 juin 2006 à 08:38 -0600, Serge Dubrouski a écrit :
> Boot up with the standard (non XEN) kernel and try to create initrd
> image for XEN Dom0 then. After you have initrd created update your
> menu.lst with new initrd. Your current initrd isn't right one because
> it contains modules form the old kernel. They can't be loaded.
> 
> 
> On 6/6/06, Aurelien Neyrand <aneyrand@xxxxxxxxxxxx> wrote:
> > Hi everyone, here's my problem with xen 3.0.2: I've installed XEN on a
> > debian sarge 2.6.8.2 (IBM bi-xeon 3.2/1goRAM/HD scsi)
> > Here's how my boot launcher looks like:
> >
> > title Xen 3.0 / XenLinux 2.6
> > root (hd0,0)
> > kernel /boot/xen-3.0.gz dom0_mem=100000
> > module /boot/vmlinuz-2.6-xen root=/dev/sda1 ro console=tty0
> > module /boot/initrd.img-2.6.8-2-386
> >
> >
> > ....and there goes my "hapy" dom0 kernel panic on boot
> >
> > « VFS: Cannot open root device "sda1" or unknown-block(0,0)
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) »
> >
> >
> > I've searched a lot about this, trying to remove/add module lines in my
> > menu.lst, and i think the problem is due to SCSI driver). On the dmesg
> > of my debian, it says :
> >
> > « Fusion MPT base driver 3.01.09
> > Fusion MPT SCSI Host driver 3.01.09 »
> >
> > If anyone know about SCSI support (how to add a driver into sources ?
> > where to find it ?) or if there's a way out with mkinit (or smthing like
> > that), i would appreciate a lot !!
> >
> >
> > thx in advance.
> >
> >
> >
> > _______________________________________________
> > 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


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

<Prev in Thread] Current Thread [Next in Thread>