Skip to main content

Libvirt KVM fixed IP address


When playing with KVM LibVirt Vms, I often need them to have fixed IP address.
Ironically, I enjoy fixing them with DHCP.
Here is the “default” configuration I use in order to fix them.
Redefining the "default" network is done with:

virsh --connect qemu:///system net-destroy default
virsh --connect qemu:///system net-undefine default
virsh --connect qemu:///system net-define /tmp/network.xml
virsh --connect qemu:///system net-start default

Feel free to get inspiration:
<network>                                                   
  <name>default</name>                                      
  <uuid>7efbc96f-94e8-443f-820c-615d2e0331d5</uuid>         
  <forward mode='nat'/>                                     
  <bridge name='virbr0' stp='on' delay='0' />               
  <ip address='192.168.122.1' netmask='255.255.255.0'>      
    <dhcp>                                                  
      <range start='192.168.122.2' end='192.168.122.254' /> 
      <host mac="52:54:00:9a:81:00" name="centos6-00.vm.mihamina.netapsys.fr" ip="192.168.122.132" />
      <host mac="52:54:00:e0:0e:8a" name="centos6-01.vm.mihamina.netapsys.fr" ip="192.168.122.118" />
      <host mac="52:54:00:c1:ff:12" name="debian7-00.vm.mihamina.netapsys.fr" ip="192.168.122.144" />
      <host mac="52:54:00:06:a1:f4" name="debian7-01.vm.mihamina.netapsys.fr" ip="192.168.122.68" />
      <host mac="52:54:00:91:d1:96" name="debian7-02.vm.mihamina.netapsys.fr" ip="192.168.122.92" />
      <host mac="52:54:00:22:20:cd" name="fedora19-00.vm.mihamina.netapsys.fr" ip="192.168.122.20" />
      <host mac="52:54:00:1d:0f:9e" name="fedora19-01.vm.mihamina.netapsys.fr" ip="192.168.122.157" />
      <host mac="52:54:00:2a:a6:41" name="gitlab-c6-01.vm.mihamina.netapsys.fr" ip="192.168.122.235" />
      <host mac="52:54:00:f7:30:03" name="gitlab-c6-02.vm.mihamina.netapsys.fr" ip="192.168.122.54" />
      <host mac="52:54:00:86:a0:d6" name="win7-00.vm.mihamina.netapsys.fr" ip="192.168.122.152" />
      <host mac="52:54:00:e8:a8:b8" name="win7-01.vm.mihamina.netapsys.fr" ip="192.168.122.14" />
    </dhcp>                                                 
  </ip>                                                     
</network>                                                  


Comments

Popular posts from this blog

vmware libz libfontconfig libexpat

Archlinux - Kernel 4.11 - VMWare workstation 12.5.7 With this combination, when I launch "vmware", despite the fact I already "export VMWARE_USE_SHIPPED_LIBS=force", I get those lines:

Unable to load libfontconfig.so.1. /usr/lib/vmware/lib/libz.so.1/libz.so.1: version `ZLIB_1.2.9' not found (required by /usr/lib/libpng16.so.16) Unable to load libfontconfig.so.1 from /usr/lib/vmware/lib/libfontconfig.so.1/libfontconfig.so.1: libexpat.so.0: cannot open shared object file: No such file or directory Unable to load dependencies for /usr/lib/vmware/lib/libvmware-modconfig.so/libvmware-modconfig.so
In order to workaround, I decided to get the things to the maximum: Add all shipped libraries in the LD_LIBRARY_PATH.

So I created my custom launcher of "vmware" and this is the content:

#!/bin/bash
export VMWARE_USE_SHIPPED_LIBS=force
LD_LIBRARY_PATH=""
LD_LIBRARY_PATH=$( find /usr/lib/vmware/lib/ -maxdepth 1 -mindepth 1 -type d | awk 'BEGIN{p=&quo…

vmware net_device trans_start

VMWare Workstation 12 and Kernel 4.7 When recompiling vmware kernel modules on a kernel 4.7, I get this error:

/tmp/modconfig-xrrZGZ/vmnet-only/netif.c:468:7: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’?     dev->trans_start = jiffies;
This seems to be an already encountered problem: http://rglinuxtech.com/?p=1746http://ferenc.homelinux.com/?p=356 I choosed to replace the line, instead of deleting it.

- dev->trans_start = jiffies; + netif_trans_update(dev); I also noted that I had to re-tar the modified sources instead of leaving them untared, because the compilation process only takes the archives. 
On precedent editions of these files, I just left the modified folders "vmnet-only/" and "vmmon-only/" expanded without the need to re-tar them.


Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.
I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.
Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:
"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

The new created project will use the same configuration as the project I selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…