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] domU ttylinux kernel panic Cannot open root device with

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU ttylinux kernel panic Cannot open root device with current xen-unstable
From: Dennis <devel@xxxxxxxxxxxxxxx>
Date: Mon, 05 Dec 2005 15:44:52 -0700
Delivery-date: Mon, 05 Dec 2005 22:45:39 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <00dd01c5f65e$17f46ae0$1e84800a@heipc0016n>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <00dd01c5f65e$17f46ae0$1e84800a@heipc0016n>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
I just happened upon that same error.  Funny thing was, that it wasn't
the domU kernel.  I accidentally copied over the dom0 kernel.  Copying
back the domU kernel worked just as it was supposed to.  That may not be
your error though.

-Dennis

Dieter Edinger WEB.DE wrote:

> Hello,
>
> I downloaded the current xen-unstable sources from 30.11.2005 and made
> an make world, make install.
> The dom0-Kernel boots successfully, but the domU-kernel cannot open
> the root device. I tried also with hda1 instead of sda1, but the
> result was the same.
>
> Has anybody an idea?
>
> Regards,
> Dieter Edinger
> dieter.edinger@xxxxxx
>
> file /etc/ttylinux:
> kernel = "/boot/vmlinuz-2.6.12.6-xenU"
> memory = 48
> name = "ttylinux"
> nics = 1
> disk = ['file:/etc/xen/ttylinux-xen,sda1,w']
> root = "/dev/sda1 ro"
>
> Output of xm create ttylinux -c:
> Using config file "ttylinux".
> Started domain ttylinux
> Linux version 2.6.12.6-xenU (root@hei-pc0016) (gcc-Version 3.4.4
> (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #1 SMP Wed Nov 30
> 13:55:53 CET 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000003000000 (usable)
> 0MB HIGHMEM available.
> 56MB LOWMEM available.
> IRQ lockup detection disabled
> Built 1 zonelists
> Kernel command line:  root=/dev/sda1 ro
> Initializing CPU#0
> PID hash table entries: 256 (order: 8, 4096 bytes)
> Xen reported: 1495.145 MHz processor.
> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> vmalloc area: c4000000-fb7fe000, maxmem 34000000
> Memory: 45568k/57344k available (1783k kernel code, 3496k reserved,
> 472k data, 136k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor
> mode... Ok.
> Mount-cache hash table entries: 512
> CPU: Trace cache: 12K uops, L1 D cache: 8K
> CPU: L2 cache: 256K
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> Brought up 1 CPUs
> NET: Registered protocol family 16
> Brought up 1 CPUs
> xen_mem: Initialising balloon driver.
> Grant table initialized
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Xen virtual console successfully installed as tty1
> Event-channel device installed.
> netfront: Initialising virtual ethernet driver.
> NET: Registered protocol family 2
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP established hash table entries: 2048 (order: 2, 16384 bytes)
> TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
> TCP: Hash tables configured (established 2048 bind 2048)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "sda1" or unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
>
>
>
>
> _______________________________________________
> 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>