KVM/libvirt: How to configure static guest IP addresses on the virtualisation host

Question

What I'd like to do is to set the guests' network configuration (IP address, subnet, gateway, broadcast address) from the host system. The used network setup is in bridge mode. How can I configure the network from the host rather than configuring the client itself to a static network configuration?

If I execute:

virsh edit vm1

there is a <network> block as well and I tried to configure the network interface from there, but unfortunately the guest VM doesn't seem to use it and as such is offline to the network (since it uses automatic network configuration only)... Guest VMs are both, Linux and Windows based. Any help would be highly appreciated.

Solution 1

If you don't want to do any configuration inside the guest, then the only option is a DHCP server that hands out static IP addresses. If you use bridge mode, that will probably be some external DHCP server. Consult its manual to find out how to serve static leases.

But at least in forward modes nat or route, you could use libvirt's built-in dnsmasqd (More recent versions of libvirtd support the dnsmasq's "dhcp-hostsfile" option). Here is how:

First, find out the MAC addresses of the VMs you want to assign static IP addresses:

virsh  dumpxml  $VM_NAME | grep 'mac address'

Then edit the network

virsh  net-list
virsh  net-edit  $NETWORK_NAME    # Probably "default"

Find the <dhcp> section, restrict the dynamic range and add host entries for your VMs

<dhcp>
  <range start='192.168.122.100' end='192.168.122.254'/>
  <host mac='52:54:00:6c:3c:01' name='vm1' ip='192.168.122.11'/>
  <host mac='52:54:00:6c:3c:02' name='vm2' ip='192.168.122.12'/>
  <host mac='52:54:00:6c:3c:03' name='vm3' ip='192.168.122.12'/>
</dhcp>

Then, reboot your VM (or restart its DHCP client, e.g. ifdown eth0; ifup eth0)

---

Update: I see there are reports that the change might not get into effect after "virsh net-edit". In that case, try this after the edit:

virsh  net-destroy  $NETWORK_NAME  
virsh  net-start    $NETWORK_NAME  

... and restart the VM's DHCP client.

If that still doesn't work, you might have to

• stop the libvirtd service
• kill any dnsmasq processes that are still alive
• start the libvirtd service

---

Note: There is no way the KVM host could force a VM with unknown OS and unknown config to use a certain network configuration. But if know know that the VM uses a certain network config protocol - say DHCP - you can can use that. This is what this post assumes.

Some OS (e.g. some Linux distros) also allow to pass network config options into the guest e.g. via the kernel command line. But that is very specific to the OS, and i see no advantage over the DHCP method.

Solution 2

virsh net-update is a good command for you (you don't need to restart/destroy your network etc)
see: https://www.redhat.com/archives/libvir-list/2012-September/msg01380.html

Solution 3

I have been able to make dnsmasq 'see' the newly added IP-MAC mapping by simply sending a -HUP signal to the dnsmasq process. After that, rebooting the new guest was enough to have the correct IP assigned to it, without the need to restart libvirtd nor the network itself.

The official libvirt documentation (http://wiki.libvirt.org/page/Networking#Applying_modifications_to_the_network) mentions this unofficial Perl script that automates the whole process: https://gist.github.com/bendiken/032ea1bddb9ffafe98b4

I haven't tried this script myself, because I figured out that the hostsfile was already updated and just sending the -HUP signal was enough.

The host is running Debian 7.8 and packages versions are:

• kvm 1:1.1.2+dfsg-6+deb7u8
• qemu-kvm 1.1.2+dfsg-6+deb7u8
• libvirt-bin 0.9.12.3-1+deb7u1

Comments

[MadHatter]

Is handing IP addresses out via reserved DHCP leases not an option?

[beta]

Hm I guess it is, but I'd like to assign VM #1 to IP #1, VM #2 to IP #2 etc (rather than giving them a random IP out of my lease). Do you think it would be possible to configuring it like this with DHCP? If it is, I'd be glad to try this approach.

[Matt]

Agree with @NilsToedtmann, any additional details about the hypervisor being used like base OS, etc would be beneficial. There may be additional OS based management tools to help with configuration of networking for virtualized systems. There are great guides on KVM and LXC for use with SUSE based operating systems that can make use of YaST.

[beta]

Thanks I'll try it and report back if I got it working that way.

[Nils Toedtmann]

Cool. But you'll have to change the network mode.

[orodbhen]

I can confirm that changes don't take effect without destroying and restarting the network. I also found, strangely, that I had to shutdown, and then start the VM. Simply rebooting left the interface in a broken state.

[orodbhen]

Restarting the network doesn't renew the DHCP leases. For this, you have to delete the network's status file in /var/lib/libvirtd/dnsmasq

[Alex Willison]

This did not work for me. I had to destroy/start the network.

[sivann]

but the mac address is also random. More stuff is needed.

[mevdschee]

It did work for me, no network restart or VM restart needed.

[Bruce]

If you destroy then start the network the client virtual interfaces will be disconnected until the VM is restarted. A reboot won't help, they must be powered off and back on. Use virsh net-update instead to prevent having to restart the network and therefore all the VMs. This behaviour is documented in the libvirt wiki networking page.