hi,
You could have a look at your /etc/fstab in the Domain U filesystem
image that you are trying to boot. It probably doesn't have a valid /
entry.
I 've something like this.
/dev/hda5 / ext2 rw,noatime 0 1
~$ubh
On 7/21/05, Landratsamt Unterallgäu - Michael Böhm
<mboehm@xxxxxxxxxxxxxxxxxxx> wrote:
> Hello!
>
> This is my Problem:
>
> ---cut---
> miranda:~# xm create -c -f /etc/xen/xmtest1
> Using config file "/etc/xen/xmtest1".
> Started domain xmtest1, console on port 9601
> ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> Linux version 2.6.11.10-xenU (xenod@xxxxxxxxxxxxxxxxxxxxx) (gcc version
> 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Sun May 22 11:42:16 BST 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000008000000 (usable)
> 128MB LOWMEM available.
> DMI not present.
> IRQ lockup detection disabled
> Allocating PCI resources starting at 08000000 (gap: 08000000:f8000000)
> Built 1 zonelists
> Kernel command line: root=/dev/sda1 ro
> Initializing CPU#0
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> Xen reported: 1808.450 MHz processor.
> Using tsc for high-res timesource
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> vmalloc area: c8800000-fbff9000, maxmem 34000000
> Memory: 127104k/131072k available (1630k kernel code, 3800k reserved, 412k
> data, 112k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode... Ok.
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> CPU: L2 Cache: 512K (64 bytes/line)
> CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 00
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> NET: Registered protocol family 16
> xen_mem: Initialising balloon driver.
> 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 tty
> Event-channel device installed.
> xen_blk: Initialising virtual block device driver
> xen_net: Initialising virtual ethernet driver.
> NET: Registered protocol family 2
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> 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)
>
> ************ REMOTE CONSOLE EXITED *****************
> miranda:~#
> ---cut---
>
> Configuration file:
> disk = [ 'file:/var/local/xen/xmtest1/sda1,sda1,w' ]
> disk = [ 'file:/var/local/xen/xmtest1/sda2,sda2,w' ]
> root = "/dev/sda1 ro"
>
> Xen and kernels are 2.0.6 prebuild binaries. I also tried to install from
> source or to use hda? instead of sda? with the same results.
>
> Any hints?
>
> Regards,
> Michael
>
>
> _______________________________________________
> 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
|
Home