Ok thanks, that is what I am thinking too. So, the question is : Can I run both Front and Node on the same host? I think so, but can you confirm?
On Thu, Dec 16, 2010 at 1:55 PM, Jaime Melis <j.me...@fdi.ucm.es> wrote: > 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'> > > <name>one-20</name> > > <uuid>34c3f015-0127-2bca-a9a8-646adf25d83e</uuid> > > <memory>65536</memory> > > <currentMemory>65536</currentMemory> > > <vcpu>1</vcpu> > > <os> > > <type arch='i686' machine='pc'>hvm</type> > > <boot dev='hd'/> > > </os> > > <clock offset='utc'/> > > <on_poweroff>destroy</on_poweroff> > > <on_reboot>restart</on_reboot> > > <on_crash>destroy</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? > >> >> >>>>> 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 | > >> >> >>>>>> (unix)["have"]+"fun"-0x60);} > >> >> >>>>>> Skype: gian.uberto.lauri | David Korn, AT&T > >> >> >>>>>> 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 > >> >> >>>>> R&D 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 > >> >> >>>> R&D 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 > >> >> >>> R&D 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 > >> >> >>> > >> >> >>> > >> >> >> > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> Jaime Melis, Cloud Technology Engineer/Researcher > >> >> >> DSA Research Group: web http://dsa-research.org and blog > >> >> >> http://blog.dsa-research.org > >> >> >> OpenNebula Open Source Toolkit for Cloud Computing: > >> >> >> http://www.OpenNebula.org > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> Jaime Melis, Cloud Technology Engineer/Researcher > >> >> DSA Research Group: web http://dsa-research.org and blog > >> >> http://blog.dsa-research.org > >> >> OpenNebula Open Source Toolkit for Cloud Computing: > >> >> http://www.OpenNebula.org > >> > > >> > > >> > > >> > -- > >> > Christophe Hamerling > >> > R&D 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 > >> > > >> > >> > >> > >> -- > >> Jaime Melis, Cloud Technology Engineer/Researcher > >> DSA Research Group: web http://dsa-research.org and blog > >> http://blog.dsa-research.org > >> OpenNebula Open Source Toolkit for Cloud Computing: > >> http://www.OpenNebula.org > >> _______________________________________________ > >> Users mailing list > >> Users@lists.opennebula.org > >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > > > > > > > -- > > Christophe Hamerling > > R&D 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 > > > > > > -- > Jaime Melis, Cloud Technology Engineer/Researcher > DSA Research Group: web http://dsa-research.org and blog > http://blog.dsa-research.org > OpenNebula Open Source Toolkit for Cloud Computing: > http://www.OpenNebula.org > -- Christophe Hamerling R&D 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