[one-users] Problem in booting VM

[Sander Klous]

Hi,
I just had this problem as well a few days ago. The xen packages on 
Lenny are broken. They don't work with the tap:aio interface, see:

http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2009-June/002344.html

To fix it, I did (as root):

ln -s /usr/lib/xen-3.2-1/bin/tapdisk /usr/sbin
echo xenblktap >> /etc/modules

After a reboot, it worked for me.
Sander

cmasmas cmasmas wrote:
> Hi,
>
> Both Dom0 and DomU are Debian Lenny.
>
> If I boot the VM directly with this .cfg, it goes Ok:
>
> /kernel = '/boot/vmlinuz-2.6.26-2-xen-686'
> ramdisk = '/boot/initrd.img-2.6.26-2-xen-686'
> memory = "256"
> name = "a"
> vif = ['mac=00:16:3e:22:22:22']
> disk = ['file:/home/user/debian.5-0.x86.img,sda1,w']
> root = "/dev/sda1 ro"/
>
> I'm using this template:
>
> /NAME   = vm-example
> MEMORY = 768
> OS     = [
>   kernel   = "/boot/vmlinuz-2.6.26-2-xen-686",
>   initrd   = "/boot/initrd.img-2.6.26-2-xen-686",
>   root     = "sda1 ro"]
>
> DISK   = [
>   source   = "/opt/nebula/images/debian-stacklet/debian.5-0.x86.img",
>   target   = "sda1",
>   readonly = "no" ]
>
> NIC    = [ mac  = "00:16:3e:58:82:3a" ]/
>
> which generates the following deployment.0 file:
>
> /name = 'one-61'
> #O CPU_CREDITS = 256
> memory  = '768'
> kernel = '/boot/vmlinuz-2.6.26-2-xen-686'
> ramdisk = '/boot/initrd.img-2.6.26-2-xen-686'
> root = '/dev/sda1 ro'
> disk = [
>     'tap:aio:/opt/nebula/ONE/var//61/images/disk.0,sda1,w',
> ]
> vif = [
>     'mac=00:16:3e:58:82:3a',
> ]/
>
> So, the first problem is at this point. It takes about 5 minutes. 
> However, when booting directly (without using ONE) it takes a few seconds.
>
> /[    5.407251] XENBUS: Waiting for devices to initialise: 
> 295s...290s...285s...280s...275s...270s...265s...(...)75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s.../
>
> The second problem: It fails when trying to mount the root file 
> system. Without using ONE, this doesn't happen:
>
> /Begin: Mounting root file system ... Begin: Running 
> /scripts/local-top ... done.
> Begin: Waiting for root file system ... ^Cdone.
> 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/sda1 does not exist. Dropping to a shell!
>
> BusyBox v1.10.2 (Debian 1:1.10.2-2) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> /bin/sh: can't access tty; job control turned off
> (initramfs)/
>
> I'm stacked at this point. Any tip/advice is welcomed.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>