Hello<br>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:<br>
<br>ID NAME STAT CPU MEM HOSTNAME TIME<br> 25 vm04 runn 0 262144 172.28.181.191 00 00:55:13<br>My VNet template:<br><br><pre class="code">NAME = "Public"<br>TYPE = FIXED<br>
BRIDGE = eth0<br>LEASES = [IP=172.28.181.194,MAC=50:20:20:20:20:20]<br></pre><br>My VM template:<br><br>NAME = vm04<br>CPU = 0.5<br>MEMORY = 256<br><br>OS = [<br> kernel = "/boot/vmlinuz-2.6.28-11-server",<br>
initrd = "/boot/initrd.img-2.6.28-11-server",<br> root = "sda1" ]<br><br><br>DISK = [<br> source = "/var/lib/one/images/feisty_base.img",<br> target = "sda1",<br>
readonly = "no" ]<br>NIC = [ NETWORK = "Public" ]<br><br>GRAPHICS = [type="vnc",listen="127.0.0.1",port="-1"]<br><br>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:<br>
<br>$ sudo xm list<br><br>Name ID Mem VCPUs State Time(s)<br>Domain-0 0 489 4 r----- 98696.9<br>one-25 13 256 1 -b---- 3.7<br>
<br>$ sudo xm console 13<br>....<br>[ 0.346661] XENBUS: Device with no driver: device/vkbd/0<br>[ 0.346677] XENBUS: Device with no driver: device/vfb/0<br>[ 0.346689] XENBUS: Device with no driver: device/vbd/2049<br>
[ 0.346701] XENBUS: Device with no driver: device/vif/0<br>[ 0.346713] XENBUS: Device with no driver: device/console/0<br>[ 0.346755] Magic number: 1:252:3141<br>[ 0.346815] /build/buildd/linux-2.6.28/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)<br>
[ 0.346835] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found<br>[ 0.346849] EDD information not available.<br>[ 0.347988] Freeing unused kernel memory: 548k freed<br>[ 0.350884] Write protecting the kernel text: 4184k<br>
[ 0.351931] Write protecting the kernel read-only data: 1552k<br>Loading, please wait...<br>Couldnt get a file descriptor referring to the console<br>Begin: Loading essential drivers... ...<br>Done.<br>Begin: Running /scripts/init-premount ...<br>
Done.<br>Begin: Mounting root file system... ...<br>Begin: Running /scripts/local-top ...<br>Done.<br>Begin: Waiting for root file system... ...<br>[ 10.990061] XENBUS: Timeout connecting to device: device/vbd/2049 (state 3)<br>
Done.<br>Gave up waiting for root device. Common problems:<br> - Boot args (cat /proc/cmdline)<br> - Check rootdelay= (did the system wait long enough?)<br> - Check root= (did the system wait for the right device?)<br>
- Missing modules (cat /proc/modules; ls /dev)<br>ALERT! /dev/sda1 does not exist. Dropping to a shell!<br><br>I think my VM cannot boot, so It has nothing to do with the network.<br>I don't know what's wrong here. I'm newbie in computer network and system.I appreciate any helps. <br>
<br>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 ? 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 ? <br>
Can anyone explain it for me ?<br><br>Thanks & Regards,<br>Le Nguyen Thach<br>