Configuring Fedora 25 as a Hypervisor using Virtual Machine Manager


After following the below instructions, you should be able to deploy VMs that:

  1. Can be accessed by IP from the Host
  2. Can communicate with each other
  3. Can communicate to the external network
  4. Are not accessible beyond your Host

While these instructions were performed on a Fedora 25 machine, they should work on other supported versions and few other distros with minimal command modifications.

Package Installation and Services

  1. Make sure your system is up to date and restart if necessary:
    • sudo dnf update -y ; reboot
  2. Install the required packages:
    • sudo dnf install virt-manager qemu-kvm qemu-img libvirt-daemon libvirt-daemon-driver*
  3. Start the Libvirt Daemon:
    • sudo systemctl start libvirtd

Configure the Virtual Network

This network will be accessible within your Host environment only and will be service IP Addresses by DHCP to your VMs.

  1. Open virt-manager by searching for it in the Gnome search bar, by finding it under the KDE applications menu, or by launching it through terminal using sudo virt-manager.
  2. Go to Edit – Connection Details.
  3. Click on the Virtual Networks tab and then click the plus (+) sign at the lower left corner of the window.
    1. For Network Name, choose something simple, such as “virtnet” and click Forward.
    2. Verify that Enable IPv4… and Enable DHCPv4 are both checked.
      • Network: (example)
      • Start: (example)
      • End: (example)
    3. Click Forward twice to skip IPv6 DHCP configuration unless you plan on needing it for another reason than deploying more than 4.3 billion VMs.
    4. Select Forward to physical network and leave other settings default.
    5. Click Finish.

You should now be able to deploy new VMs without much difficulty.

