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

[Xen-users] Dom0 Slackware 11.0 - Boot Failure


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Diogo R" <cadamia@xxxxxxxxx>
  • Date: Sun, 26 Nov 2006 20:19:04 +0000
  • Delivery-date: Sun, 26 Nov 2006 12:19:18 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=FrwPS9WK6yG4vMhI/GFRuUd0v/csuDKnQEqoUBx02rSiFN6HOyhWpGN1A4ZBRFj2LMsx8wGsaVflYo3qOKpRumetEcydHi61u4KXUARm7wLXN7O2yUebhUF4A1q4MFIx7h0dTHkSM0JK0FHgu5USy8CoXalii1OuTBCeX53VCQs=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I'm running into problems setting up Slackware 11.0 as Dom0, the Xen
kernel won't boot.

The install scripts are run without any problems, and this is what I
end up with in /boot:

        lrwxrwxrwx 1 root root   37 2006-11-25 19:50 README.initrd ->
/usr/doc/mkinitrd-1.0.1/README.initrd
        lrwxrwxrwx 1 root root   28 2006-11-26 11:24 System.map ->
System.map-generic-2.6.17.13
        -rw-r--r-- 1 root root 740K 2006-11-26 10:18 System.map-2.6.16.29-xen
        -rw-r--r-- 1 root root 695K 2006-09-09 07:14 
System.map-generic-2.6.17.13
        -rw-r--r-- 1 root root  512 2006-11-25 20:05 boot.0300
        -rw-r--r-- 1 root root  168 2006-11-25 20:05 boot_message.txt
        lrwxrwxrwx 1 root root   24 2006-11-26 11:24 config -> 
config-generic-2.6.17.13
        -rw-r--r-- 1 root root  60K 2006-11-26 10:18 config-2.6.16.29-xen
        -rw-r--r-- 1 root root  62K 2006-09-09 07:14 config-generic-2.6.17.13
        drwxr-xr-x 2 root root 4.0K 2006-11-26 13:05 grub/
        -rw------- 1 root root  28K 2006-11-25 20:05 map
        -rw-r--r-- 1 root root 4.0M 2006-11-26 10:18 vmlinux-syms-2.6.16.29-xen
        lrwxrwxrwx 1 root root   25 2006-11-26 11:24 vmlinuz ->
vmlinuz-generic-2.6.17.13
        lrwxrwxrwx 1 root root   21 2006-11-26 19:14 vmlinuz-2.6-xen ->
vmlinuz-2.6.16.29-xen
        lrwxrwxrwx 1 root root   21 2006-11-26 19:14 vmlinuz-2.6.16-xen ->
vmlinuz-2.6.16.29-xen
        -rw-r--r-- 1 root root 1.5M 2006-11-26 10:18 vmlinuz-2.6.16.29-xen
        -rw-r--r-- 1 root root 1.7M 2006-09-09 07:14 vmlinuz-generic-2.6.17.13
        -rw-r--r-- 1 root root 234K 2006-11-26 10:18 xen-3.0.3-0.gz
        lrwxrwxrwx 1 root root   14 2006-11-26 19:14 xen-3.0.gz -> 
xen-3.0.3-0.gz
        lrwxrwxrwx 1 root root   14 2006-11-26 19:14 xen-3.gz -> xen-3.0.3-0.gz
        -rw-r--r-- 1 root root 2.5M 2006-11-26 10:18 xen-syms-3.0.3-0
        lrwxrwxrwx 1 root root   14 2006-11-26 19:14 xen.gz -> xen-3.0.3-0.gz


I've modified /boot/grub/menu.lst:

        default 0
        timeout 15
        color light-gray/blue black/light-gray


        title Slackware 11.0
                root (hd0,0)
                kernel /boot/vmlinuz root=/dev/hda1 ro vga=773

        title Slackware 11.0 (Xen)
                root (hd0,0)
                kernel /boot/xen.gz noreboot
                module /boot/vmlinuz-2.6-xen root=/dev/hda1 ro

And finally the whole system rests on /dev/hda1 using ext3, with
/dev/hda2 being swap.

When I try to boot the system using the Xen kernel, it fails to mount
the root fs with the following error:

        VFS: Cannot open root device "hda1" or unknown-block(0,0)
        Please append a correct "root=" boot option
        Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)

This is using the default kernel, which has ext2 support, so it should
have been able to mount the root fs. I've also tried building an inird
with the ext3 module and building a custom Xen kernel with ext3
support built in, after running out of ideas.

Nothing seems to work. Any ideas?

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


 


Rackspace

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