Re: [one-users] Difficulty in accessing the virtual instance
Hi, I tried to use the contextualization in the template file. But everytime I create the instance, it fails at boot time saying tap device could not be connected. I belive this is the problem with xen. Is there any way I can change the driver of the iso file created by the opennebula when the instance is created. Following is the instance log - Mon Dec 20 15:23:14 2010 [DiM][I]: New VM state is ACTIVE. Mon Dec 20 15:23:14 2010 [LCM][I]: New VM state is PROLOG. Mon Dec 20 15:24:46 2010 [TM][I]: tm_clone.sh: prakhar-desktop:/var/lib/one//images/32e8224dac203aa2874167c7b180f666c1c77da2 192.168.145.71:/var/lib/one//48/images/disk.0 Mon Dec 20 15:24:46 2010 [TM][I]: tm_clone.sh: DST: /var/lib/one//48/images/disk.0 Mon Dec 20 15:24:46 2010 [TM][I]: tm_clone.sh: Creating directory /var/lib/one//48/images Mon Dec 20 15:24:46 2010 [TM][I]: tm_clone.sh: Executed /usr/bin/ssh 192.168.145.71 mkdir -p /var/lib/one//48/images. Mon Dec 20 15:24:46 2010 [TM][I]: tm_clone.sh: Cloning prakhar-desktop:/var/lib/one//images/32e8224dac203aa2874167c7b180f666c1c77da2 Mon Dec 20 15:24:46 2010 [TM][I]: tm_clone.sh: Executed /usr/bin/scp prakhar-desktop:/var/lib/one//images/32e8224dac203aa2874167c7b180f666c1c77da2 192.168.145.71:/var/lib/one//48/images/disk.0. Mon Dec 20 15:24:46 2010 [TM][I]: tm_clone.sh: Executed /usr/bin/ssh 192.168.145.71 chmod a+rw /var/lib/one//48/images/disk.0. Mon Dec 20 15:24:47 2010 [TM][I]: tm_mkswap.sh: Creating 1024Mb image in /var/lib/one//48/images/disk.1 Mon Dec 20 15:24:47 2010 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh 192.168.145.71 mkdir -p /var/lib/one//48/images. Mon Dec 20 15:24:47 2010 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh 192.168.145.71 /bin/dd if=/dev/zero of=/var/lib/one//48/images/disk.1 bs=1 count=1 seek=1024M. Mon Dec 20 15:24:47 2010 [TM][I]: tm_mkswap.sh: Initializing swap space Mon Dec 20 15:24:47 2010 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh 192.168.145.71 /sbin/mkswap /var/lib/one//48/images/disk.1. Mon Dec 20 15:24:47 2010 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh 192.168.145.71 chmod a+w /var/lib/one//48/images/disk.1. Mon Dec 20 15:24:48 2010 [TM][I]: tm_context.sh: Executed mkdir -p /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5/isofiles. Mon Dec 20 15:24:48 2010 [TM][I]: tm_context.sh: Executed cp -R /var/lib/one/48/context.sh /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5/isofiles. Mon Dec 20 15:24:48 2010 [TM][I]: tm_context.sh: Executed cp -R /home/prakhar/cloud/context/init.sh /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5/isofiles. Mon Dec 20 15:24:48 2010 [TM][I]: tm_context.sh: Executed cp -R /home/prakhar/cloud/context/init.sh /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5/isofiles. Mon Dec 20 15:24:48 2010 [TM][I]: tm_context.sh: Executed cp -R /root/.ssh/id_dsa.pub /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5/isofiles. Mon Dec 20 15:24:48 2010 [TM][I]: tm_context.sh: Executed /usr/bin/mkisofs -o /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5/disk.2 -J -R /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5/isofiles. Mon Dec 20 15:24:48 2010 [TM][I]: tm_context.sh: Executed /usr/bin/scp /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5/disk.2 192.168.145.71: /var/lib/one//48/images/disk.2. Mon Dec 20 15:24:48 2010 [TM][I]: tm_context.sh: Executed rm -rf /var/lib/one/b18484d61cd76a74c80d8576ecc7a1d5. Mon Dec 20 15:24:48 2010 [LCM][I]: New VM state is BOOT Mon Dec 20 15:24:48 2010 [VMM][I]: Generating deployment file: /var/lib/one/48/deployment.0 Mon Dec 20 15:26:36 2010 [VMM][I]: Command execution fail: 'if [ -x /var/tmp/one/vmm/xen/deploy ]; then /var/tmp/one/vmm/xen/deploy /var/lib/one//48/images/deployment.0; else exit 42; fi' Mon Dec 20 15:26:36 2010 [VMM][I]: STDERR follows. Mon Dec 20 15:26:36 2010 [VMM][I]: Error: Device 51744 (tap) could not be connected. Hotplug scripts not working. Mon Dec 20 15:26:36 2010 [VMM][I]: ExitCode: 1 Mon Dec 20 15:26:36 2010 [VMM][E]: Error deploying virtual machine: Error: Device 51744 (tap) could not be connected. Hotplug scripts not working. Mon Dec 20 15:26:36 2010 [DiM][I]: New VM state is FAILED Mon Dec 20 15:26:37 2010 [TM][W]: Ignored: LOG - 48 tm_delete.sh: Deleting /var/lib/one//48/images --- The deployment file is created as follows (Managed to copy it before it was deleted) name = 'one-48' #O CPU_CREDITS = 256 memory = '256' vcpus = '1' kernel = '/home/cloud/vm2/vmlinuz-2.6.27.21-0.1-xen' ramdisk = '/home/cloud/vm2/initrd-2.6.27.21-0.1-xen' root = '/dev/xvda' extra = 'xencons=tty' disk = [ 'file:/var/lib/one//48/images/disk.0,xvda,w', 'file:/var/lib/one//48/images/disk.1,xvdd,w', 'tap:aio:/var/lib/one//48/images/disk.2,xvdc,r', ]
Re: [one-users] Difficulty in accessing the virtual instance
You may need to setup the VM to get those parameters or set up an external DHCP server. http://opennebula.org/documentation:rel2.0:cong On Thu, Dec 16, 2010 at 1:35 PM, Prakhar Srivastava prakhar@gmail.com wrote: Hi, I am trying to install a opennebula cloud. I have one front end with ubuntu installed. I have successfully installed opennebula. I am able to run instances but cannot access them using the IP given in the network template file.. Following is my VM template file. NAME = test-vm MEMORY = 256 CPU = 1 OS = [ KERNEL = /boot/vmlinuz-2.6.32-5-xen-amd64, INITRD = /boot/initrd.img-2.6.32-5-xen-amd64, ROOT = /dev/xvda, KERNEL_CMD = ro xencons=tty console=tty1] # OS image, mapped to sda. DISK = [ IMAGE = Debian Lenny, TARGET = xvda, DRIVER = file:, READONLY = no ] # First DATABLOCK image, mapped to sde #DISK = [ IMAGE = Debian ] # Second DATABLOCK image, mapped to sdf #DISK = [ IMAGE = Experiment scripts ] # swap, sdd DISK = [ TYPE = swap, SIZE = 1024, TARGET = sdb, READONLY = no, DRIVER = file: ] #DISK = [ TYPE = fs, # SIZE = 4096, # FORMAT = ext3, # SAVE = yes, # TARGET = sdg ] NIC=[NETWORK=Public1] -- The network file is as follows NAME = Public1 TYPE = FIXED BRIDGE = eth0 LEASES = [IP=192.168.145.68] --- In opennebula , there is no option for specifying gateway, broadcast, netmask and dns server. How these values are communicated to the instance at boot time. I would like to know how networking is managed by opennebula front-end. Prakhar ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- 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 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Difficulty in accessing the virtual instance
Hi, I am trying to install a opennebula cloud. I have one front end with ubuntu installed. I have successfully installed opennebula. I am able to run instances but cannot access them using the IP given in the network template file.. Following is my VM template file. NAME = test-vm MEMORY = 256 CPU= 1 OS = [ KERNEL = /boot/vmlinuz-2.6.32-5-xen-amd64, INITRD = /boot/initrd.img-2.6.32-5-xen-amd64, ROOT = /dev/xvda, KERNEL_CMD = ro xencons=tty console=tty1] # OS image, mapped to sda. DISK = [ IMAGE = Debian Lenny, TARGET = xvda, DRIVER = file:, READONLY = no ] # First DATABLOCK image, mapped to sde #DISK = [ IMAGE = Debian ] # Second DATABLOCK image, mapped to sdf #DISK = [ IMAGE = Experiment scripts ] # swap, sdd DISK = [ TYPE = swap, SIZE = 1024, TARGET = sdb, READONLY = no, DRIVER = file: ] #DISK = [ TYPE = fs, # SIZE = 4096, # FORMAT = ext3, # SAVE = yes, # TARGET = sdg ] NIC=[NETWORK=Public1] -- The network file is as follows NAME = Public1 TYPE = FIXED BRIDGE = eth0 LEASES = [IP=192.168.145.68] --- In opennebula , there is no option for specifying gateway, broadcast, netmask and dns server. How these values are communicated to the instance at boot time. I would like to know how networking is managed by opennebula front-end. Prakhar ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
