HI All,<br><br>Just want to share the solution of this problem with you guys (Thanks Ettore)<br><br>1 - First of all, I didn`t define the context neither the target disk to be booting up.<br>2 - I was using a Full Virtualization image, and trying to deploy via OpenNebula a Paravirtualization.<br>
3 - I downloaded a CentOS image Paravirtualization, and got to raise a new VM using the Xen and also via OpenNebula (Thanks Ettore again).<br><br>So, everything is doing all right now. Going to start the scenarios runs and then will write an paper down. <br>
<br>Thanks for all support.<br><br>Cheers<br><br>Denis<br><br><div class="gmail_quote">On Fri, Mar 5, 2010 at 7:57 PM, Denis Ogura <span dir="ltr"><<a href="mailto:denisogura@gmail.com">denisogura@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi All,<br><br>One more question from me... I got to deploy the onehost, onvnet and also onevm, everything looks ok. following the results of each command:<br>
<br># onehost show 0<br>HOST 0 INFORMATION <br>
ID : 0 <br>NAME : cloud2 <br>STATE : MONITORED <br>IM_MAD : im_xen <br>VM_MAD : vmm_xen <br>
TM_MAD : tm_ssh <br><br>HOST SHARES <br>MAX MEM : 3931136 <br>USED MEM (REAL) : 1099776 <br>
USED MEM (ALLOCATED) : 524288 <br>MAX CPU : 400 <br>USED CPU (REAL) : 1 <br>USED CPU (ALLOCATED) : 100 <br>RUNNING VMS : 1 <br>
<br>MONITORING INFORMATION <br>ARCH=i686<br>CPUSPEED=2300<br>FREECPU=399<br>FREEMEMORY=2831360<br>HOSTNAME=cloud2<br>HYPERVISOR=xen<br>MODELNAME=AMD Phenom(tm) 9650 Quad-Core Processor<br>
NETRX=0<br>NETTX=0<br>TOTALCPU=400<br>TOTALMEMORY=3931136<br>USEDCPU=1<br>USEDMEMORY=1099776<br><br># onevnet show 0<br>VIRTUAL NETWORK 0 INFORMATION <br>ID: : 0 <br>
UID: : 0 <br><br>VIRTUAL NETWORK TEMPLATE <br>BRIDGE=br0<br>LEASES=[ IP=192.168.0.30, MAC=50:20:20:20:20:20 ]<br>LEASES=[ IP=192.168.0.31, MAC=50:20:20:20:20:21 ]<br>
LEASES=[ IP=192.168.0.32, MAC=50:20:20:20:20:22 ]<br>LEASES=[ IP=192.168.0.33, MAC=50:20:20:20:20:23 ]<br>LEASES=[ IP=192.168.0.34, MAC=50:20:20:20:20:24 ]<br>NAME=cloudnet<br>TYPE=FIXED<br><br>LEASES INFORMATION <br>
LEASE=[ IP=192.168.0.30, MAC=50:20:20:20:20:20, USED=1, VID=4 ]<br>LEASE=[ IP=192.168.0.31, MAC=50:20:20:20:20:21, USED=0, VID=-1 ]<br>LEASE=[ IP=192.168.0.32, MAC=50:20:20:20:20:22, USED=0, VID=-1 ]<br>LEASE=[ IP=192.168.0.33, MAC=50:20:20:20:20:23, USED=0, VID=-1 ]<br>
LEASE=[ IP=192.168.0.34, MAC=50:20:20:20:20:24, USED=0, VID=-1 ]<br><br># onevm show 4<br>VIRTUAL MACHINE 4 INFORMATION <br>ID : 4 <br>NAME : vmopensuse-2 <br>
STATE : ACTIVE <br>LCM_STATE : RUNNING <br>START TIME : 03/05 17:49:30 <br>END TIME : - <br>DEPLOY ID: : one-4 <br><br>VIRTUAL MACHINE TEMPLATE <br>
CPU=1<br>DISK=[<br> READONLY=no,<br> SOURCE=/var/lib/xen/images/opensuse11/disk0,<br> TARGET=sda ]<br>GRAPHICS=[<br> LISTEN=127.0.0.1,<br> PORT=5900,<br> TYPE=vnc ]<br>MEMORY=512<br>NAME=vmopensuse-2<br>NIC=[<br> BRIDGE=br0,<br>
IP=192.168.0.30,<br> MAC=50:20:20:20:20:20,<br> NETWORK=cloudnet,<br> VNID=0 ]<br>OS=[<br> INITRD=/boot/initrd-xen,<br> KERNEL=/boot/vmlinuz-xen,<br> ROOT=sda ]<br>VMID=4<br><br> # ping 192.168.0.30<br>PING 192.168.0.30 (192.168.0.30) 56(84) bytes of data.<br>
^C<br>--- 192.168.0.30 ping statistics ---<br>2 packets transmitted, 0 received, 100% packet loss, time 1010ms<br><br># ssh <a href="mailto:root@192.168.0.30" target="_blank">root@192.168.0.30</a><br>ssh: connect to host 192.168.0.30 port 22: No route to host<br>
<br>However, I can`t make the ip address get on the br0. The Virtual machine assign the IP from the onevnet, but it`s not pingagle or reachable using the ssh. From the other hand, the using the XEN manager, I can reach the template image VM without any problem.<br>
<br>One question, in XEN I`m the Full Virtualization, instead of Paravirtualization... Is might be a possibly problem? How can I troubleshoot this network issue?<br><br>Thanks<br><font color="#888888"><br>Denis<br><br>
</font></blockquote></div><br>