Deploying a Fedora 25 Server Guest VM (Exercise #1)

With Fedora, it is easy to deploy a VM using HTTP.  This will ensure you are always deploying with the latest packages available.

  1. Within Virtual Machine Manager, go to File – New Virtual Machine, or click on the Create a new virtual machine icon _below_ File.
  2. Select Network Install and then click Forward.
  3. For URL, paste in the following link and then click Forward four times:

Manually assigning an IP Address from the Host (Exercise #2)

Libvirt uses dnsmasq to manage the DHCP range of newly deployed VMs.  Due to this, you are given some flexibility to have dnsmasq manually assign IP Addresses based off of the VM’s MAC Address.

For this example, I am using the VM I deployed from the first exercise.

  1. From terminal on the Host, grab the MAC address of the fedora25 VM that was deployed:
    • sudo virsh dumpxml fedora25 | grep 'mac address'
  2. Next, use the MAC address shown to give that VM a specific IP Address ( in this example):
    • sudo virsh net-update virtnet add ip-dhcp-host "<host mac='######' name='fedora25' ip='192.168.100.#'/>" --live --config
  3. Finally, bounce the network adapter on the VM itself to grab the new IP.  Example:
    • sudo ifdown eth0 ; sudo ifup eth0


====== Fedora 25 Host

striker host ~ $ sudo virsh dumpxml fedora25 | grep ‘mac address’
<mac address=’52:54:00:a9:37:f0’/>

striker host ~ $ sudo virsh net-update virtnet add ip-dhcp-host “”<host mac=’52:54:00:a9:37:f0′ name=’fedora25′ ip=’’/>” –live –config
Updated network virtnet persistent config and live state

====== Fedora 25 VM

[root@fedora25 ~]# ip a | grep ‘inet 192’
inet brd scope global dynamic ens3

[root@fedora25 ~]# ifdown ens3
Device ‘ens3’ successfully disconnected.

[root@fedora25 ~]# ifup ens3
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/1)

[root@fedora25 ~]# ip a | grep ‘inet 192’
inet brd scope global dynamic ens3

Adding a new Storage layer to a VM (Exercise #3)

This exercise will walk you through creating a virtual storage drive and attach it to your VM.  For the purpose of the exercise, I will be using the Fedora 25 Server VM deployed above.

  1. Within Virtual Machine Manager, highlight the VM you wish to add a new storage drive to and then click Open.
  2. Within the VM window, click the Lightbulb icon labeled Show virtual hardware details.
  3. In the bottom-left corner, click Add Hardware.
  4. Storage should be selected within the next window.  Choose the size you wish the new storage device to be and click Finish.
  5. Within the VM window, click on the Computer Monitor icon labeled Show the graphical console.
  6. You may need to restart the VM for the new storage device to show up.  Since we are using the Fedora 25 VM deployed above, the device shows up immediately:

[root@fedora25 ~]# lsblk
vdb 252:16 0 20G 0 disk   #   <———————–
vda 252:0 0 20G 0 disk
├─vda2 252:2 0 19G 0 part
│ ├─fedora-swap 253:1 0 2G 0 lvm [SWAP]
│ └─fedora-root 253:0 0 15G 0 lvm /
└─vda1 252:1 0 1G 0 part /boot

Stay in touch!

You can stay in touch with libvirt specialists by joining the OFTC IRC network and then joining the #virt channel.  Fedora’s IRC channel is #fedora on Freenode‘s IRC network.  You can also join the libvirt mailing list discussion by following the below link:

Authenticating to Fedora using Active Directory credentials that lack Unix attributes

This weekend at the SouthEast LinuxFest, I had a talk about how you can authenticate to Fedora using Active Directory credentials that lack Unix attributes.  Since newer deployments of the most recent versions of Active Directory no longer give you the ability by default to configure Unix attributes, it is important to know that this is not a show stopper.

In my talk, I showed how SSSD uses ID Mapping by converting an objectSID value from a user object from binary to a human-readable number and then runs that number through an algorithm to generate a UID.  It will do the same thing for group objects so that you also have GIDs.  Besides the UID and GID, SSSD has the ability to use a ‘fallback’ mode for home directory and shell locations.  This way, you can “fill in the blanks” of missing information.

Here is an example user object we used in the demonstration to show this:

ldapsearch -LLL -h -D Administrator@WIN.TERRANFORGE.COM -W -b dc=win,dc=terranforge,dc=com samaccountname=youknownothing

dn: CN=Jon Snow,CN=Users,DC=win,DC=terranforge,DC=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
cn: Jon Snow
sn: Snow
givenName: Jon
distinguishedName: CN=Jon Snow,CN=Users,DC=win,DC=terranforge,DC=com
instanceType: 4
whenCreated: 20160610164605.0Z
whenChanged: 20160610164605.0Z
displayName: Jon Snow
uSNCreated: 20499
uSNChanged: 20504
name: Jon Snow
objectGUID:: Y7sOFvVwRkmrKNCJiXYkSw==
userAccountControl: 66048
badPwdCount: 0
codePage: 0
countryCode: 0
badPasswordTime: 0
lastLogoff: 0
lastLogon: 0
pwdLastSet: 131100507651203267
primaryGroupID: 513
accountExpires: 9223372036854775807
logonCount: 0
sAMAccountName: youknownothing
sAMAccountType: 805306368
objectCategory: CN=Person,CN=Schema,CN=Configuration,DC=win,DC=terranforge,DC=
dSCorePropagationData: 16010101000000.0Z

# refldap://,DC=win,DC=terranforge,DC=com

As you can see, Jon Snow (youknownothing) lacks four of the things that POSIX compliant systems require a user to have: UID, GID, Home Directory and Shell.  However, on a Fedora 23 system that has been joined to the same AD domain, we can successfully see that the user DOES have a UID, GID, Home Directory and Shell:

[root@garden ~]# cat /etc/fedora-release
Fedora release 23 (Twenty Three)
[root@garden ~]# id youknownothing
uid=436801105(youknownothing) gid=436800513(domain users) groups=436800513(domain users)
[root@garden ~]# getent passwd youknownothing
youknownothing:*:436801105:436800513:Jon Snow:/home/youknownothing:/bin/bash

And, we can authenticate as that user to the Fedora system:

[root@garden ~]# ssh youknownothing@localhost
youknownothing@localhost’s password:
[youknownothing@garden ~]$ id
uid=436801105(youknownothing) gid=436800513(domain users) groups=436800513(domain users) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
[youknownothing@garden ~]$

This happens successfully because SSSD is converting the binary SID value to a number, turning that number into a UID based off of an algorithm and then filling in whatever attributes are necessary for the POSIX-compliant system to accept the user as valid.  The only thing SSSD requires from AD to make this happen is an ‘id’, such as a username and the SID attribute.  In sssd.conf, we specify the Shell and Home Directory attributes:

id_provider = ad
ad_server =

services = nss, pam
config_file_version = 2
domains =



Using the ‘default_shell’ and ‘fallback_homedir’ options means that if SSSD does not find these attributes within AD, it will substitute what you give it.  In this case, /bin/bash and /home/%u.  This allows you to specify the unixHomeDir and unixShell attributes in AD for a user if you still desire to do so, and SSSD will use those.

To generate an UID and GID based off of the object’s SID value, SSSD’s ID Mapping algorithm is very similar to how Winbind’s autorid backend works.  This makes it trivial to move from older Winbind configurations to SSSD and continue to retain original UID and GID values.  Using SSSD in this fashion will make the UIDs and GIDs across all systems joined to AD consistent for each user and group, making things like file-sharing hassle-free.

Install the i3 tiling window manager from Fedora 23 Minimal

It was mentioned in the #fedora channel on Freenode’s IRC server that it is difficult to get the i3 tiling window manager working from a Minimal Fedora 23 install.  I ran through the steps myself and narrowed down what was needed to get this to work.

  1. Install Fedora 23 using the Minimal selection on the Server ISO
  2. Post-install, do the following:
    • dnf install i3 i3status dmenu i3lock xbacklight feh conky xterm sddm mesa-dri-drivers xorg-x11-drv-evdev xorg-x11-drv-fbdev xorg-x11-drv-vmmouse xorg-x11-drv-synaptics
    • systemctl set-default
    • systemctl isolate

The above process should bring you to an SDDM login screen where you can select the Window Manager you wish to use (top-left) and then log in.

SystemD Analyze Blame

If you want your boot times to be quicker, consider removing things like FirewallD, LVM and NetworkManager as these things cause the most delay at boot:

sudo systemd-analyze blame

1.119s firewalld.service
584ms dev-mapper-fedora\x2droot.device
332ms plymouth-start.service
250ms lvm2-monitor.service
187ms systemd-journal-flush.service
177ms systemd-vconsole-setup.service
125ms systemd-udevd.service
84ms systemd-tmpfiles-setup-dev.service
70ms fedora-readonly.service
66ms user@995.service
62ms systemd-udev-trigger.service
53ms systemd-tmpfiles-setup.service
52ms systemd-user-sessions.service
47ms plymouth-quit-wait.service
46ms systemd-journald.service
44ms kmod-static-nodes.service
41ms plymouth-quit.service
39ms NetworkManager.service
38ms systemd-sysctl.service
35ms sys-kernel-debug.mount
34ms dev-mqueue.mount
34ms systemd-fsck@dev-disk-by\x2duuid-*******.service
34ms systemd-logind.service
29ms tmp.mount
25ms systemd-remount-fs.service
21ms user@0.service
21ms auditd.service
20ms boot.mount
20ms plymouth-read-write.service
18ms lvm2-pvscan@252:2.service
16ms dev-hugepages.mount
15ms dracut-shutdown.service
15ms systemd-random-seed.service
13ms systemd-update-utmp-runlevel.service
7ms systemd-fsck-root.service
6ms dev-mapper-fedora\x2dswap.swap
4ms systemd-update-utmp.service
1ms sys-kernel-config.mount