[one-users] [one users] Error cannot access to the VM

[Javier Fontan]

Hello,

On Thu, Oct 8, 2009 at 11:25 AM, Le Nguyen Thach <nevilarus at gmail.com> wrote:
> Hello
> I follow the guide on OpenNebula Site to install and config OpenNebula in my
> small Cluster. I have just two node, one acts as a front-end and one acts as
> cluster node. I use Ubuntu Jaunty Server Edition and Xen. Everything seemed
> going well . I've got  result like this:
>
> ID     NAME STAT CPU     MEM        HOSTNAME        TIME
>      25     vm04 runn   0  262144  172.28.181.191 00 00:55:13
> My VNet template:
>
> NAME   = "Public"
> TYPE   = FIXED
>
> BRIDGE = eth0
> LEASES = [IP=172.28.181.194,MAC=50:20:20:20:20:20]

If you don't need a specific MAC address do not specify it as
OpenNebula will generate one for you. It will be also specially
crafted so the network vmcontext script knows what IP does the machine
have.

>
> My VM template:
>
> NAME   = vm04
> CPU    = 0.5
> MEMORY = 256
>
> OS      = [
>         kernel = "/boot/vmlinuz-2.6.28-11-server",
>         initrd = "/boot/initrd.img-2.6.28-11-server",
>         root   = "sda1" ]
>
>
> DISK   = [
>   source   = "/var/lib/one/images/feisty_base.img",
>   target   = "sda1",
>   readonly = "no" ]
> NIC    = [ NETWORK = "Public" ]
>
> GRAPHICS = [type="vnc",listen="127.0.0.1",port="-1"]
>
> But I cannot access to the VM by using SSH. At first, I think my problem is
> in my network config. But when I log on to the cluster-node and tried 2
> access to the VM, I got:
>
> $ sudo xm list
>
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0   489     4     r-----
> 98696.9
> one-25                                      13   256     1     -b----
> 3.7
>
> $ sudo xm console 13
> ....
> [    0.346661] XENBUS: Device with no driver: device/vkbd/0
> [    0.346677] XENBUS: Device with no driver: device/vfb/0
> [    0.346689] XENBUS: Device with no driver: device/vbd/2049
> [    0.346701] XENBUS: Device with no driver: device/vif/0
> [    0.346713] XENBUS: Device with no driver: device/console/0
> [    0.346755]   Magic number: 1:252:3141
> [    0.346815] /build/buildd/linux-2.6.28/drivers/rtc/hctosys.c: unable to
> open
> rtc device (rtc0)
> [    0.346835] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> [    0.346849] EDD information not available.
> [    0.347988] Freeing unused kernel memory: 548k freed
> [    0.350884] Write protecting the kernel text: 4184k
> [    0.351931] Write protecting the kernel read-only data: 1552k
> Loading, please wait...
> Couldnt get a file descriptor referring to the console
> Begin: Loading essential drivers... ...
> Done.
> Begin: Running /scripts/init-premount ...
> Done.
> Begin: Mounting root file system... ...
> Begin: Running /scripts/local-top ...
> Done.
> Begin: Waiting for root file system... ...
> [   10.990061] XENBUS: Timeout connecting to device: device/vbd/2049 (state
> 3)
> Done.
> 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!
>
> I think my VM cannot boot, so It has nothing to do with the network.
> I don't know what's wrong here. I'm newbie in computer network and system.I
> appreciate any helps.

It cannot access sda1. Check that in the remote host you have
/var/lib/one/images/disk.0 and is readable.

> Btw, I'm stil confused about some attributes in the VM template : the kernel
> and initrd of OS point to the kernel on the host machine or VM image file ?

That files point to host machine files. Those parameters are the same
as XEN kernel and initrd parameters.

> The target of DISK must be the same in /etc/fstab (in VM image file) ? I 've
> searched over the Internet and someone say root of OS and target of DISK
> must be the same ?

You have to make fstab point to the correct device or it wont work. If
you tell in fstab that you have to mount a disk from /dev/sda1 you
should have the disk there.

Bye



-- 
Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org