[one-users] The vnet is not reachable

[Ettore Enrico Delfino Ligorio]

Hi Denis,

Did you have a dhcp server to assing an ip for the virtual machine?

Or, did you pass the ip in the context inside the template used by OpenNebula?

These two are the easiest ways to complete the setup of the network.

If you decide to use dhcp for some OpenNebula vnet, could be useful
setup the dhcp to marry the mac and ips. Also, the nics of virtual
machine image must be configured to use dhcp at boot.

If you use the context, take a look at
http://www.opennebula.org/documentation:rel1.4:cong

For troubleshoot, you can:

1-) Logon on xen physical host, where the virtual machine is running;

2-) Use "xm list" to get the id of virtual machine;

3-) xm console <id_from_step_2>

4-) Logon on virtual machine and check the network configuration.

Can you send us the template of virtual machine

PS: There is a convention about the mac address of xen nic must starts
with 00:16:3E.

Best regards
--
Ettore Enrico Delfino Ligorio

On Fri, Mar 5, 2010 at 7:57 PM, Denis Ogura <denisogura at gmail.com> wrote:
> Hi All,
>
> One more question from me... I got to deploy the onehost, onvnet and also
> onevm, everything looks ok. following the results of each command:
>
> # onehost show 0
> HOST 0
> INFORMATION
> ID                    : 0
> NAME                  : cloud2
> STATE                 : MONITORED
> IM_MAD                : im_xen
> VM_MAD                : vmm_xen
> TM_MAD                : tm_ssh
>
> HOST
> SHARES
> MAX MEM               : 3931136
> USED MEM (REAL)       : 1099776
> USED MEM (ALLOCATED)  : 524288
> MAX CPU               : 400
> USED CPU (REAL)       : 1
> USED CPU (ALLOCATED)  : 100
> RUNNING VMS           : 1
>
> MONITORING
> INFORMATION
> ARCH=i686
> CPUSPEED=2300
> FREECPU=399
> FREEMEMORY=2831360
> HOSTNAME=cloud2
> HYPERVISOR=xen
> MODELNAME=AMD Phenom(tm) 9650 Quad-Core Processor
> NETRX=0
> NETTX=0
> TOTALCPU=400
> TOTALMEMORY=3931136
> USEDCPU=1
> USEDMEMORY=1099776
>
> # onevnet show 0
> VIRTUAL NETWORK 0
> INFORMATION
> ID:       : 0
> UID:      : 0
>
> VIRTUAL NETWORK
> TEMPLATE
> BRIDGE=br0
> LEASES=[ IP=192.168.0.30, MAC=50:20:20:20:20:20 ]
> LEASES=[ IP=192.168.0.31, MAC=50:20:20:20:20:21 ]
> LEASES=[ IP=192.168.0.32, MAC=50:20:20:20:20:22 ]
> LEASES=[ IP=192.168.0.33, MAC=50:20:20:20:20:23 ]
> LEASES=[ IP=192.168.0.34, MAC=50:20:20:20:20:24 ]
> NAME=cloudnet
> TYPE=FIXED
>
> LEASES
> INFORMATION
> LEASE=[ IP=192.168.0.30, MAC=50:20:20:20:20:20, USED=1, VID=4 ]
> LEASE=[ IP=192.168.0.31, MAC=50:20:20:20:20:21, USED=0, VID=-1 ]
> LEASE=[ IP=192.168.0.32, MAC=50:20:20:20:20:22, USED=0, VID=-1 ]
> LEASE=[ IP=192.168.0.33, MAC=50:20:20:20:20:23, USED=0, VID=-1 ]
> LEASE=[ IP=192.168.0.34, MAC=50:20:20:20:20:24, USED=0, VID=-1 ]
>
> # onevm show 4
> VIRTUAL MACHINE 4
> INFORMATION
> ID             : 4
> NAME           : vmopensuse-2
> STATE          : ACTIVE
> LCM_STATE      : RUNNING
> START TIME     : 03/05 17:49:30
> END TIME       : -
> DEPLOY ID:     : one-4
>
> VIRTUAL MACHINE
> TEMPLATE
> CPU=1
> DISK=[
>   READONLY=no,
>   SOURCE=/var/lib/xen/images/opensuse11/disk0,
>   TARGET=sda ]
> GRAPHICS=[
>   LISTEN=127.0.0.1,
>   PORT=5900,
>   TYPE=vnc ]
> MEMORY=512
> NAME=vmopensuse-2
> NIC=[
>   BRIDGE=br0,
>   IP=192.168.0.30,
>   MAC=50:20:20:20:20:20,
>   NETWORK=cloudnet,
>   VNID=0 ]
> OS=[
>   INITRD=/boot/initrd-xen,
>   KERNEL=/boot/vmlinuz-xen,
>   ROOT=sda ]
> VMID=4
>
>  # ping 192.168.0.30
> PING 192.168.0.30 (192.168.0.30) 56(84) bytes of data.
> ^C
> --- 192.168.0.30 ping statistics ---
> 2 packets transmitted, 0 received, 100% packet loss, time 1010ms
>
> # ssh root at 192.168.0.30
> ssh: connect to host 192.168.0.30 port 22: No route to host
>
> 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.
>
> 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?
>
> Thanks
>
> Denis
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>