[one-users] Strange IP given to VM

[Adnan Pasic]

Hi guys,
I have built a little cloud with a front-end and two nodes. Everything 
is working well, even my own debian-VM is running and working without 
any flaws. I only have one problem - the VM doesn't get the IP it 
leased. That's why I can't normally ssh into the VM, but first have to 
enter it via VNC, perform a ifconfig to see what IP it got, and then I 
can ssh with this IP address. Here are my settings:

Network template
------------------------
NAME = "Small network"
TYPE = FIXED

#Now we'll use the cluster private network (physical)
BRIDGE = virbr0
LEASES = [IP = 192.168.0.5]
LEASES = [IP = 192.168.0.6]
LEASES = [IP = 192.168.0.7]
LEASES = [IP = 192.168.0.8]
LEASES = [IP = 192.168.0.9]
LEASES = [IP = 192.168.0.10]
LEASES = [IP = 192.168.0.11]
LEASES = [IP = 192.168.0.12]

GATEWAY = 192.168.0.1


ifconfig on the cluster where the VM is running
--------------------------------------------------
eth0      Link encap:Ethernet  Hardware Adresse 00:19:99:03:b0:3e
           inet Adresse:192.168.0.3  Bcast:192.168.0.255  
Maske:255.255.255.0
           inet6-Adresse: fe80::219:99ff:fe03:b03e/64 
Gültigkeitsbereich:Verbindung
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
           RX packets:1310926 errors:0 dropped:0 overruns:0 frame:0
           TX packets:926659 errors:0 dropped:0 overruns:0 carrier:0
           Kollisionen:0 Sendewarteschlangenlänge:1000
           RX bytes:915804031 (915.8 MB)  TX bytes:875825917 (875.8 MB)
           Interrupt:17

lo        Link encap:Lokale Schleife
           inet Adresse:127.0.0.1  Maske:255.0.0.0
           inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
           UP LOOPBACK RUNNING  MTU:16436  Metrik:1
           RX packets:39350 errors:0 dropped:0 overruns:0 frame:0
           TX packets:39350 errors:0 dropped:0 overruns:0 carrier:0
           Kollisionen:0 Sendewarteschlangenlänge:0
           RX bytes:312585500 (312.5 MB)  TX bytes:312585500 (312.5 MB)

virbr0    Link encap:Ethernet  Hardware Adresse fe:00:c0:a8:00:0b
           inet Adresse:192.168.122.1  Bcast:192.168.122.255  
Maske:255.255.255.0
           inet6-Adresse: fe80::6c73:a7ff:fe18:82c2/64 
Gültigkeitsbereich:Verbindung
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
           RX packets:9741 errors:0 dropped:0 overruns:0 frame:0
           TX packets:21749 errors:0 dropped:0 overruns:0 carrier:0
           Kollisionen:0 Sendewarteschlangenlänge:0
           RX bytes:663908 (663.9 KB)  TX bytes:27641431 (27.6 MB)

vnet0     Link encap:Ethernet  Hardware Adresse fe:00:c0:a8:00:0b
           inet6-Adresse: fe80::fc00:c0ff:fea8:b/64 
Gültigkeitsbereich:Verbindung
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
           RX packets:8886 errors:0 dropped:0 overruns:0 frame:0
           TX packets:22354 errors:0 dropped:0 overruns:0 carrier:0
           Kollisionen:0 Sendewarteschlangenlänge:500
           RX bytes:716296 (716.2 KB)  TX bytes:27628111 (27.6 MB)


ifconfig of the VM
-------------------------
eth0      Link encap:Ethernet  HWaddr 02:00:c0:a8:00:0b
           inet addr:192.168.122.44  Bcast:192.168.122.255  
Mask:255.255.255.0
           inet6 addr: fe80::c0ff:fea8:b/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:20877 errors:0 dropped:0 overruns:0 frame:0
           TX packets:8890 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:27551697 (26.2 MiB)  TX bytes:717022 (700.2 KiB)
           Interrupt:11 Base address:0xc100

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:8 errors:0 dropped:0 overruns:0 frame:0
           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)



As you can see, the cluster somehow assigned a 192.168.122.* IP-address 
to the virtual interface, although I don't know why. Also, the VM 
received a correct MAC-address (corresponding to IP 192.168.0.11), but 
still it got an IP address from the .122.* interval! Anyone an idea why 
this virtual interface behaves like that?
Cheers