Re: [one-users] Cannot connect to VM
Hi Christophe, If I understand correctly you're trying with the ttylinux image at: http://dev.opennebula.org/attachments/download/170/ttylinux.tar.gz correct? I have downloaded it again and tested it and it works for me. Could it be that yout image is corrupt? The md5sum should be: 04c7d00e88fa66d9aaa34d9cf8ad6aaa ttylinux.img If you're trying this with the correct image, can you send us the output of virsh dumpxl of the running vm? virsh -c qemu:///system dumpxl one-VMID Regards, Jaime On Thu, Dec 16, 2010 at 10:24 AM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Hi all, So you are right, something looks wrong in the ttylinux image. I am able to connect to the VM with VNC and it seems to have some problems with LILO : Booting from Hard Disk... LILO - Keytable read/checksum error and nothing more... :( Attached is the screenshot of VNC viewer window. On Wed, Dec 15, 2010 at 7:07 PM, Jaime Melis j.me...@fdi.ucm.es wrote: No, launch the vncviewer from your desktop PC, connecting to your worker node (which is running the VM): vncviewer 192.168.2.61::5900 Regards, Jaime On Wed, Dec 15, 2010 at 6:54 PM, Christophe Hamerling - Petals Link chamerling.eb...@gmail.com wrote: Ok i Will try this. I need to launch vnc viewer from node? Le 15 déc. 2010 à 18:06, Jaime Melis j.me...@fdi.ucm.es a écrit : Hi Christophe, I've been reading the thread but I think your configuration looks correct. Can you give it a shot at using VNC to see if the VM is booting up correctly? Maybe there's a problem with the VM... Add the following to your ONE template: GRAPHICS = [ TYPE = vnc, LISTEN = 0.0.0.0, PORT = 5900] Start the VM and connect to it via a VNC client (for instance vncviewer). Inspect the VM to see if there's a problem with it. Regards, Jaime On Wed, Dec 15, 2010 at 4:47 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: I am wondering if the problem does not also comes from the virtual network configuration. Here is my configuration : I am at home, my LAN address is 192.168.2.0/255.255.255.0 . GW is 192.168.2.1 My front address is 192.168.2.60 and the node one is 192.168.2.61 I tried to setup a bridge on the node, it seems to work (refer to my previous mails). I try to create a VM and to reach it at 192.168.2.71 but I am wondering now if it is possible to access a VM network from my laptop for exemple? How can I say to opennebula that I want to 'publish' VMs on my LAN? Is PUBLIC = YES is enough in the network configuration file? Do I need to put the front as a gateway somewhere, or another host? Thanks a lot Christophe On Wed, Dec 15, 2010 at 3:59 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a link between the MAC address defined in the VM and with the ones listed with ifconfig on the node? I do not have any. On Wed, Dec 15, 2010 at 3:46 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a web page where the network configuration on front and nodes is described? The only thing that I can find is at http://marianmi.comp.nus.edu.sg/2010/08/opennebula-installation-and-configuration-guide.php I really think that it is a network configuration problem. Here is what I did : Front : eth0 = 192.168.2.60 On the Node : br0 = 192.168.2.61 The gateway defined to 192.168.2.60, not sure about that. Using my internet box as gateway does not work too. I defined a LEASES address out of my DHCP range. When the VM is starting, I can see on the node a new network interface named vnet0 with the same mac address of my bridge. Is it ok? Before the VM start, the br0 mac address is the same as eth0... Is this a normal behaviour? Here is my ifconfig log br0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21 inet adr:192.168.2.61 Bcast:192.168.2.255 Masque:255.255.255.0 adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:787 errors:0 dropped:0 overruns:0 frame:0 TX packets:500 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:126978 (124.0 KiB) TX bytes:81984 (80.0 KiB) eth0 Link encap:Ethernet HWaddr 08:00:27:d7:f0:fd adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1268 errors:0 dropped:0 overruns:0 frame:0 TX packets:506 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:188739 (184.3 KiB) TX bytes:82452 (80.5 KiB) lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte
Re: [one-users] Cannot connect to VM
md5 SUM is OK. Here is the dump : debian-node01:~# virsh -c qemu:///system dumpxml one-20 domain type='kvm' id='1' nameone-20/name uuid34c3f015-0127-2bca-a9a8-646adf25d83e/uuid memory65536/memory currentMemory65536/currentMemory vcpu1/vcpu os type arch='i686' machine='pc'hvm/type boot dev='hd'/ /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/srv/cloud/one/var//20/images/disk.0'/ target dev='hda' bus='ide'/ /disk interface type='bridge' mac address='02:00:c0:a8:02:47'/ source bridge='br0'/ target dev='vnet0'/ /interface input type='mouse' bus='ps2'/ graphics type='vnc' port='5900' autoport='no' listen='0.0.0.0'/ /devices /domain On Thu, Dec 16, 2010 at 11:52 AM, Jaime Melis j.me...@fdi.ucm.es wrote: Hi Christophe, If I understand correctly you're trying with the ttylinux image at: http://dev.opennebula.org/attachments/download/170/ttylinux.tar.gz correct? I have downloaded it again and tested it and it works for me. Could it be that yout image is corrupt? The md5sum should be: 04c7d00e88fa66d9aaa34d9cf8ad6aaa ttylinux.img If you're trying this with the correct image, can you send us the output of virsh dumpxl of the running vm? virsh -c qemu:///system dumpxl one-VMID Regards, Jaime On Thu, Dec 16, 2010 at 10:24 AM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Hi all, So you are right, something looks wrong in the ttylinux image. I am able to connect to the VM with VNC and it seems to have some problems with LILO : Booting from Hard Disk... LILO - Keytable read/checksum error and nothing more... :( Attached is the screenshot of VNC viewer window. On Wed, Dec 15, 2010 at 7:07 PM, Jaime Melis j.me...@fdi.ucm.es wrote: No, launch the vncviewer from your desktop PC, connecting to your worker node (which is running the VM): vncviewer 192.168.2.61::5900 Regards, Jaime On Wed, Dec 15, 2010 at 6:54 PM, Christophe Hamerling - Petals Link chamerling.eb...@gmail.com wrote: Ok i Will try this. I need to launch vnc viewer from node? Le 15 déc. 2010 à 18:06, Jaime Melis j.me...@fdi.ucm.es a écrit : Hi Christophe, I've been reading the thread but I think your configuration looks correct. Can you give it a shot at using VNC to see if the VM is booting up correctly? Maybe there's a problem with the VM... Add the following to your ONE template: GRAPHICS = [ TYPE= vnc, LISTEN = 0.0.0.0, PORT= 5900] Start the VM and connect to it via a VNC client (for instance vncviewer). Inspect the VM to see if there's a problem with it. Regards, Jaime On Wed, Dec 15, 2010 at 4:47 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: I am wondering if the problem does not also comes from the virtual network configuration. Here is my configuration : I am at home, my LAN address is 192.168.2.0/255.255.255.0 . GW is 192.168.2.1 My front address is 192.168.2.60 and the node one is 192.168.2.61 I tried to setup a bridge on the node, it seems to work (refer to my previous mails). I try to create a VM and to reach it at 192.168.2.71 but I am wondering now if it is possible to access a VM network from my laptop for exemple? How can I say to opennebula that I want to 'publish' VMs on my LAN? Is PUBLIC = YES is enough in the network configuration file? Do I need to put the front as a gateway somewhere, or another host? Thanks a lot Christophe On Wed, Dec 15, 2010 at 3:59 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a link between the MAC address defined in the VM and with the ones listed with ifconfig on the node? I do not have any. On Wed, Dec 15, 2010 at 3:46 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a web page where the network configuration on front and nodes is described? The only thing that I can find is at http://marianmi.comp.nus.edu.sg/2010/08/opennebula-installation-and-configuration-guide.php I really think that it is a network configuration problem. Here is what I did : Front : eth0 = 192.168.2.60 On the Node : br0 = 192.168.2.61 The gateway defined to 192.168.2.60, not sure about that. Using my internet box as gateway does not work too. I defined a LEASES address out of my DHCP range. When the VM is starting, I can see on the node a new network interface named vnet0 with the same mac address of my bridge. Is it ok? Before the VM start, the br0 mac address is the same as eth0... Is this a normal behaviour?
Re: [one-users] Cannot connect to VM
Hi Christophe, Your deployment file seems correct. You said in your first email: My environment : libvirt/KVM on Debian 5 (In fact the Debian Node runs on top of virtual box, I hope that it is not a problem). We are thinking the problem might be that. In order to discard that possibility, could you by any chance try to virtualize on a physical host? In any case we are positive your network configuration is OK, and your OpenNebula configuration is also OK. The problem here is the hypervisor, which is not working correctly. regards, Jaime On Thu, Dec 16, 2010 at 1:26 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: md5 SUM is OK. Here is the dump : debian-node01:~# virsh -c qemu:///system dumpxml one-20 domain type='kvm' id='1' nameone-20/name uuid34c3f015-0127-2bca-a9a8-646adf25d83e/uuid memory65536/memory currentMemory65536/currentMemory vcpu1/vcpu os type arch='i686' machine='pc'hvm/type boot dev='hd'/ /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/srv/cloud/one/var//20/images/disk.0'/ target dev='hda' bus='ide'/ /disk interface type='bridge' mac address='02:00:c0:a8:02:47'/ source bridge='br0'/ target dev='vnet0'/ /interface input type='mouse' bus='ps2'/ graphics type='vnc' port='5900' autoport='no' listen='0.0.0.0'/ /devices /domain On Thu, Dec 16, 2010 at 11:52 AM, Jaime Melis j.me...@fdi.ucm.es wrote: Hi Christophe, If I understand correctly you're trying with the ttylinux image at: http://dev.opennebula.org/attachments/download/170/ttylinux.tar.gz correct? I have downloaded it again and tested it and it works for me. Could it be that yout image is corrupt? The md5sum should be: 04c7d00e88fa66d9aaa34d9cf8ad6aaa ttylinux.img If you're trying this with the correct image, can you send us the output of virsh dumpxl of the running vm? virsh -c qemu:///system dumpxl one-VMID Regards, Jaime On Thu, Dec 16, 2010 at 10:24 AM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Hi all, So you are right, something looks wrong in the ttylinux image. I am able to connect to the VM with VNC and it seems to have some problems with LILO : Booting from Hard Disk... LILO - Keytable read/checksum error and nothing more... :( Attached is the screenshot of VNC viewer window. On Wed, Dec 15, 2010 at 7:07 PM, Jaime Melis j.me...@fdi.ucm.es wrote: No, launch the vncviewer from your desktop PC, connecting to your worker node (which is running the VM): vncviewer 192.168.2.61::5900 Regards, Jaime On Wed, Dec 15, 2010 at 6:54 PM, Christophe Hamerling - Petals Link chamerling.eb...@gmail.com wrote: Ok i Will try this. I need to launch vnc viewer from node? Le 15 déc. 2010 à 18:06, Jaime Melis j.me...@fdi.ucm.es a écrit : Hi Christophe, I've been reading the thread but I think your configuration looks correct. Can you give it a shot at using VNC to see if the VM is booting up correctly? Maybe there's a problem with the VM... Add the following to your ONE template: GRAPHICS = [ TYPE = vnc, LISTEN = 0.0.0.0, PORT = 5900] Start the VM and connect to it via a VNC client (for instance vncviewer). Inspect the VM to see if there's a problem with it. Regards, Jaime On Wed, Dec 15, 2010 at 4:47 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: I am wondering if the problem does not also comes from the virtual network configuration. Here is my configuration : I am at home, my LAN address is 192.168.2.0/255.255.255.0 . GW is 192.168.2.1 My front address is 192.168.2.60 and the node one is 192.168.2.61 I tried to setup a bridge on the node, it seems to work (refer to my previous mails). I try to create a VM and to reach it at 192.168.2.71 but I am wondering now if it is possible to access a VM network from my laptop for exemple? How can I say to opennebula that I want to 'publish' VMs on my LAN? Is PUBLIC = YES is enough in the network configuration file? Do I need to put the front as a gateway somewhere, or another host? Thanks a lot Christophe On Wed, Dec 15, 2010 at 3:59 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a link between the MAC address defined in the VM and with the ones listed with ifconfig on the node? I do not have any. On Wed, Dec 15, 2010 at 3:46 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a web page where the network configuration on front and nodes is
Re: [one-users] Cannot connect to VM
[My apologies for breaking the threading informations]
CH == Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com writes:
CH On Tue, Dec 14, 2010 at 11:29 PM, carsten.friedr...@csiro.au
CH wrote:
I think your problem is that the ttylinux VM does not configure its
network card.
I agree with this opinion. If the ttyLinux TCP/IP stack does not know
what is the IP to use, it can not recognize inbound packets as such
and will discard them.
CH I was really hoping that the VM provided there
CH http://www.opennebula.org/documentation:rel2.0:vmg works. So I
CH think (and hope) that I have a configuration issue or I do not
CH understand this part.
What appens is that, for what I understood:
The contextualization infos(*) are automatically inserted in a shell
script contained in small iso9660 image that the ttyLinux instance
mounts.
(*) you do not need a context section in your vm definition, network
values come from the network you defined.
This script contains some variable definition, one of which holds the
IP address leased to the vm; a script in ttyLinux will source this
file and create the redhattish sysconfig/network-script file that will
be used when the /etc/init.d/network start command is issued by init -
throught the symbolic link in one of the rc(runlevel).d.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One Liner, 1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Cannot connect to VM
What I understand is that the init.sh script provided in
http://dev.opennebula.org/attachments/download/170/ttylinux.tar.gz is just
useful in context based VM and is not used in my case.
Where can I look to the VM configuration file once it is started? Is iy
exploded somewhere so I can have a look to files?
On Wed, Dec 15, 2010 at 10:46 AM, Gian Uberto Lauri sa...@eng.it wrote:
[My apologies for breaking the threading informations]
CH == Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com writes:
CH On Tue, Dec 14, 2010 at 11:29 PM, carsten.friedr...@csiro.au
CH wrote:
I think your problem is that the ttylinux VM does not configure its
network card.
I agree with this opinion. If the ttyLinux TCP/IP stack does not know
what is the IP to use, it can not recognize inbound packets as such
and will discard them.
CH I was really hoping that the VM provided there
CH http://www.opennebula.org/documentation:rel2.0:vmg works. So I
CH think (and hope) that I have a configuration issue or I do not
CH understand this part.
What appens is that, for what I understood:
The contextualization infos(*) are automatically inserted in a shell
script contained in small iso9660 image that the ttyLinux instance
mounts.
(*) you do not need a context section in your vm definition, network
values come from the network you defined.
This script contains some variable definition, one of which holds the
IP address leased to the vm; a script in ttyLinux will source this
file and create the redhattish sysconfig/network-script file that will
be used when the /etc/init.d/network start command is issued by init -
throught the symbolic link in one of the rc(runlevel).d.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One Liner, 1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Christophe Hamerling
RD Engineer Project Leader
Petals Link - SOA open-source company
OW2 PEtALS SOA Suite Comitter
Skype : christophe.hamerling
Jabber : chamerl...@jabber.org
Blog : http://chamerling.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Cannot connect to VM
[My apologies for breaking the threading informations]
CH What I understand is that the init.sh script provided in
CH http://dev.opennebula.org/attachments/download/170/ttylinux.tar.gz
CH is just useful in context based VM and is not used in my case.
CH Where can I look to the VM configuration file once it is started?
CH Is iy exploded somewhere so I can have a look to files?
The content of the script that's run on the first boot of the VM after
sourcing the file in the iso image:
--8---
#!/bin/bash
#
# chkconfig: 2345 10 90
# description: network reconfigure
#
# -- #
# Copyright 2002-2009, Distributed Systems Architecture Group, Universidad #
# Complutense de Madrid (dsa-research.org) #
##
# Licensed under the Apache License, Version 2.0 (the License); you may#
# not use this file except in compliance with the License. You may obtain#
# a copy of the License at #
##
# http://www.apache.org/licenses/LICENSE-2.0 #
##
# Unless required by applicable law or agreed to in writing, software#
# distributed under the License is distributed on an AS IS BASIS, #
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. #
# See the License for the specific language governing permissions and#
# limitations under the License. #
#--- #
# Gets IP address from a given MAC
mac2ip() {
mac=$1
let ip_a=0x`echo $mac | cut -d: -f 3`
let ip_b=0x`echo $mac | cut -d: -f 4`
let ip_c=0x`echo $mac | cut -d: -f 5`
let ip_d=0x`echo $mac | cut -d: -f 6`
ip=$ip_a.$ip_b.$ip_c.$ip_d
echo $ip
}
# Gets the network part of an IP
get_network() {
IP=$1
echo $IP | cut -d'.' -f1,2,3
}
get_interfaces() {
IFCMD=/sbin/ifconfig -a
$IFCMD | grep ^eth | sed 's/ *Link encap:Ethernet.*HWaddr /-/g'
}
get_dev() {
echo $1 | cut -d'-' -f 1
}
get_mac() {
echo $1 | cut -d'-' -f 2
}
gen_hosts() {
NETWORK=$1
echo 127.0.0.1 localhost
for n in `seq -w 01 99`; do
n2=`echo $n | sed 's/^0*//'`
echo ${NETWORK}.$n2 cluster${n}
done
}
gen_exports() {
NETWORK=$1
echo /images ${NETWORK}.0/255.255.255.0(rw,async,no_subtree_check)
}
gen_hostname() {
MAC=$1
NUM=`mac2ip $MAC | cut -d'.' -f4`
NUM2=`echo 00$NUM | sed 's/.*\(..\)/\1/'`
echo cluster$NUM2
}
gen_interface() {
DEV_MAC=$1
DEV=`get_dev $DEV_MAC`
MAC=`get_mac $DEV_MAC`
IP=`mac2ip $MAC`
# dumping the values into the reddattish file
cat EOT
DEVICE=$DEV
BOOTPROTO=none
HWADDR=$MAC
ONBOOT=yes
TYPE=Ethernet
NETMASK=255.255.255.0
IPADDR=$IP
EOT
if [ $DEV == eth0 ]; then
echo GATEWAY=$NETWORK.1
fi
echo
}
IFACES=`get_interfaces`
for i in $IFACES; do
MASTER_DEV_MAC=$i
DEV=`get_dev $i`
MAC=`get_mac $i`
IP=`mac2ip $MAC`
NETWORK=`get_network $IP`
done
# gen_hosts $NETWORK /etc/hosts
# gen_exports $NETWORK /etc/exports
# gen_hostname $MAC /etc/hostname
(
cat EOT
EOT
for i in $IFACES; do
gen_interface $i
done
) /etc/sysconfig/network-scripts/ifcfg-${DEV}
#ifdown $DEV
#ifup $DEV
exit $RETVAL
# /bin/hostname `cat /etc/hostname`
--8---
I have to investigate other means of accessing the VM console, since we plan
to use OpenNebula to offer Windows virtualization and this script does
not cope
with Windows bootstrap process AFAIK.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One Liner, 1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Cannot connect to VM
Ok, so I will check that the generated IP is the one expected from the
leases list based on this script algorithm.
Is the VM is exploded somewhere at startup? If yes, where?
On Wed, Dec 15, 2010 at 11:19 AM, Gian Uberto Lauri sa...@eng.it wrote:
[My apologies for breaking the threading informations]
CH What I understand is that the init.sh script provided in
CH http://dev.opennebula.org/attachments/download/170/ttylinux.tar.gz
CH is just useful in context based VM and is not used in my case.
CH Where can I look to the VM configuration file once it is started?
CH Is iy exploded somewhere so I can have a look to files?
The content of the script that's run on the first boot of the VM after
sourcing the file in the iso image:
--8---
#!/bin/bash
#
# chkconfig: 2345 10 90
# description: network reconfigure
#
#
-- #
# Copyright 2002-2009, Distributed Systems Architecture Group, Universidad
#
# Complutense de Madrid (dsa-research.org)
#
#
#
# Licensed under the Apache License, Version 2.0 (the License); you may
#
# not use this file except in compliance with the License. You may obtain
#
# a copy of the License at
#
#
#
# http://www.apache.org/licenses/LICENSE-2.0
#
#
#
# Unless required by applicable law or agreed to in writing, software
#
# distributed under the License is distributed on an AS IS BASIS,
#
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#
# See the License for the specific language governing permissions and
#
# limitations under the License.
#
#---
#
# Gets IP address from a given MAC
mac2ip() {
mac=$1
let ip_a=0x`echo $mac | cut -d: -f 3`
let ip_b=0x`echo $mac | cut -d: -f 4`
let ip_c=0x`echo $mac | cut -d: -f 5`
let ip_d=0x`echo $mac | cut -d: -f 6`
ip=$ip_a.$ip_b.$ip_c.$ip_d
echo $ip
}
# Gets the network part of an IP
get_network() {
IP=$1
echo $IP | cut -d'.' -f1,2,3
}
get_interfaces() {
IFCMD=/sbin/ifconfig -a
$IFCMD | grep ^eth | sed 's/ *Link encap:Ethernet.*HWaddr /-/g'
}
get_dev() {
echo $1 | cut -d'-' -f 1
}
get_mac() {
echo $1 | cut -d'-' -f 2
}
gen_hosts() {
NETWORK=$1
echo 127.0.0.1 localhost
for n in `seq -w 01 99`; do
n2=`echo $n | sed 's/^0*//'`
echo ${NETWORK}.$n2 cluster${n}
done
}
gen_exports() {
NETWORK=$1
echo /images ${NETWORK}.0/255.255.255.0(rw,async,no_subtree_check)
}
gen_hostname() {
MAC=$1
NUM=`mac2ip $MAC | cut -d'.' -f4`
NUM2=`echo 00$NUM | sed 's/.*\(..\)/\1/'`
echo cluster$NUM2
}
gen_interface() {
DEV_MAC=$1
DEV=`get_dev $DEV_MAC`
MAC=`get_mac $DEV_MAC`
IP=`mac2ip $MAC`
# dumping the values into the reddattish file
cat EOT
DEVICE=$DEV
BOOTPROTO=none
HWADDR=$MAC
ONBOOT=yes
TYPE=Ethernet
NETMASK=255.255.255.0
IPADDR=$IP
EOT
if [ $DEV == eth0 ]; then
echo GATEWAY=$NETWORK.1
fi
echo
}
IFACES=`get_interfaces`
for i in $IFACES; do
MASTER_DEV_MAC=$i
DEV=`get_dev $i`
MAC=`get_mac $i`
IP=`mac2ip $MAC`
NETWORK=`get_network $IP`
done
# gen_hosts $NETWORK /etc/hosts
# gen_exports $NETWORK /etc/exports
# gen_hostname $MAC /etc/hostname
(
cat EOT
EOT
for i in $IFACES; do
gen_interface $i
done
) /etc/sysconfig/network-scripts/ifcfg-${DEV}
#ifdown $DEV
#ifup $DEV
exit $RETVAL
# /bin/hostname `cat /etc/hostname`
--8---
I have to investigate other means of accessing the VM console, since we
plan
to use OpenNebula to offer Windows virtualization and this script does not
cope
with Windows bootstrap process AFAIK.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One Liner,
1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Christophe Hamerling
RD Engineer Project Leader
Petals Link - SOA open-source company
OW2 PEtALS SOA Suite Comitter
Skype : christophe.hamerling
Jabber : chamerl...@jabber.org
Blog : http://chamerling.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Cannot connect to VM
Is there a web page where the network configuration on front and nodes is
described? The only thing that I can find is at
http://marianmi.comp.nus.edu.sg/2010/08/opennebula-installation-and-configuration-guide.php
I really think that it is a network configuration problem. Here is what I
did :
Front : eth0 = 192.168.2.60
On the Node : br0 = 192.168.2.61
The gateway defined to 192.168.2.60, not sure about that. Using my internet
box as gateway does not work too.
I defined a LEASES address out of my DHCP range.
When the VM is starting, I can see on the node a new network interface named
vnet0 with the same mac address of my bridge. Is it ok?
Before the VM start, the br0 mac address is the same as eth0... Is this a
normal behaviour?
Here is my ifconfig log
br0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21
inet adr:192.168.2.61 Bcast:192.168.2.255 Masque:255.255.255.0
adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:787 errors:0 dropped:0 overruns:0 frame:0
TX packets:500 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:126978 (124.0 KiB) TX bytes:81984 (80.0 KiB)
eth0 Link encap:Ethernet HWaddr 08:00:27:d7:f0:fd
adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1268 errors:0 dropped:0 overruns:0 frame:0
TX packets:506 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:188739 (184.3 KiB) TX bytes:82452 (80.5 KiB)
loLink encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:2156 (2.1 KiB) TX bytes:2156 (2.1 KiB)
vnet0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21
adr inet6: fe80::2ff:daff:fe72:221/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:500
RX bytes:0 (0.0 B) TX bytes:38791 (37.8 KiB)
On Wed, Dec 15, 2010 at 11:37 AM, Gian Uberto Lauri sa...@eng.it wrote:
CH == Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com writes:
CH Ok, so I will check that the generated IP is the one expected from
CH the leases list based on this script algorithm. Is the VM is
CH exploded somewhere at startup? If yes, where?
No, it is not.
A _new_, temporary cd image is created on the fly and mounted at the
first boot, AFAIK.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One Liner,
1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Christophe Hamerling
RD Engineer Project Leader
Petals Link - SOA open-source company
OW2 PEtALS SOA Suite Comitter
Skype : christophe.hamerling
Jabber : chamerl...@jabber.org
Blog : http://chamerling.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Cannot connect to VM
Is there a link between the MAC address defined in the VM and with the ones
listed with ifconfig on the node? I do not have any.
On Wed, Dec 15, 2010 at 3:46 PM, Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com wrote:
Is there a web page where the network configuration on front and nodes is
described? The only thing that I can find is at
http://marianmi.comp.nus.edu.sg/2010/08/opennebula-installation-and-configuration-guide.php
I really think that it is a network configuration problem. Here is what I
did :
Front : eth0 = 192.168.2.60
On the Node : br0 = 192.168.2.61
The gateway defined to 192.168.2.60, not sure about that. Using my internet
box as gateway does not work too.
I defined a LEASES address out of my DHCP range.
When the VM is starting, I can see on the node a new network interface
named vnet0 with the same mac address of my bridge. Is it ok?
Before the VM start, the br0 mac address is the same as eth0... Is this a
normal behaviour?
Here is my ifconfig log
br0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21
inet adr:192.168.2.61 Bcast:192.168.2.255 Masque:255.255.255.0
adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:787 errors:0 dropped:0 overruns:0 frame:0
TX packets:500 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:126978 (124.0 KiB) TX bytes:81984 (80.0 KiB)
eth0 Link encap:Ethernet HWaddr 08:00:27:d7:f0:fd
adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1268 errors:0 dropped:0 overruns:0 frame:0
TX packets:506 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:188739 (184.3 KiB) TX bytes:82452 (80.5 KiB)
loLink encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:2156 (2.1 KiB) TX bytes:2156 (2.1 KiB)
vnet0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21
adr inet6: fe80::2ff:daff:fe72:221/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:500
RX bytes:0 (0.0 B) TX bytes:38791 (37.8 KiB)
On Wed, Dec 15, 2010 at 11:37 AM, Gian Uberto Lauri sa...@eng.it wrote:
CH == Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com writes:
CH Ok, so I will check that the generated IP is the one expected from
CH the leases list based on this script algorithm. Is the VM is
CH exploded somewhere at startup? If yes, where?
No, it is not.
A _new_, temporary cd image is created on the fly and mounted at the
first boot, AFAIK.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One
Liner, 1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Christophe Hamerling
RD Engineer Project Leader
Petals Link - SOA open-source company
OW2 PEtALS SOA Suite Comitter
Skype : christophe.hamerling
Jabber : chamerl...@jabber.org
Blog : http://chamerling.org
--
Christophe Hamerling
RD Engineer Project Leader
Petals Link - SOA open-source company
OW2 PEtALS SOA Suite Comitter
Skype : christophe.hamerling
Jabber : chamerl...@jabber.org
Blog : http://chamerling.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Cannot connect to VM
Hi Christophe,
I've been reading the thread but I think your configuration looks
correct. Can you give it a shot at using VNC to see if the VM is
booting up correctly? Maybe there's a problem with the VM...
Add the following to your ONE template:
GRAPHICS = [
TYPE= vnc,
LISTEN = 0.0.0.0,
PORT= 5900]
Start the VM and connect to it via a VNC client (for instance
vncviewer). Inspect the VM to see if there's a problem with it.
Regards,
Jaime
On Wed, Dec 15, 2010 at 4:47 PM, Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com wrote:
I am wondering if the problem does not also comes from the virtual network
configuration.
Here is my configuration :
I am at home, my LAN address is 192.168.2.0/255.255.255.0 . GW is
192.168.2.1
My front address is 192.168.2.60 and the node one is 192.168.2.61
I tried to setup a bridge on the node, it seems to work (refer to my
previous mails).
I try to create a VM and to reach it at 192.168.2.71 but I am wondering now
if it is possible to access a VM network from my laptop for exemple? How can
I say to opennebula that I want to 'publish' VMs on my LAN? Is PUBLIC = YES
is enough in the network configuration file? Do I need to put the front as a
gateway somewhere, or another host?
Thanks a lot
Christophe
On Wed, Dec 15, 2010 at 3:59 PM, Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com wrote:
Is there a link between the MAC address defined in the VM and with the
ones listed with ifconfig on the node? I do not have any.
On Wed, Dec 15, 2010 at 3:46 PM, Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com wrote:
Is there a web page where the network configuration on front and nodes is
described? The only thing that I can find is
at http://marianmi.comp.nus.edu.sg/2010/08/opennebula-installation-and-configuration-guide.php
I really think that it is a network configuration problem. Here is what I
did :
Front : eth0 = 192.168.2.60
On the Node : br0 = 192.168.2.61
The gateway defined to 192.168.2.60, not sure about that. Using my
internet box as gateway does not work too.
I defined a LEASES address out of my DHCP range.
When the VM is starting, I can see on the node a new network interface
named vnet0 with the same mac address of my bridge. Is it ok?
Before the VM start, the br0 mac address is the same as eth0... Is this a
normal behaviour?
Here is my ifconfig log
br0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21
inet adr:192.168.2.61 Bcast:192.168.2.255
Masque:255.255.255.0
adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:787 errors:0 dropped:0 overruns:0 frame:0
TX packets:500 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:126978 (124.0 KiB) TX bytes:81984 (80.0 KiB)
eth0 Link encap:Ethernet HWaddr 08:00:27:d7:f0:fd
adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1268 errors:0 dropped:0 overruns:0 frame:0
TX packets:506 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:188739 (184.3 KiB) TX bytes:82452 (80.5 KiB)
lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:2156 (2.1 KiB) TX bytes:2156 (2.1 KiB)
vnet0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21
adr inet6: fe80::2ff:daff:fe72:221/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:500
RX bytes:0 (0.0 B) TX bytes:38791 (37.8 KiB)
On Wed, Dec 15, 2010 at 11:37 AM, Gian Uberto Lauri sa...@eng.it wrote:
CH == Christophe Hamerling - Petals Link
christophe.hamerl...@petalslink.com writes:
CH Ok, so I will check that the generated IP is the one expected from
CH the leases list based on this script algorithm. Is the VM is
CH exploded somewhere at startup? If yes, where?
No, it is not.
A _new_, temporary cd image is created on the fly and mounted at the
first boot, AFAIK.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |
Re: [one-users] Cannot connect to VM
No, launch the vncviewer from your desktop PC, connecting to your worker node (which is running the VM): vncviewer 192.168.2.61::5900 Regards, Jaime On Wed, Dec 15, 2010 at 6:54 PM, Christophe Hamerling - Petals Link chamerling.eb...@gmail.com wrote: Ok i Will try this. I need to launch vnc viewer from node? Le 15 déc. 2010 à 18:06, Jaime Melis j.me...@fdi.ucm.es a écrit : Hi Christophe, I've been reading the thread but I think your configuration looks correct. Can you give it a shot at using VNC to see if the VM is booting up correctly? Maybe there's a problem with the VM... Add the following to your ONE template: GRAPHICS = [ TYPE = vnc, LISTEN = 0.0.0.0, PORT = 5900] Start the VM and connect to it via a VNC client (for instance vncviewer). Inspect the VM to see if there's a problem with it. Regards, Jaime On Wed, Dec 15, 2010 at 4:47 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: I am wondering if the problem does not also comes from the virtual network configuration. Here is my configuration : I am at home, my LAN address is 192.168.2.0/255.255.255.0 . GW is 192.168.2.1 My front address is 192.168.2.60 and the node one is 192.168.2.61 I tried to setup a bridge on the node, it seems to work (refer to my previous mails). I try to create a VM and to reach it at 192.168.2.71 but I am wondering now if it is possible to access a VM network from my laptop for exemple? How can I say to opennebula that I want to 'publish' VMs on my LAN? Is PUBLIC = YES is enough in the network configuration file? Do I need to put the front as a gateway somewhere, or another host? Thanks a lot Christophe On Wed, Dec 15, 2010 at 3:59 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a link between the MAC address defined in the VM and with the ones listed with ifconfig on the node? I do not have any. On Wed, Dec 15, 2010 at 3:46 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a web page where the network configuration on front and nodes is described? The only thing that I can find is at http://marianmi.comp.nus.edu.sg/2010/08/opennebula-installation-and-configuration-guide.php I really think that it is a network configuration problem. Here is what I did : Front : eth0 = 192.168.2.60 On the Node : br0 = 192.168.2.61 The gateway defined to 192.168.2.60, not sure about that. Using my internet box as gateway does not work too. I defined a LEASES address out of my DHCP range. When the VM is starting, I can see on the node a new network interface named vnet0 with the same mac address of my bridge. Is it ok? Before the VM start, the br0 mac address is the same as eth0... Is this a normal behaviour? Here is my ifconfig log br0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21 inet adr:192.168.2.61 Bcast:192.168.2.255 Masque:255.255.255.0 adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:787 errors:0 dropped:0 overruns:0 frame:0 TX packets:500 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:126978 (124.0 KiB) TX bytes:81984 (80.0 KiB) eth0 Link encap:Ethernet HWaddr 08:00:27:d7:f0:fd adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1268 errors:0 dropped:0 overruns:0 frame:0 TX packets:506 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:188739 (184.3 KiB) TX bytes:82452 (80.5 KiB) lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:2156 (2.1 KiB) TX bytes:2156 (2.1 KiB) vnet0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21 adr inet6: fe80::2ff:daff:fe72:221/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:226 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:500 RX bytes:0 (0.0 B) TX bytes:38791 (37.8 KiB) On Wed, Dec 15, 2010 at 11:37 AM, Gian Uberto Lauri sa...@eng.it wrote: CH == Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com writes: CH Ok, so I will check that the generated IP is the one expected from CH the leases list based on this script algorithm. Is the VM is CH exploded somewhere at startup? If yes, where? No, it is not. A _new_, temporary cd image is
Re: [one-users] Cannot connect to VM
Ok i Will try this. I need to launch vnc viewer from node? Le 15 déc. 2010 à 18:06, Jaime Melis j.me...@fdi.ucm.es a écrit : Hi Christophe, I've been reading the thread but I think your configuration looks correct. Can you give it a shot at using VNC to see if the VM is booting up correctly? Maybe there's a problem with the VM... Add the following to your ONE template: GRAPHICS = [ TYPE= vnc, LISTEN = 0.0.0.0, PORT= 5900] Start the VM and connect to it via a VNC client (for instance vncviewer). Inspect the VM to see if there's a problem with it. Regards, Jaime On Wed, Dec 15, 2010 at 4:47 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: I am wondering if the problem does not also comes from the virtual network configuration. Here is my configuration : I am at home, my LAN address is 192.168.2.0/255.255.255.0 . GW is 192.168.2.1 My front address is 192.168.2.60 and the node one is 192.168.2.61 I tried to setup a bridge on the node, it seems to work (refer to my previous mails). I try to create a VM and to reach it at 192.168.2.71 but I am wondering now if it is possible to access a VM network from my laptop for exemple? How can I say to opennebula that I want to 'publish' VMs on my LAN? Is PUBLIC = YES is enough in the network configuration file? Do I need to put the front as a gateway somewhere, or another host? Thanks a lot Christophe On Wed, Dec 15, 2010 at 3:59 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a link between the MAC address defined in the VM and with the ones listed with ifconfig on the node? I do not have any. On Wed, Dec 15, 2010 at 3:46 PM, Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com wrote: Is there a web page where the network configuration on front and nodes is described? The only thing that I can find is at http://marianmi.comp.nus.edu.sg/2010/08/opennebula-installation-and-configuration-guide.php I really think that it is a network configuration problem. Here is what I did : Front : eth0 = 192.168.2.60 On the Node : br0 = 192.168.2.61 The gateway defined to 192.168.2.60, not sure about that. Using my internet box as gateway does not work too. I defined a LEASES address out of my DHCP range. When the VM is starting, I can see on the node a new network interface named vnet0 with the same mac address of my bridge. Is it ok? Before the VM start, the br0 mac address is the same as eth0... Is this a normal behaviour? Here is my ifconfig log br0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21 inet adr:192.168.2.61 Bcast:192.168.2.255 Masque:255.255.255.0 adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:787 errors:0 dropped:0 overruns:0 frame:0 TX packets:500 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:126978 (124.0 KiB) TX bytes:81984 (80.0 KiB) eth0 Link encap:Ethernet HWaddr 08:00:27:d7:f0:fd adr inet6: fe80::a00:27ff:fed7:f0fd/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1268 errors:0 dropped:0 overruns:0 frame:0 TX packets:506 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:188739 (184.3 KiB) TX bytes:82452 (80.5 KiB) loLink encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:2156 (2.1 KiB) TX bytes:2156 (2.1 KiB) vnet0 Link encap:Ethernet HWaddr 00:ff:da:72:02:21 adr inet6: fe80::2ff:daff:fe72:221/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:226 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:500 RX bytes:0 (0.0 B) TX bytes:38791 (37.8 KiB) On Wed, Dec 15, 2010 at 11:37 AM, Gian Uberto Lauri sa...@eng.it wrote: CH == Christophe Hamerling - Petals Link christophe.hamerl...@petalslink.com writes: CH Ok, so I will check that the generated IP is the one expected from CH the leases list based on this script algorithm. Is the VM is CH exploded somewhere at startup? If yes, where? No, it is not. A _new_, temporary cd image is created on the fly and mounted at the first boot, AFAIK. -- ing. Gian Uberto Lauri Ricercatore / Reasearcher Divisione Ricerca ed Innovazione / Research Innovation Division gianuberto.la...@eng.it Engineering Ingegneria
