Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Yes that is your problem. It attempts to give the first address in the subnet to your machine and it is conflicting with your external dns server. You could try using a smaller network, such as: 128.96.126.224/27 although your .1 server may still give out addresses and mess things up. Worth a shot. You'll have to delete networks and fixed_ip tables and recreate the smaller range with nova-network network create you should also change: --fixed_range=128.96.224/27 --flat_network_dhcp_start=138.96.126.225

killall dnsmasq iptables -F iptabbles -t nat -F restart nova-network

try again?

Vish

On Apr 22, 2011, at 7:52 AM, Brian Amedro wrote:

Question #153827 on OpenStack Compute (nova) changed: https://answers.launchpad.net/nova/+question/153827

Status: Answered => Open

Brian Amedro is still having a problem: Hi vish, thanks for the reply !

You're right, I am trying to put instances on the same network as the host machine. This network already has a DHCP server on 138.96.126.1, which give IP for the range 138.96.126.1-199. Also, I cannot modify the config of this server.

Is there any way so the host machine respond to the VM requests instead of the external DHCP server ? Looking at /var/lib/nova/instances/instance-00000019/libvirt.xml, it does not seems to be the case: <parameter name="DHCPSERVER" value="138.96.126.1"/>

Also, and to be complete, even if I put --flat_network_dhcp_start=138.96.126.200 in my nova.config file, started instances was assigned with an IP in the wrong range. Thus, I modified by hand the database, in order to exclude some range by setting the 'reserved' column in the fixed_ips table.

As you asked, here is the list of dnsmasq processes.

nobody 1029 0.0 0.0 21688 1072 ? S 18:16 0:00 dnsmasq --strict-order --bind-interfaces --pid- file=/var/run/libvirt/network/default.pid --conf-file= --except- interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-lease-max=253 --dhcp-no-override

nobody 1417 0.0 0.0 24388 1112 ? S 18:16 0:00 dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid- file=/var/lib/nova/networks/nova-br100.pid --listen-address=138.96.126.1 --except-interface=lo --dhcp-range=138.96.126.200,static,120s --dhcp- hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/bin /nova-dhcpbridge --leasefile-ro

root 1418 0.0 0.0 24256 416 ? S 18:16 0:00 dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid- file=/var/lib/nova/networks/nova-br100.pid --listen-address=138.96.126.1 --except-interface=lo --dhcp-range=138.96.126.200,static,120s --dhcp- hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/bin /nova-dhcpbridge --leasefile-ro

$ cat /var/lib/nova/networks/nova-br100.conf 02:16:3e:12:e4:ad,i-0000001e.novalocal,138.96.126.200

-- You received this question notification because you are a member of Nova Core, which is an answer contact for OpenStack Compute (nova).