On Fri, Jul 8, 2011 at 9:56 PM, Stefan <hest@xxxxxxxxxxx> wrote:
> Hello Fajar,
> Hello List,
>
>>> As I said domu is accessible but... I foudn several mount problems >> and
>>
>> what problems?
>
> It seems to me that Dom0 is not handing over /dev/xvda1 and /dev/xvda2
> to DomU. Root (on /dev/xvda1) is not accessible...
>
This might be the cause
disk = [ 'phy:/dev/mapper/data-xen1,/dev/xvda1,w',
'phy:/dev/mapper/data-xen1_swap,/dev/xvda2,w' ]
try
disk = [ 'phy:/dev/mapper/data-xen1,xvda1,w',
'phy:/dev/mapper/data-xen1_swap,xvda2,w' ]
> This is the output on the screen:
> --------------
> Gave up waiting for root device. Common problems:
> - Boot args (cat /proc/cmdline)
> - Check rootdelay= (did the system wait long enough?)
> - Check root= (did the system wait for the right device?)
> - Missing modules (cat /proc/modules; ls /dev)
> ALERT! /dev/xvda1 does not exist. Dropping to a shell!
>
>
> BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> /bin/sh: can't access tty; job control turned off
> (initramfs)
> --------------
>
>> Full boot log might help find out what's wrong.
>
> Attached the dmesg of the DomU and again fstab (of DomU) and xen.conf.
You're attaching "xm dmesg". Not needed in this case. What's needed is
full log of domU during boot, which you do NOT attach.
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home