Hi cmasmas<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">bridge name bridge id STP enabled interfaces<br>eth0 8000.001e373597bc no peth0<br>
</blockquote><div><br>you should have in your network template then:<br>BRIDGE = eth0<br></div><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
I think I do need to specity a MAC-IP pair. Each VM must have the same IP, always, even if they are restarted. <br></blockquote><div><br>Follow these steps:<br><ul><li>enable saving: "SAVE = yes" in the vm template file.</li>
<li>contextualize the VM with the vmcontext scripts (follow the guide Tino showed you)<br></li><li>stop the vm with onevm stop <vmid></li><li>resume the vm whenever you want with onevm resume <vmid><br></li></ul>
As you can see you don't need DHCP. OpenNebula will generate the MAC, the vmcontext script running in your vms will grab the MAC and configure the IP accordingly. Since the MAC address won't change, the IP won't change either, even if you reboot the vm. By doing 'stop', you create a checkpoint and you can resume it later.<br>
<br>regards,<br>Jaime<br><br></div><div class="gmail_quote">On Wed, Oct 7, 2009 at 11:39 AM, cmasmas cmasmas <span dir="ltr"><<a href="mailto:cmasmas10@gmail.com" target="_blank">cmasmas10@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;">
<br><br><div class="gmail_quote">2009/10/5 Jaime Melis <span dir="ltr"><<a href="mailto:j.melis@fdi.ucm.es" target="_blank">j.melis@fdi.ucm.es</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi cmasmas,</blockquote><div><br>First of all, thanks for your answer.<br><br><br><br><br><br><br></div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>This parameter is actually very important. The way hypervisors work is to create a tun/tap device and to attach to it a bridge. The whole point of this is to permit your vm to be in the same network as the the selected device of the host. Execute 'brctl show' to see what bridges you have. <br>
</div></blockquote></div><div><br>bridge name bridge id STP enabled interfaces<br>eth0 8000.001e373597bc no peth0<br><br> </div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Regarding the network template, I would suggest that you didn't specify the MAC for each IP, like this:<br><br><i>LEASES = [IP=192.168.2.2]<br>LEASES = [IP=192.168.2.3]</i><br></div></blockquote></div><div><br>I think I do need to specity a MAC-IP pair. Each VM must have the same IP, always, even if they are restarted. <br>
<br>Maybe what I'm trying to do is not possible. I wanted to create a small network of 5-6 VM's to do some testing. I don't need access to Internet, but only the communication between the VM's. In a previous mail, I said about the problem with the DHCP server @ University.<br>
So, is it possible what I need without a DHCP server?<br><br>Thanks again, and sorry if I'm not clear.<br><font color="#888888"><br></font></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br>