On Tue, Aug 26, 2008 at 8:52 AM, Jörg Spilker <js@xxxxxxxxx> wrote:
> Hello,
>
> when starting a guest domain (using OpenSUSE 11.0 for host and guest) the
> startup process lasts very long. The logfile of the guest shows the
> following entries:
>
> <4>XENBUS: Waiting for devices to initialise:
> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
> <4>XENBUS: Device not ready: device/vbd/2816
>
> The host device configuration for the guest is:
>
> disk=[ 'phy:/dev/domX/daolin_root,sda1,w'
> , 'phy:/dev/domX/daolin_boot,sda2,w'
> , 'phy:/dev/domX/daolin_usr,sda3,w'
> , 'phy:/dev/domX/daolin_opt,sda4,w'
> , 'phy:/dev/domX/daolin_var,sda5,w'
> , 'phy:/dev/domX/daolin_src,sda6,w'
> , 'phy:/dev/domX/daolin_tmp,sda7,w'
> , 'phy:/dev/data/home,sda8,w'
> , 'phy:/dev/data/foto,sda9,w'
> , 'phy:/dev/data/imap,sda10,w'
> , 'phy:/dev/data/news,sda11,w'
> , 'phy:/dev/data/squid,sda12,w'
> , 'phy:/dev/data/srv,sda13,w'
> # , 'phy:/dev/hda1,sda14,w'
> , 'phy:/dev/cdrom,sr0:cdrom,r', ]
> vif=[ 'mac=00:16:3e:35:55:5f', ]
> vfb=['type=vnc,vncunused=1']
>
> and the hosts log shows the following:
>
> Aug 26 14:11:58 lotus logger: /etc/xen/scripts/block: add
> XENBUS_PATH=backend/vbd/4/2816
> Aug 26 14:12:05 lotus logger: /etc/xen/scripts/block: Writing
> backend/vbd/4/2816/physical-device b:0 to xenstore.
> Aug 26 14:12:05 lotus logger: /etc/xen/scripts/block: Writing
> backend/vbd/4/2816/hotplug-status connected to xenstore.
> Aug 26 14:12:05 lotus kernel: vbd vbd-4-2816: 2 creating vbd structure
>
> All configured disks on the host are available on the guest and i´m not able
> to identify the missing device. Is there any way to identify the source of
> the problem ?
>
This is usually caused by a missing module in the initial ram disk of the guest.
when it drops you to busybox, do what it suggest, check the modules, cmdline,
and /dev/
You may just need to rebuild your initial ram disk.
Hope that helps.
Cheers,
Todd
> Greetings, Jörg
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
--
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home