[one-users] Virtual machine IP

[Steven Timm]

Do you have the latest one-context script from opennebula 2.0
included as part of your VM.. that is what is either
supposed to grab the IP that opennebula assigns through
contextualization, or
make it be the last 4 bytes of the MAC address.  At least that's
what I understand.

Is your image configured to get DHCP network otherwise?
If so, maybe that's where it is coming from, perhaps
via your libvirt configuration.  I have only seen the 192.168.122.*
libvirt virbr0 bridge used to do NAT networking and typically
it is only a 255.255.255.0 netmask meaning that 192.168.123.2
wouldn't be part of it.

Better to create a different bridge from virbr0 especially
for opennebula networking.. if you are doing KVM you will
have to do this by hand with brctl.

Steve Timm



On Tue, 7 Dec 2010, Zaina AFOULKI wrote:

>
> Hi,
>
> I'm experiencing the same issue with OpenNebula:
>
> I've a vnet defined by this template:
>
> NAME = "vnet1"
> TYPE = RANGED
> PUBLIC = NO
> BRIDGE = virbr0
> NETWORK_SIZE    = C
> NETWORK_ADDRESS = 192.168.123.0
>
> The inet addr of virbr0 is: 192.168.122.1
>
> When I create a VM on this VNet, OpenNebula shows that it assigned it the
> IP 192.168.123.2 However, when I use virsh or vnc to log into the VM, it
> has another IP address 192.168.122.65.
>
> I don't understand why the VM get a different IP that is not defined in
> the network. Any ideas on how to solve this problem?
>
> Thank you.
>
>

-- 
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525
timm at fnal.gov  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.