Skip to main content

KVM - Headless Server setup with Bonding, Bridging and LVM on CentOS 7


I'll be using a plain CentOS 7 minimal install with the latest updates for this installation. First up, let's install the packages we need to make the Host a hypervisor:
 [archy@hyv01 ~]$ sudo yum install qemu-kvm libvirt libvirt-python libguestfs-tools virt-install tuned  
 [archy@hyv01 ~]$ sudo systemctl enable libvirtd.service  
 [archy@hyv01 ~]$ sudo systemctl start libvirtd.service
 [archy@hyv01 ~]$ sudo tuned-adm profile virtual-host
NOTE: Tuned is optional but might squeeze out a little bit more performance and optimize the host for virtualization workloads. More info can be found by using 'man tuned-profiles'.

Next, the network Configuratin. I'll use 4 Interfaces for the bond itself which will then again be a slave interface to the bridge which the VMs on this host will connect to.

The Network Interfaces for the Bond will be:
- ens2f0
- ens2f1
- ens2f2
- ens2f3
 [archy@hyv01 ~]$ sudo nmcli connection add type bond con-name bond0 ifname bond0 mode 802.3ad  
 [archy@hyv01 ~]$ sudo nmcli connection add type ethernet con-name bond0-ens2f0 ifname ens2f0 master bond0  
 [archy@hyv01 ~]$ sudo nmcli connection add type ethernet con-name bond0-ens2f1 ifname ens2f1 master bond0  
 [archy@hyv01 ~]$ sudo nmcli connection add type ethernet con-name bond0-ens2f2 ifname ens2f2 master bond0  
 [archy@hyv01 ~]$ sudo nmcli connection add type ethernet con-name bond0-ens2f3 ifname ens2f3 master bond0  
 [archy@hyv01 ~]$ sudo nmcli connection add type bridge con-name br0 ifname br0  
 [archy@hyv01 ~]$ sudo nmcli connection mod bond0 connection.master br0 connection.slave-type bridge  
 [archy@hyv01 ~]$ sudo nmcli connection mod br0 ipv4.address 172.31.0.250/24  
 [archy@hyv01 ~]$ sudo nmcli connection mod br0 ipv4.dns 9.9.9.9  
 [archy@hyv01 ~]$ sudo nmcli connection mod br0 +ipv4.dns 1.1.1.1  
 [archy@hyv01 ~]$ sudo nmcli connection mod br0 ipv4.gateway 172.31.0.254

You can raise the Interfaces yourself or restart the network.service. Note: this might take a few seconds since the dependencies of all interfaces is quite large. Next up, adding VLANs:
 [archy@hyv01 ~]$ sudo nmcli connection add type vlan con-name bond0.100 ifname bond0.100 dev bond0 id 100  
 [archy@hyv01 ~]$ sudo nmcli connection add type bridge ifname br0.100 con-name br0.100  
 [archy@hyv01 ~]$ sudo nmcli connection mod bond0.100 connection.master br0.100 connection.slave-type bridge  
 [archy@hyv01 ~]$ sudo nmcli connection mod br0.100 ipv4.method link-local
 [archy@hyv01 ~]$ sudo nmcli connection mod br0.100 ipv6.method ignore

I will not give this VLAN-Interface any IP-Address since it's not supposed to be reachable over IP.
Next up, create the storage pools

I'd recommend to restart the server, just to verify if everything works as expected at reboot.

If everything works as expected, let's continue with storage pools and disk setup.
If you are using a second disk (which I highly encourage you to) first set up the physical volumes and volume groups.

I have already created a partition on my second disk (/dev/sdb) with type 8e if you are using fdisk or 8e00 if you are using gdisk.

Create the physical volume, volume groups and logical volumes:
 [archy@hyv01 ~]$ sudo pvcreate /dev/sdb1  
 [archy@hyv01 ~]$ sudo vgcreate vg_kvmstore /dev/sdb1  
 [archy@hyv01 ~]$ sudo lvcreate -n lv_vm_iso -L 100G vg_kvmstore  
 [archy@hyv01 ~]$ sudo lvcreate -n lv_vm_images -L 1T vg_kvmstore  
 [archy@hyv01 ~]$ sudo mkfs.xfs /dev/vg_kvmstore/lv_vm_iso  
 [archy@hyv01 ~]$ sudo mkfs.xfs /dev/vg_kvmstore/lv_vm_images

Now that the storage is set up, make sure it's entered in the fstab correctly. I'll use the following lines:
 /dev/mapper/vg_kvmstore-lv_vm_iso /srv/kvm/vm-iso xfs defaults 0 0  
 /dev/mapper/vg_kvmstore-lv_vm_images /srv/kvm/vm-images xfs defaults 0 0

and mount them all:
 [archy@hyv01 ~]$ sudo mount -a

If you are using SELinux, you'll also have to set the context for each path:
 [archy@hyv01 ~]$ sudo semanage fcontext -a -t virt_content_t '/srv/kvm/vm-iso(/.*)?'  
 [archy@hyv01 ~]$ sudo semanage fcontext -a -t virt_image_t '/srv/kvm/vm-images(/.*)?'  
 [archy@hyv01 ~]$ sudo restorecon -Rv /srv/kvm  
 [archy@hyv01 ~]$ sudo chown -R qemu:eqmu /srv/kvm  
 [archy@hyv01 ~]$ sudo chmod -R 1755 /srv/kvm

You can now go ahead and sync any ISOs to the location. I'll use rsync for task:
 [archy@hyv01 ~]$ sudo rsynv -vrlptgoDxh --progress -e ssh archy@strgnas.archyslife.lan:/storage/data/iso-files/ /srv/kvm/vm-iso/

If you have a linux client that runs virt-manager and want to manage your hypervisor that way, you'll have to export your public key to the user permitted to manage libvirt. I'll use the root-user for simplicity.
 [archy@stealth-falcon ~]$ ssh-copy-id root@hyv01.archyslife.lan  
 Password:

Now open the Virt-Manager Application and Click on
File --> Add Connection
--> Set Hypervisor to 'QEMU/KVM'
--> Tick the box that says 'connect to remote host over SSH'
--> Set the Username to 'root'
--> Set the Hostname to your hypervisor's hostname, in my case 'hyv01.archyslife.lan'
--> Tick the box that says 'autoconnect'
--> Click on 'Connect' and you're done.

From the Virt-Manager GUI you can define your storage pools. I'll use the GUI for that since it's easier and faster than to define your XML-File and running virsh pool-define, virsh pool-create and virsh pool-autostart. But that's just my favor. Anyway, that completes my setup for a headless KVM Hypervisor with Bridging, Bonding and LVM.

Feel free to comment and / or suggest any topics.
Labels:

Comments

Post a Comment

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0
Post a Comment
Read more

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla
8 comments
Read more

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?
9 comments
Read more

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). recently went over my network configuration and I noticed that I've never put my My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key&quo
2 comments
Read more

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the
Post a Comment
Read more