Thanks Guba,<br><br>I decided to contextualize my VMs, it's working so far. I think it is the easiest way.<br><br>I wanted to avoid contextualization because I had problems with scripts for CentOS in the past. I think that in CentOS you need more than just add the script with chkconfig, the system messes up the interfaces. OpenNebula comes with a contextualization ready to use with Debian, it was easy to enable it, since I changed all my VMs to Debian.<br>
<br><br>Cordially,<br><br>Antonio Carlos Furtado<br><br><div class="gmail_quote">On Mon, May 7, 2012 at 2:24 PM, Guba Sándor <span dir="ltr"><<a href="mailto:gubasanyi@gmail.com" target="_blank">gubasanyi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Opennebula calculate IP address from MAC address and it's show that
IP address as leased. However the DHCP server is running by libvirt
and it has no idea that it's need to assign IP by mac address so
it's assign IP by other metric. You can generate host file with
proper mac-ip pairs or contextualize vm-s or somebody know other way
to keep it synchronized.<br>
<br>
2012-05-07 18:10 keltezéssel, Antonio Carlos Salzvedel Furtado
Junior írta:
<blockquote type="cite"><div><div class="h5">Hello,<br>
<br>
<br>
I'm successfully being able to deploy VMs on my cloud, but there
is a problem with the IP addresses that OpenNebula reports to be
leased.<br>
<br>
The DHCP seems to work fine with the bridge. For instance, I have
a Debian running in a VM, which was given the IP 192.168.122.254.
<br>
This is the output of 'ifconfig -a' ( excluding loopback ):<br>
<br>
eth0 Link encap:Ethernet Endereço de HW 02:00:c0:a8:7a:02 <br>
inet end.: 192.168.122.244 Bcast:192.168.122.255
Masc:255.255.255.0<br>
endereço inet6: fe80::c0ff:fea8:7a02/64 Escopo:Link<br>
UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1<br>
RX packets:13 errors:0 dropped:0 overruns:0 frame:0<br>
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0<br>
colisões:0 txqueuelen:1000 <br>
RX bytes:1198 (1.1 KiB) TX bytes:1512 (1.4 KiB)<br>
IRQ:11 Endereço de E/S:0x8000 <br>
<br>
The MAC address is correct. It is the same as the output of onevm
show <VM NUMBER>:<br>
<br>
NIC=[<br>
BRIDGE=virbr0,<br>
IP=<a href="tel:192.168.122.2" value="+551921681222" target="_blank">192.168.122.2</a>,<br>
MAC=02:00:c0:a8:7a:02,<br>
NETWORK="Private LAN",<br>
NETWORK_ID=0,<br>
VLAN=NO ]<br>
<br>
I just don't know where OpenNebula got that IP address
<a href="tel:192.168.122.2" value="+551921681222" target="_blank">192.168.122.2</a>, shown above. 'arp -i virbr0' gives me the
following:<br>
<br>
Address HWtype HWaddress Flags
Mask Iface<br>
192.168.122.244 ether 02:00:c0:a8:7a:02
C virbr0<br>
<br>
<br>
<br>
The VM was not contextualized, but that is not necessary, right?
As far as I'm concerned, OpenNebula only defines the MAC ADDRESS,
but where does it take information about leases?<br>
<br>
ps.:Using KVM as hypervisor.<br>
<br>
Thanks in advance.<br>
<br>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">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><br clear="all"><br>-- <br>Antonio Carlos Furtado<br><br>