<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tadaweb on Medium]]></title>
        <description><![CDATA[Stories by Tadaweb on Medium]]></description>
        <link>https://medium.com/@tadaweb?source=rss-bf6e71b222f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*nKEHUqGOObF0MR_B9xpcBg.png</url>
            <title>Stories by Tadaweb on Medium</title>
            <link>https://medium.com/@tadaweb?source=rss-bf6e71b222f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:27:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tadaweb/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Creating a Professional Home Lab Setup -Part 3: Virtual Machine Management]]></title>
            <link>https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-3-virtual-machine-management-cf4e5f64c0ac?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf4e5f64c0ac</guid>
            <category><![CDATA[kvm]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[qemu]]></category>
            <category><![CDATA[homelab]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Wed, 27 Mar 2024 13:29:55 GMT</pubDate>
            <atom:updated>2024-03-27T13:30:59.462Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l4UwohzbUq3cLA9eI_8CJw.png" /></figure><h4>In the third part of “Creating a Professional Home Lab Setup,” Pascal explains how to clone virtual machines and use the virt-sysprep tool to customize them for your network.</h4><p><em>By Pascal Van Acker</em></p><h3>Introduction</h3><p>This is part 3 of a 3-part series:</p><ul><li><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-1-installing-the-operating-system-cfb4839fc796">Part 1</a> covers the installation of the Ubuntu operating system on a bare-metal machine.</li><li><a href="https://tadaweb.medium.com/8a19c44813e5?sk=63fd2e36080d1e8e5fbebd73a69bd331">Part 2</a> covers the setup and configuration of the <a href="https://linux-kvm.org/">KVM</a> and <a href="https://www.qemu.org/">QEMU</a> hypervisors with an API on top using <a href="https://libvirt.org/">libvirt</a>. We will also install our first virtual machine.</li><li><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-3-virtual-machine-management-cf4e5f64c0ac">Part 3</a> covers virtual machine management and the process of cloning virtual machines and using the <a href="https://www.libguestfs.org/virt-sysprep.1.html">virt-sysprep</a> tool to make the cloned machine unique in the network.</li></ul><p>In this final part of the series, we will be taking a look at some virtual machine management topics. We will perform a clone of the virtual machine and use the <a href="https://www.libguestfs.org/virt-sysprep.1.html">virt-sysprep</a> tool to make it unique in the network. We will also take a look at some management tools to facilitate working with virtual machines.</p><h3>Prerequisites</h3><p>At this point, we expect you to have a physical machine with <a href="https://ubuntu.com/">Ubuntu</a> 22.04 LTS already set up. The machine is configured as a hypervisor using <a href="https://linux-kvm.org/">KVM</a> and <a href="https://www.qemu.org/">QEMU</a> and is using <a href="https://libvirt.org/">libvirt</a> as the managment api. If you do not have this, you can follow <a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-1-installing-the-operating-system-cfb4839fc796">Part 1</a> and <a href="https://tadaweb.medium.com/8a19c44813e5?sk=63fd2e36080d1e8e5fbebd73a69bd331">Part 2</a> of the series and return to this part when you are done.</p><h3>Virtual Machine Cloning</h3><p>Whenever we add new machines to our labs, we don’t want to go through the hassle of setting them up from scratch. For that reason, we will be using the <a href="https://linux.die.net/man/1/virt-clone">virt-clone</a> and <a href="https://www.libguestfs.org/virt-sysprep.1.html">virt-sysprep</a> commands to make a unique clone of the <strong>ubuntu22.04</strong> machine we created earlier in the series.</p><p>We can use the virsh command to list all of our virtual machines. If you have followed the first two parts of the tutorial, the machine you have created will be called <strong>ubuntu22.04</strong>. If you chose another name, please replace the name in all susequent commands:</p><pre># List virtual machines<br>virsh list --all</pre><p>This will output the following</p><pre>Id   Name                   State<br>---------------------------------------<br> -    ubuntu22.04            shut off</pre><p>We can clone this machine to create a new machine called <strong>lab01</strong> using the <a href="https://linux.die.net/man/1/virt-clone">virt-clone</a> command:</p><pre># This create a virtual machine clone called lab01 from the ubuntu22.04 <br># template machine<br>virt-clone --original ubuntu22.04 --name lab01 --auto-clone<br>Allocating &#39;lab01.qcow2&#39;                                                                                                                                                                     | 2.6 GB  00:01:44 ...</pre><p>The output expected should be:</p><pre>Clone &#39;lab01&#39; created successfully.</pre><p>We can confirm that the cloning was successful by listing the virtual machines again:</p><pre># List virtual machines<br>virsh list --all</pre><p>This will output the following</p><pre> Id   Name                   State<br>---------------------------------------<br> -    lab01                  shut off<br> -    ubuntu22.04            shut off</pre><p>To see the differences between the original machine and the new clone, we can perform a diff on the virsh dumpxml command:</p><pre># This shows a diff of the output of the two commands<br>diff &lt;(virsh dumpxml ubuntu22.04) &lt;(virsh dumpxml lab01)</pre><p>You should get the following output:</p><pre>2,3c2,3<br>&lt;   &lt;name&gt;ubuntu22.04&lt;/name&gt;<br>&lt;   &lt;uuid&gt;c1a22b34-db2b-4f75-944c-4496a1d6f48c&lt;/uuid&gt;<br>---<br>&gt;   &lt;name&gt;lab01&lt;/name&gt;<br>&gt;   &lt;uuid&gt;ed53c885-5d12-4fb3-b374-f6bd373e41b1&lt;/uuid&gt;<br>37c37<br>&lt;       &lt;source file=&#39;/data/vmstorage/ubuntu22.04.qcow2&#39;/&gt;<br>---<br>&gt;       &lt;source file=&#39;/data/vmstorage/lab01.qcow2&#39;/&gt;<br>128c128<br>&lt;       &lt;mac address=&#39;52:54:00:91:75:33&#39;/&gt;<br>---<br>&gt;       &lt;mac address=&#39;52:54:00:c7:b9:8c&#39;/&gt;</pre><p>At this point, the machine is cloned and the new machine has a different <strong>name</strong>, <strong>uuid,</strong> and <strong>mac address</strong> but, the new <strong>lab01</strong> machine is not ready to be used on the network. The machine linux installation still contains the same <strong>machine_id</strong> as the machine we cloned it from. We can use the <a href="https://linux.die.net/man/1/virt-cat">virt-cat</a> tool to confirm this:</p><blockquote>NOTE: <a href="https://linux.die.net/man/1/virt-cat">virt-cat</a> and <a href="https://libguestfs.org/virt-edit.1.html">virt-edit</a> are handy tools that allow for inspection and modification of files on the virtual machine disk image while the virtual machine is not started. They are all part of the <strong>libguestfs</strong> package we installed in part 2 of the series.</blockquote><blockquote>NOTE: You will have to use sudo because the virtual machine disks are owned by <strong>root</strong>.</blockquote><pre># Print the machine id of the lab01 machine<br>sudo virt-cat --domain lab01 /etc/machine-id<br><br># Print the machine id of the ubuntu22.04 machine<br>sudo virt-cat --domain ubuntu22.04 /etc/machine-id</pre><p>In the output, you can see that the machine id of both machines is still identical</p><pre>c1a22b34db2b4f75944c4496a1d6f48c<br><br>c1a22b34db2b4f75944c4496a1d6f48c</pre><p>We will use the <a href="https://www.libguestfs.org/virt-sysprep.1.html">virt-sysprep</a> tool on our new clone to make it unique. This operation will change some settings such as ssh fingerprints, network settings, and the machine id.</p><blockquote>NOTE: In the command below, we omit certain operations such as <strong>ssh-userdir</strong> and <strong>lvm-uuids</strong> by prefixing them with a minus symbol (-). The -<strong>ssh-userdir</strong> opersation ensures that any authorized_keys files we have set up will be kept while the -<strong>lvm-uuids </strong>operation makes sure we can boot the new machine without having to modify the <a href="https://wiki.archlinux.org/title/fstab">/etc/fstab</a> file to change the mount points beforehand.</blockquote><blockquote>NOTE: We also need to reconfigure the openssh-server config by passing a command in the --<strong>firstboot-comand</strong> flag to ensure that new ssh host keys are generated when the machine starts for the first time.</blockquote><pre># Prepare the virtual machine<br>sudo virt-sysprep -a /data/vmstorage/lab01.qcow2 --hostname lab01 --operations defaults,machine-id,-ssh-userdir,-lvm-uuids --firstboot-command &#39;dpkg-reconfigure openssh-server&#39;</pre><p>This should output the following</p><pre>[   0.0] Examining the guest …<br>[   2.3] Performing &quot;abrt-data&quot; …<br>[   2.3] Performing &quot;backup-files&quot; …<br>[   2.6] Performing &quot;bash-history&quot; …<br>[   2.6] Performing &quot;blkid-tab&quot; …<br>[   2.6] Performing &quot;crash-data&quot; …<br>[   2.7] Performing &quot;cron-spool&quot; …<br>[   2.7] Performing &quot;dhcp-client-state&quot; …<br>[   2.7] Performing &quot;dhcp-server-state&quot; …<br>[   2.7] Performing &quot;dovecot-data&quot; …<br>[   2.7] Performing &quot;ipa-client&quot; …<br>[   2.8] Performing &quot;kerberos-hostkeytab&quot; …<br>[   2.8] Performing &quot;logfiles&quot; …<br>[   2.8] Performing &quot;machine-id&quot; …<br>[   2.8] Performing &quot;mail-spool&quot; …<br>[   2.8] Performing &quot;net-hostname&quot; …<br>[   2.9] Performing &quot;net-hwaddr&quot; …<br>[   2.9] Performing &quot;pacct-log&quot; …<br>[   2.9] Performing &quot;package-manager-cache&quot; …<br>[   3.0] Performing &quot;pam-data&quot; …<br>[   3.0] Performing &quot;passwd-backups&quot; …<br>[   3.0] Performing &quot;puppet-data-log&quot; …<br>[   3.0] Performing &quot;rh-subscription-manager&quot; …<br>[   3.0] Performing &quot;rhn-systemid&quot; …<br>[   3.1] Performing &quot;rpm-db&quot; …<br>[   3.1] Performing &quot;samba-db-log&quot; …<br>[   3.1] Performing &quot;script&quot; …<br>[   3.1] Performing &quot;smolt-uuid&quot; …<br>[   3.1] Performing &quot;ssh-hostkeys&quot; …<br>[   3.1] Performing &quot;sssd-db-log&quot; …<br>[   3.2] Performing &quot;tmp-files&quot; …<br>[   3.2] Performing &quot;udev-persistent-net&quot; …<br>[   3.2] Performing &quot;utmp&quot; …<br>[   3.2] Performing &quot;yum-uuid&quot; …<br>[   3.2] Performing &quot;customize&quot; …<br>[   3.3] Setting a random seed<br>[   3.3] Setting the machine ID in /etc/machine-id<br>[   3.3] Setting the hostname: lab01<br>[   4.1] Installing firstboot command: dpkg-reconfigure openssh-server</pre><p>You can take a look at the output to find out what actually happened. Additionally, you can pass the <strong>-v</strong> flag to enable <strong>verbose</strong> output and get even more information.</p><p>You can repeat this process as often as you want to create your home lab. You will of course be limited by the amount of resources (CPU, Memory) that you have on the hypervisor machine. All the clones that you create can safely be used in the same network.</p><h3>Connecting to the Virtual Machine Console Using VNC</h3><p>Let’s start by booting our newly cloned virtual machine:</p><pre># Start the machine<br>virsh start --domain lab01</pre><p>This will output the following</p><pre>Domain &#39;lab01&#39; started</pre><p>Because have cloned the machine from our <strong>ubuntu22.04</strong> template, VNC is already enabled and we can connect to our new clone using the server_ip and port combination. In this part of the series, I will connect using remmina from an ubuntu laptop on the same network.</p><blockquote>NOTE: You can find the server ip by logging in to the console of the hypervisor and typing <strong>hostname -I</strong>. In my case the ip address is <strong>192.168.1.11</strong>.</blockquote><blockquote>NOTE: If this is the only virtual machine that is started, the default port for VNC will be <strong>5900</strong>. If this does not work, you can use the <strong>virsh dumpxml lab01</strong> command on the hypervisor to find out which port the VNC server is bound to.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5vtbqmHGm8xJe8sF8WtFLA.png" /><figcaption>Image 1</figcaption></figure><ol><li>Click on the <strong>New Connection Profile</strong> icon</li><li>Select a name for the connection (for example: kvm)</li><li>Enter the server ip address + vnc port combination</li><li>Click on <strong>Save and Connect</strong></li></ol><p>You will be presented with the console of the <strong>lab01</strong> virtual machine. To log in, you can use the same credentials as the template machine that we have cloned it from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*78dcAV_cbK6N-DxP-fxOoQ.png" /><figcaption>Image 2</figcaption></figure><p>You can log in to the machine and issue the <strong>sudo shutdown -h now</strong> command to cleanly shut down the machine.</p><h3>Managing Virtual Machine Settings via CLI</h3><p>Our clones will not always need the same amount of resources as the template machine. We can change the resource allocation of the machine from the command-line using virsh.</p><p>For example, we can change the amount of vCPUs allocated to the machine and change it to 1 by running the following command:</p><blockquote>NOTE: After running this command, the number of vCPUs will be set to 1 the next time the machine boots.</blockquote><pre># Reconfigure vCPUs<br>virsh setvcpus lab01 1 --config</pre><p>Similarly, we can change the allocated memory with the command below:</p><blockquote>NOTE: it is important to add MiB because by default the setting is in KiB. If you set the memory to 512KiB, the machine will not start.</blockquote><pre># Reconfigure memory<br>virsh setmem lab01 512MiB --config</pre><p>You use the diff command to see how these changes affect the virtual machine configuration:</p><pre># This shows a diff of the output of the two commands<br>diff &lt;(virsh dumpxml ubuntu22.04) &lt;(virsh dumpxml lab01)</pre><p>This will be the output</p><pre>2,3c2,3<br>&lt;   &lt;name&gt;ubuntu22.04&lt;/name&gt;<br>&lt;   &lt;uuid&gt;c1a22b34-db2b-4f75-944c-4496a1d6f48c&lt;/uuid&gt;<br>---<br>&gt;   &lt;name&gt;lab01&lt;/name&gt;<br>&gt;   &lt;uuid&gt;292f599c-b097-430a-b16a-93dfb4673f1d&lt;/uuid&gt;<br>10,11c10,11<br>&lt;   &lt;currentMemory unit=&#39;KiB&#39;&gt;2097152&lt;/currentMemory&gt;<br>&lt;   &lt;vcpu placement=&#39;static&#39; cpuset=&#39;1&#39;&gt;2&lt;/vcpu&gt;<br>---<br>&gt;   &lt;currentMemory unit=&#39;KiB&#39;&gt;524288&lt;/currentMemory&gt;<br>&gt;   &lt;vcpu placement=&#39;static&#39; cpuset=&#39;1&#39; current=&#39;1&#39;&gt;2&lt;/vcpu&gt;<br>37c37<br>&lt;       &lt;source file=&#39;/data/vmstorage/ubuntu22.04.qcow2&#39;/&gt;<br>---<br>&gt;       &lt;source file=&#39;/data/vmstorage/lab01.qcow2&#39;/&gt;<br>128c128<br>&lt;       &lt;mac address=&#39;52:54:00:91:75:33&#39;/&gt;<br>---<br>&gt;       &lt;mac address=&#39;52:54:00:82:e9:98&#39;/&gt;</pre><p>We can log to the <strong>lab01</strong> machine via VNC to confirm our settings have been correctly applied using the <strong>cat /proc/cpuinfo</strong>, <strong>grep MemTotal /proc/meminfo</strong> and <strong>free -m </strong>commands:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HcgDWnQwA9oolkqkD_fCA.png" /><figcaption>Image 3</figcaption></figure><p>In the output above, we can see that the machine has access to one CPU core and has 512MiB of memory allocated to it.</p><h3>Virtual Machine Manager (Optional)</h3><p>We can also manage our machines via a graphical interface using <strong>Virtual Machine Manager</strong>. This tool allows us to connect to multiple hypervisors to configure and control the virtual machines.</p><p>We will be installing this on a remote laptop since our kvm/qemu host is not running a graphical user interface. The package can be installed with the following command on ubuntu:</p><pre># Install the virt-manager<br>sudo apt install -y virt-manager</pre><p>You can add the connection by opening Virtual Machine Manager and clicking on <strong>File → Add Connection</strong>. You will see the <strong>Add Connection</strong> dialog box pop up. Select <strong>QEMU/KVM</strong> for the Hypervisor, check the<strong> Connect to remote host over SSH</strong> checkbox,<strong> </strong>and fill in your username and ip address. (You can also check autoconnect and the hypervisor connection will be made when you start Virtual Machine Manager)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UCClooVOxwidMFjahcimUw.png" /><figcaption>Image 4</figcaption></figure><p>If you have already set up the ssh connection for your hypervisor using an ssh private/public key pair, the connection will be automatic. I will not be covering ssh key authentication in the guide but, you can easily find instructions on how to do that online (Here is a <a href="https://www.digitalocean.com/community/tutorials/how-to-set-up-ssh-keys-on-ubuntu-20-04">tutorial</a> on Digital Ocean). Just be careful to not overwrite any important ssh keys you might have previously generated.</p><p>If you did not set up ssh key authentication, you will be prompted to enter the password for the username you have entered on the hypervisor host. Once connected, you will see the virtual machines we have created throughout this guide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aaj-zQPyW9eMmOFcdnHQHw.png" /><figcaption>Image 5</figcaption></figure><p>You can configure the machines by double-clicking on the machine you want to configure and switching to the <strong>Show Virtual Hardware Details</strong> tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kbqm5t-nYU0ySOKLEzGRFw.png" /><figcaption>Image 6</figcaption></figure><p>On this screen, you can customize the virtual machine settings such as vCPU and Memory allocation. You can also view the XML output that we dumped on the command-line here.</p><p>If you start the virtual machine by clicking on the <strong>Play</strong> button and switch to the <strong>Show the Graphical Console</strong> tab, you can access the virtual machine console without using VNC directly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXPnmZp-ws-rziuNTbbljw.png" /><figcaption>Image 7</figcaption></figure><p>If you don’t plan on using a direct VNC connection anymore, you can go to the virtual machine configuration screen and set the <strong>Display</strong> <strong>VNC → Address</strong> field to <strong>Localhost only</strong>. Since Virtual Machine Manager uses <strong>SSH Tunneling</strong> to make the connection, it can still access the VNC server using localhost with the added benefit of the connection being encrypted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XjReJeQR_CX7gr7Ndb8RJA.png" /><figcaption>Image 8</figcaption></figure><p>It is worth noting that you can also clone a virtual machine from Virtual Machine Manager by right-clicking on the machine and selecting <strong>clone</strong> but, this will not run the <a href="https://www.libguestfs.org/virt-sysprep.1.html">virt-sysprep</a> tool to make the machine unique on the network.</p><h3>Virtual Machine Snapshots</h3><p>A nice benefit of using Virtual Machines is having the ability to snapshot the state of the machines. This allows for easy testing of changes and to rollback when things break.</p><p>With our <strong>lab01</strong> machine shut down, we can issue the following command to create a new snapshot of the virtual machine:</p><pre># Create snapshot<br>virsh snapshot-create-as - domain lab01 - name &quot;Working State&quot;</pre><p>This will output the following</p><pre>Domain snapshot Working State created</pre><p>We can validate that the snapshot was created with the following command:</p><pre># List snapshots<br>virsh snapshot-list --domain lab01</pre><p>This will be the output</p><pre>Name Creation Time State<br> - - - - - - - - - - - - - - - - - - - - - - - - - - - <br>Working State 2024–03–23 12:04:41 +0000 shutoff</pre><p>We can now start the<strong> lab01 </strong>machine and remove all files in the boot directory to make the machine unbootable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rCkS02nqVv-5lLsEZuyReg.png" /><figcaption>Image 9</figcaption></figure><p>If we then restart the machine using the <strong>sudo shutdown -r now</strong> command, we will end up on the grub rescue prompt because the boot files are missing from the machine disk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y7s-hBKeldUUffzvj3qaDQ.png" /><figcaption>Image 10</figcaption></figure><p>After the machine has been shut down, we can use Virtual Machine Manager or the following command to restore our snapshot:</p><blockquote>NOTE: This command will produce no output</blockquote><pre># Restore snapshot<br>virsh snapshot-revert --domain lab01 --snapshotname &quot;Working State&quot;</pre><p>When we start the lab01 machine using the <strong>virsh start lab01 </strong>command, we can see that our snapshot has been restored and the virtual machine is once again booting successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tt23K_6eEWys6-TwWm6gJA.png" /><figcaption>Image 11</figcaption></figure><p>To clean-up the snapshot we have created, we can use the <strong>snapshot-delete </strong>subcommand. (This will not change the state of the funning machine):</p><pre># Delete snapshot<br>virsh snapshot-delete --domain lab01 --snapshotname &quot;Working State&quot;</pre><p>The output will be the following</p><pre>Domain snapshot Working State deleted</pre><p>That’s all there is to it. You can use this mechanism to create and restore snapshots at various stages of your tests, allowing you to rapidly recreate scenarios in your labs for whatever you are testing or practicing.</p><h3>Summary</h3><p>In this part of the series, we have learned how to clone a virtual machine and make it unique on the network using the virt-sysprep tool. Next, we learned to manage our virtual machines from the command-line as well as using Virtual Machine Manager to access and configure the virtual machines. Finally, we worked with snapshots to quickly save and restore different states of our virtual machines.</p><p>In this three-part tutorial, we were able to create a lightweight, headless (no graphical user interface) virtual machine host using KVM, QEMU, and Libvirt. We then used this virtual machine host to set up multiple virtual machines that can be used together in a network to create virtual machine labs.</p><p>By starting out and configuring the hypervisor using the command-line we are able to gain a deeper understanding of how this works under the hood and are better equipped for troubleshooting in the future.</p><p>Coming to the end of this tutorial, I hope it can help you enhance and expand your knowledge for future challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf4e5f64c0ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-3-virtual-machine-management-cf4e5f64c0ac">Creating a Professional Home Lab Setup -Part 3: Virtual Machine Management</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Professional Home Lab Setup — Part 2: Configuration of the Hypervisors]]></title>
            <link>https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-2-configuration-of-the-hypervisors-8a19c44813e5?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a19c44813e5</guid>
            <category><![CDATA[open-source-software]]></category>
            <category><![CDATA[homelab]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Mon, 12 Feb 2024 15:24:22 GMT</pubDate>
            <atom:updated>2024-03-27T13:30:38.271Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sMTW8D3Zxb_DzNCjvQXeDQ.png" /></figure><h3><strong>Creating a Professional Home Lab Setup — Part 2: Configuration of the Hypervisors</strong></h3><p><em>By Pascal Van Acker</em></p><h4>Introduction</h4><p>This is part 2 of a 3-part series:</p><ul><li><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-1-installing-the-operating-system-cfb4839fc796">Part 1</a> covers the installation of the Ubuntu operating system on a bare-metal machine.</li><li><a href="https://tadaweb.medium.com/8a19c44813e5?sk=63fd2e36080d1e8e5fbebd73a69bd331">Part 2</a> covers the setup and configuration of the <a href="https://linux-kvm.org/">KVM</a> and <a href="https://www.qemu.org/">QEMU</a> hypervisors with an API on top using <a href="https://libvirt.org/">libvirt</a>. We will also install our first virtual machine.</li><li><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-3-virtual-machine-management-cf4e5f64c0ac">Part 3</a> covers virtual machine management and the process of cloning virtual machines and using the <a href="https://www.libguestfs.org/virt-sysprep.1.html">virt-sysprep</a> tool to make the cloned machine unique in the network.</li></ul><p>In this part of the tutorial, we will continue to set up our new Ubuntu server as a hypervisor (or virtual machine host). There are quite a few hypervisors that we can choose from, such as <a href="https://www.virtualbox.org/">Oracle VirtualBox</a>, <a href="https://www.ovirt.org/">oVirt</a>, <a href="https://www.proxmox.com/">Proxmox</a>, <a href="https://www.vmware.com/be/products/esxi-and-esx.html">VMWare ESXI</a>, <a href="https://www.xenserver.com/">XenServer</a>, and probably a lot more. I chose KVM+QEMU for a couple of reasons:</p><ul><li>I already had a desktop computer running Ubuntu 22.04 in my living room that was acting as a <a href="https://en.wikipedia.org/wiki/Home_theater_PC">Home Theater PC</a> which was quite overpowered making it the perfect candidate to act as a hypervisor. Since it was already running Linux, KVM+QEMU was a good choice.</li><li>I wanted to keep things minimal and free and I was not interested in all the bells and whistles of a full management suite. KVM+QEMU can easily be managed locally via the command-line or remotely using <a href="https://en.wikipedia.org/wiki/Secure_Shell">SSH</a> and <a href="https://en.wikipedia.org/wiki/Virtual_Network_Computing">VNC</a> without much overhead.</li><li>KVM+QEMU provides all the capabilities I need for a lab setup such as hardware emulation, networking, cloning, and snapshots/restores of virtual machines.</li></ul><h4>Prerequisites</h4><p>At this point, we expect to have a physical machine with <a href="https://ubuntu.com/">Ubuntu</a> 22.04 LTS already set up. If you do not have that, you can follow <a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-1-installing-the-operating-system-cfb4839fc796">part 1</a> of this series and come back to part 2 later. If you are running a different version of Ubuntu, or a different Linux distribution altogether, the package names and versions might be different and the steps in this tutorial might not work.</p><p>Additionally, for virtualization to work, you need to make sure that virtualization extensions are supported by your CPU, and that these virtualization extensions are enabled in the BIOS. They are often enabled by default but, not always. The process to enable the extensions is specific for each manufacturer and motherboard model.</p><h4>Enabling Virtualization in the BIOS</h4><p>If your system is already booted up, you can install the <strong>CPU-checker</strong> package and run the <strong>KVM-ok </strong>command to make sure your computer is able to run KVM.</p><pre># Install cpu-checker <br>sudo apt -y install cpu-checker<br><br># Check CPU compatibility <br>sudo kvm-ok </pre><p>The expected output is below:</p><pre>INFO: /dev/kvm exists <br>KVM acceleration can be used</pre><p>If you see the message below, the extensions in the BIOS might not have been enabled correctly, or the CPU is unsuitable for usage as a hypervisor with KVM:</p><pre>INFO: Your CPU does not support KVM extensions <br>KVM acceleration can NOT be used</pre><p>To enter the BIOS, you have to repeatedly press a key such as <strong>F1, F11, F12,</strong> or<strong> delete</strong> during system startup. Once there, you have to look for settings with names such as <strong>VT-x</strong>, <strong>VT-d</strong>, <strong>AMD-V</strong>, <strong>SVM</strong> or <strong>Intel Virtualization Technology</strong> and enable them. It is best to search for the specific instructions of your motherboard in the manual or online.</p><h4>Installation of the Packages and Services</h4><p>After we have successfully confirmed that the CPU extensions are available and enabled, we can continue setting up the machine.</p><p>The first thing we need to do is install the packages needed to run our hypervisor. We will also update our packages to the latest version while we are at it:</p><pre># refresh packages (update system) <br>sudo apt update &amp;&amp; sudo apt -y upgrade <br> <br># install bash-completion and curl <br>sudo apt -y install bash-completion curl<br><br># install the KVM/QEMU hypervisors and libvirt <br>sudo apt -y install \ <br> bridge-utils \ <br> libvirt-clients \ <br> libvirt-daemon \ <br> libvirt-daemon-system \ <br> qemu \ <br> qemu-kvm</pre><p>The <strong>bash-completion</strong> package will make it easier for us to discover how to use <strong>virsh</strong> commands by enabling TAB-completion on the command-line. This is not installed by default on a minimal installation of Ubuntu. We will use the <strong>curl </strong>utility to download an Ubuntu ISO image from the command-line later in the tutorial.</p><p>Next, we will install the <strong>virtinst</strong> convenience tool. This is useful for provisioning virtual machines from scratch. If you are running a graphical desktop or have a Linux desktop somewhere in your network, you can install the <a href="https://virt-manager.org/"><strong>virt-manager</strong></a> tool instead. Since we are using a headless server in this tutorial, we will stick to <strong>virt-install</strong>.</p><pre># install the virt-install tool<br>sudo apt -y install virtinst</pre><p>After installing our packages, we need to make sure that the <strong>libvirtd</strong> service is running and will automatically be started each time we start the machine. This can easily be done using the following commands:</p><pre># start and enable libvirtd <br>sudo systemctl enable --now libvirtd</pre><pre># check libvirtd status <br>sudo systemctl status libvirtd</pre><h4>Configuring User Access</h4><p>For convenience, we will give our user access tot he libvirt API by adding the user to the <strong>libvirtd</strong> group. This can be done by using the command below followed by a logout + login on the system. (change the username <strong>pascal</strong> to your username on the system)</p><pre># add our user to the libvirtd group<br>sudo usermod -a -G libvirtd pascal</pre><h4>Creating a New Storage Pool (optional)</h4><p>Creating a storage pool is optional but, it is nice to organize and choose a path other than the default <strong>/var/lib/libvirt/images</strong> to store our data. That way, we can store the data on any mounted disk or network storage device and easily find our data without remembering the default path.</p><p>We start by listing the current storage pools available on the system:</p><pre># Note: you can type a partial command and hit the TAB key to discover <br># possible sub-commands<br>virsh pool-&lt;TAB&gt;<br>pool-autostart pool-edit <br>pool-build pool-event <br>pool-capabilities pool-info <br>pool-create pool-list <br>pool-create-as pool-name <br>pool-define pool-refresh <br>pool-define-as pool-start <br>pool-delete pool-undefine <br>pool-destroy pool-uuid <br>pool-dumpxml</pre><pre># list existing storage pools<br>virsh pool-list<br>Name State Autostart <br> - - - - - - - - - - - - - - - - <br> default active yes</pre><p>Then we dump the configuration of the default pool to find out how a storage pool is defined:</p><pre># dump default storage pool information<br>virsh pool-dumpxml default</pre><p>This will produce the following output (the uuid and sizes will be different for you):</p><pre>&lt;pool type=&#39;dir&#39;&gt; <br> &lt;name&gt;default&lt;/name&gt; <br> &lt;uuid&gt;c263b4d0–9e50–46ca-8cc4–5128e3b41a67&lt;/uuid&gt; <br> &lt;capacity unit=&#39;bytes&#39;&gt;79986151424&lt;/capacity&gt; <br> &lt;allocation unit=&#39;bytes&#39;&gt;26132226048&lt;/allocation&gt; <br> &lt;available unit=&#39;bytes&#39;&gt;53853925376&lt;/available&gt; <br> &lt;source&gt; <br> &lt;/source&gt; <br> &lt;target&gt; <br> &lt;path&gt;/var/lib/libvirt/images&lt;/path&gt; <br> &lt;permissions&gt; <br> &lt;mode&gt;0711&lt;/mode&gt; <br> &lt;owner&gt;0&lt;/owner&gt; <br> &lt;group&gt;0&lt;/group&gt; <br> &lt;/permissions&gt; <br> &lt;/target&gt; <br>&lt;/pool&gt;</pre><p>Next, we will create the directory <strong>/data/vmstorage </strong>that will be used as our storage. You can change this path to any place on the system and it can reference a local disk or mounted network drive. For the best performance however, it is recommended to use a local storage device with plenty of space to store virtual machine disks unless you have a very fast network connection with low latency to the external storage.</p><pre># Make the storage directory<br>mkdir -p /data/vmstorage</pre><p>Finally, we can create our own storage pool called <strong>vmstorage</strong> that will use the previously created directory <strong>/data/vmstorage </strong>for storage (replace the path with your chosen directory in the command below):</p><pre>cat &lt;&lt;EOF | virsh pool-define --file /dev/stdin <br>&lt;pool type=&#39;dir&#39;&gt; <br> &lt;name&gt;vmstorage&lt;/name&gt; <br> &lt;target&gt; <br> &lt;path&gt;/data/vmstorage&lt;/path&gt; <br> &lt;permissions&gt; <br> &lt;mode&gt;0775&lt;/mode&gt; <br> &lt;owner&gt;$(echo $UID)&lt;/owner&gt; <br> &lt;/permissions&gt; <br> &lt;/target&gt; <br>&lt;/pool&gt; <br>EOF</pre><p>This will output the following</p><pre>Pool vmstorage defined from /dev/stdin</pre><p><em>Note: If you make a mistake, you can use the command </em><strong><em>virsh pool-undefine</em></strong><em> </em><strong><em>&lt;name&gt;</em></strong><em> to remove the pool and start over. If the pool is already activated (see below), you will first have to run </em><strong><em>virsh pool-destroy &lt;name&gt;</em></strong><em>.</em></p><p>If we list our storage pools now, we can see that the new storage pool is not yet listed:</p><pre># List storage pools<br>virsh pool-list</pre><p>This will output the following</p><pre>Name State Autostart <br> - - - - - - - - - - - - - - - - <br> default active yes</pre><p>This is because we will need to <strong>start</strong> and <strong>autostart</strong> the pool for it to be usable by libvirt:</p><pre># start the pool <br>virsh pool-start vmstorage<br><br># autostart the pool <br>virsh pool-autostart vmstorage</pre><p>This will output</p><pre>Pool vmstorage started<br><br>Pool vmstorage marked as autostarted</pre><p>If you run <strong>virsh pool-list</strong> again, the pool will be listed as active and <strong>autostart</strong> will be set to <strong>yes</strong>.</p><pre># List storage pools<br>virsh pool-list</pre><p>This will be the output</p><pre>Name State Autostart <br> - - - - - - - - - - - - - - - - - <br> default active yes <br> vmstorage active yes</pre><h4>Creating a Lab Network (optional)</h4><p>Creating a dedicated network for your lab is optional but, again, it is nice to be able to segregate and organize your virtual machines in a dedicated network. The process of creating the network is quite similar to creating a storage pool.</p><p>Once again, we start by listing the existing networks:</p><pre># List networks<br>virsh net-list</pre><p>The output will be</p><pre>Name State Autostart Persistent <br> - - - - - - - - - - - - - - - - - - - - - - <br> default active yes yes</pre><p>Next, we will dump the <strong>default</strong> network to learn how we can define our own network:</p><pre># Dump default network<br>virsh net-dumpxml default</pre><p>The output will be similar to the one below</p><pre>&lt;network&gt; <br> &lt;name&gt;default&lt;/name&gt; <br> &lt;uuid&gt;1be34b43-b18a-4aa7-a804–087d6439843f&lt;/uuid&gt; <br> &lt;forward mode=&#39;nat&#39;&gt; <br> &lt;nat&gt; <br> &lt;port start=&#39;1024&#39; end=&#39;65535&#39;/&gt; <br> &lt;/nat&gt; <br> &lt;/forward&gt; <br> &lt;bridge name=&#39;virbr0&#39; stp=&#39;on&#39; delay=&#39;0&#39;/&gt; <br> &lt;mac address=&#39;52:54:00:49:8d:ca&#39;/&gt; <br> &lt;ip address=&#39;192.168.122.1&#39; netmask=&#39;255.255.255.0&#39;&gt; <br> &lt;dhcp&gt; <br> &lt;range start=&#39;192.168.122.2&#39; end=&#39;192.168.122.254&#39;/&gt; <br> &lt;/dhcp&gt; <br> &lt;/ip&gt; <br>&lt;/network&gt;</pre><p>Then, we will create a new <a href="https://nl.wikipedia.org/wiki/Network_address_translation">NAT</a> network using the subnet <strong>10.200.0.0/24</strong> (netmask <strong>255.255.255.0</strong>) with the gateway address of <strong>10.200.0.1</strong> by running the following command:</p><pre># Note: Feel free to change the name, subnet, and forwarded port ranges <br># as you desire but, take care with the subnet ranges and IP-addresses. <br># Don&#39;t use any subnet ranges that are already used on the host system <br># and never use the network-address or broadcast-address as the ip address<br># in your configuration. If you configure this setting incorrectly, you <br># will not be able to communicate with the virtual machine due to <br># routing issues. You can use a subnet-calculator to be sure.<br><br>cat &lt;&lt;EOF | virsh net-define --file /dev/stdin <br>&lt;network&gt; <br> &lt;name&gt;vmlab&lt;/name&gt; <br> &lt;forward mode=&#39;nat&#39;&gt; <br> &lt;nat&gt; <br> &lt;port start=&#39;1024&#39; end=&#39;65535&#39;/&gt; <br> &lt;/nat&gt; <br> &lt;/forward&gt; <br> &lt;ip address=&#39;10.200.0.1&#39; netmask=&#39;255.255.255.0&#39;&gt; <br> &lt;dhcp&gt; <br> &lt;range start=&#39;10.200.0.2&#39; end=&#39;10.200.0.254&#39;/&gt; <br> &lt;/dhcp&gt; <br> &lt;/ip&gt; <br>&lt;/network&gt; <br>EOF</pre><p>This will be the output</p><pre>Network vmlab defined from /dev/stdin</pre><p>We can see the new network by running the <strong>virsh net-list</strong> command with the --<strong>all</strong> flag. The network is not yet started so we have <strong>start</strong> it and set <strong>autostart</strong> as we did with the storage pool:</p><pre># list networks <br>virsh net-list --all<br><br># start the network <br>virsh net-start vmlab<br><br># autostart the network <br>virsh net-autostart vmlab</pre><p>This will be the output</p><pre>Name State Autostart Persistent <br> - - - - - - - - - - - - - - - - - - - - - - - <br> default active yes yes <br> vmlab inactive no yes<br><br>Network vmlab started<br><br>Network vmlab marked as autostarted</pre><p>To see our newly defined network, we can once again use the <strong>virsh net-dumpxml</strong> command to see the network details:</p><pre># Dump our new network<br>virsh net-dumpxml vmlab</pre><p>This will be the output</p><pre>&lt;network&gt; <br> &lt;name&gt;vmlab&lt;/name&gt; <br> &lt;uuid&gt;768c4829-a49a-4d5d-8d36-f0fb1992d389&lt;/uuid&gt; <br> &lt;forward mode=&#39;nat&#39;&gt; <br> &lt;nat&gt; <br> &lt;port start=&#39;1024&#39; end=&#39;65535&#39;/&gt; <br> &lt;/nat&gt; <br> &lt;/forward&gt; <br> &lt;bridge name=&#39;virbr1&#39; stp=&#39;on&#39; delay=&#39;0&#39;/&gt; <br> &lt;mac address=&#39;52:54:00:2f:de:4f&#39;/&gt; <br> &lt;ip address=&#39;10.200.0.1&#39; netmask=&#39;255.255.255.0&#39;&gt; <br> &lt;dhcp&gt; <br> &lt;range start=&#39;10.200.0.2&#39; end=&#39;10.200.0.254&#39;/&gt; <br> &lt;/dhcp&gt; <br> &lt;/ip&gt; <br>&lt;/network&gt;</pre><p>As you can see from the output above, the network has been created with the settings we have specified and a<strong> bridge interface</strong>,<strong> uuid</strong> and <strong>mac address</strong> have automatically been generated for us.</p><h4>Creating a Virtual Machine</h4><p>There are multiple ways to create a new virtual machine with libvirt. We could create it using an XML spec like we did for the storage pool and network above but, we do not yet have a virtual machine that we can copy, and the spec is quite large so we really don’t want to write it from scratch. That is exactly why we installed the <strong>virt-install </strong>utility earlier. It will greatly simplify defining new virtual machines.</p><blockquote>Note: If you have <strong>virt-manager </strong>installed on a graphical destkop, you can use that to create the virtual machine instead. You can find more information on the RedHat Enterprise Linux documentation <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_host_configuration_and_guest_installation_guide/chap-virtualization_host_configuration_and_guest_installation_guide-guest_installation_virt_manager-creating_guests_with_virt_manager">here</a>.</blockquote><p>We can list the virtual machines on the system with the commands below (We don’t have any yet, so the list will be empty):</p><pre># list active (running) virtual machines <br>virsh list<br><br># list all virtual machines <br>virsh list --all </pre><p>This will be the output</p><pre>Id Name State <br> - - - - - - - - - -<br><br>Id Name State <br> - - - - - - - - - - - - - - - - - - - -</pre><p>To create a virtual machine, we will first need to download an ISO image of the operating system we want to install on our virtual machine and place it in our storage pool. For the tutorial, we will be using Ubuntu 22.04 LTS (the same operating system as the host). You can download it via the command-line using <strong>curl</strong>. You can navigate to the <a href="https://releases.ubuntu.com/jammy/">ubuntu releases</a> page for <strong>jammy</strong> (the code-name of 22.04) to find up to date links for the download by using the <strong>Copy Link</strong> functionality of your browser (choose the <strong>Server install image</strong>).</p><blockquote>Note: The <strong>curl</strong> command will report the current state of the download and once it has been completed, you will be returned to the shell.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dc7uvd4ozAhKTM4yTaZDkw.png" /><figcaption>Image 1</figcaption></figure><pre># Download ubuntu 22.04 iso image<br> curl -LO https://releases.ubuntu.com/20.04.6/ubuntu-20.04.6-live-server-amd64.iso</pre><pre># Move image to our storage pool<br> mv ubuntu-20.04.6-live-server-amd64.iso /data/vmstorage/</pre><p>We have to find the IP address of our machine in the network prior to starting the installation as it will block the terminal and we need the IP to connect to the remote console during installation:</p><pre># List ip address for the hostname (in /etc/hosts)<br># If this returns a 127.x.x.x (localhost) address<br># use the second command instead<br>hostname -i<br><br><br># Return all ip addresses of the machine<br>hostname -I</pre><p>The output will be similar to this</p><pre>127.0.1.1<br><br>192.168.1.11 192.168.122.1 10.200.0.0 …</pre><p>You can see that the IP address of the machine, on my network, is <strong>192.168.1.11</strong>.</p><p>After the download has completed, we can use the <strong>virt-install</strong> utility to define a new virtual machine using this image. The following command will create an Ubuntu 22.04 virtual machine with 1vCPU, 2048 Megabytes of RAM and a 20GB hard disk. It will also add a <a href="https://en.wikipedia.org/wiki/Virtual_Network_Computing">VNC</a> console through which we can complete the operating system installation process.</p><blockquote>Note: I added the option <strong>listen=0.0.0.0</strong> to the<strong> --graphics</strong> flag. It will make sure the VNC server listens on all IP-addresses of the machine and not just localhost (<strong>127.0.0.1</strong>). This way we can directly connect from another machine on the network using a VNC client and without setting up an <a href="https://goteleport.com/blog/ssh-tunneling-explained/">SSH tunnel</a>. If you know what you are doing, you can use an SSH tunnel when connecting to VNC and omit this option.</blockquote><pre>virt-install \<br>--name ubuntu22.04 \<br>--cpus 1 \<br>--memory 2048 \<br>--disk &quot;pool=vmstorage,size=20&quot; \<br>--os-variant &quot;ubuntu22.04&quot; \<br>--network &quot;network=vmlab&quot; \<br>--console &quot;pty,target_type=serial&quot; \<br>--graphics vnc,listen=0.0.0.0 \<br>--cdrom &quot;/data/vmstorage/ubuntu-20.04.6-live-server-amd64.iso&quot;</pre><p>This should output the following</p><pre> WARNING Graphics requested but DISPLAY is not set. Not running virt-viewer.<br> WARNING No console to launch for the guest, defaulting to - wait -1<br> Starting install…<br> Allocating &#39;ubuntu22.04–3.qcow2&#39; | 4.9 MB 00:00:03 … Creating domain… | 0 B 00:00:00<br> …<br>Domain is still running. Installation may be in progress.<br> Waiting for the installation to complete.</pre><p>The installation of the new virtual machine (or <strong>domain</strong> in libvirt terminology) has started. At this point you can remotely connect to the machine using a VNC client. The VNC server will start assigning ports for graphical consoles from <strong>5900</strong> onward but, you can chose a custom port by adding <strong>port=&lt;port&gt;</strong> to the <strong>--graphics</strong> options. Since we did not specify that and have only one virtual machine started, the port will be <strong>5900</strong>.</p><p>On my desktop computer that is running Window 11, I use <a href="https://www.realvnc.com/">RealVNC</a> to connect to the server. On my laptop that is running Linux, I use <a href="https://remmina.org/">Remmina</a> as my VNC client. The process of adding and using a connection should be quite similar across different clients. I will use RealVNC in this tutorial.</p><p>You can add a new connection by navigating to<strong> File &gt; New</strong> <strong>Connection</strong> or by<strong> </strong>pressing <strong>CTRL+N</strong> and filling the <strong>VNC Server</strong> field with the IP-address and port of your VNC server. You can find that in the output of the<strong> hostname </strong>command we ran above, in my case it is <strong>192.168.1.11:5900</strong>. Click on <strong>OK </strong>to add the connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/881/1*Bdbk7JpT4Y5kwqRN3MbICQ.png" /><figcaption>Image 2</figcaption></figure><p>After adding the connection, when you <strong>double-click</strong> on the new connection, you will receive a warning that the connection is not encrypted. This is completely true (unless you are using an SSH Tunnel) and we don’t really care about it because we are in our local network. Click <strong>Continue</strong> to connect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*T5Z2rzO_b4wjRJeo-eoUTQ.png" /><figcaption>Image 3</figcaption></figure><p>You will be greeted by the trusty Ubuntu installer once again, But this time on a remote virtual machine that is running on your KVM+QEMU server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*4Tdhj_kT1_wnpAWzwdpB_A.png" /><figcaption>Image 4</figcaption></figure><p>You can follow the same instructions detailed in <a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-1-installing-the-operating-system-cfb4839fc796">part 1</a> to install the virtual machine (Don’t worry if the installer complains that it cannot remove the CD-ROM from the drive at the end, you can ignore it and reboot). Once the setup has been completed. The machine will reboot and you will be presented with the login screen. Login with your user account and password chosen during installation and use the <strong>hostname -i</strong> or <strong>hostname -I</strong> commands to find the IP-address of the virtual machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n3cQv-iAOaHoKG1BhbecvQ.png" /><figcaption>Image 5</figcaption></figure><p>Additionally, you can query the IP-address from the hypervisor:</p><pre># List network DHCP leases<br>virsh net-dhcp-leases --network vmlab</pre><p>This will give you the following output</p><pre>Expiry Time MAC address Protocol IP address Hostname Client ID or DUID<br> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>2024–01–20 17:47:35 52:54:00:bb:12:67 ipv4 10.200.0.105/24 vm01 ff:56:50:4d:98:00:02:00:00:ab:11:fa:09:85:7e:26:57:64:ba</pre><p>We can see that the machine is running by using the <strong>virsh list </strong>command.</p><pre># List virtual machines<br>virsh list</pre><p>This will output the following</p><pre>Id Name State<br> - - - - - - - - - - - - - - - - - - - -<br> 1 ubuntu22.04 running</pre><p>In libvirt terminology, a virtual machine is called as a <strong>domain</strong>. You can shut down your virtual machine by running the following command on the hypervisor:</p><pre># destroy shuts down the machine but does not delete it<br>virsh destroy --domain ubuntu22.04</pre><p>To restart the machine later, you can use <strong>virsh start --domain ubuntu22.04</strong>:</p><pre># start virtual machine<br>virsh start --domain ubuntu22.04</pre><p>If at any point you want to delete the machine, you can use <strong>virsh undefine</strong>.</p><pre># Delete virtual machine<br>virsh undefine ubuntu22.04</pre><p>By default, the storage of the machines is not cleaned up. You can clean them up using the <strong>virsh</strong> volume subcommands:</p><pre># List volumes in vmstorage storage pool<br>virsh vol-list --pool vmstorage</pre><p>This is the output you should expect</p><pre>Name Path<br> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>ubuntu-20.04.6-live-server-amd64.iso /data/vmstorage/ubuntu-20.04.6-live-server-amd64.iso<br>ubuntu22.04.qcow2 /data/vmstorage/ubuntu22.04.qcow2</pre><p>To delete the volume, use the following command</p><pre>virsh vol-delete --pool vmstorage ubuntu22.04.qcow2</pre><h3>Summary</h3><p>In this part of the tutorial, we have configured our hypervisor and setup our first virtual machine (or guest). In the process, we have learned to how create our own storage pools and how to add NAT networks to isolate virtual machines in dedicated networks. Lastly, we have learned how to connect to a graphical console provided by the VNC protocol to finish the guest operating system installation (which can also be helpful when troubleshooting).</p><p>In the next and final part we will discuss virtual machine management techniques such as cloning and <strong>sys-prepping</strong> to avoid having to install more operating systems from scratch and we might take a look at the <strong>virt-manager</strong> tool on a graphical Linux desktop.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a19c44813e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-2-configuration-of-the-hypervisors-8a19c44813e5">Creating a Professional Home Lab Setup — Part 2: Configuration of the Hypervisors</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Professional Home Lab Setup — Part 1: Installing the Operating System]]></title>
            <link>https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-1-installing-the-operating-system-cfb4839fc796?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfb4839fc796</guid>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[sre]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Tue, 09 Jan 2024 09:21:07 GMT</pubDate>
            <atom:updated>2024-03-27T13:30:18.645Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ig3RedJBtXKz0zmHPFclkw.png" /></figure><h3>Creating a Professional Home Lab Setup — Part 1: Installing the Operating System</h3><h4><em>Tadaweb’s SRE team has recently aced the Certified Kubernetes Administrators (CKA) certification. When they needed some infrastructure for the course, some members of the SRE team built their own lab server. Pascal, one team member, is sharing a tutorial for anyone keen on taking the same route. Discover more here.</em></h4><p><em>By Pascal Van Acker</em></p><h4>Preface</h4><p>Not too long ago, the Site Reliability Engineering team at Tadaweb was tasked with taking the Certified Kubernetes Administrator (CKA) certification. The team members were provided with access to the <a href="https://training.linuxfoundation.org/training/kubernetes-fundamentals-lfs258-cka-exam-bundle/">Kubernetes Fundamentals (LFS258) + CKA Exam Bundle</a> training and online exam created by the <a href="https://training.linuxfoundation.org/">Linux Foundation</a>. The entire team ended up passing this certification with high scores on the first try which is something we can all be proud of.</p><p>During the training, our team required some IT infrastructure to complete the course’s lab exercises. The way this infrastructure was provisioned varied greatly between each different member of the team. Some used a simple <a href="https://kind.sigs.k8s.io/">kind</a> cluster, others used automation tools like <a href="https://www.vagrantup.com/">Vagrant</a> to spin up temporary Virtual Machines and, I went for a somewhat more permanent setup by installing Ubuntu Server on a spare desktop computer I had received from Tadaweb not too long ago.</p><p>After I had completed my new server installation using KVM and QEMU as the hypervisor software, I decided to share the setup commands with one of my team members. I received overwhelmingly positive feedback after supporting this team member with his new server setup and was inspired to create this tutorial.</p><h4>Prerequisites</h4><p>We recommend that you have basic knowledge of installing computers, partitioning disks, using the Linux shell, and have some basic understanding of networking (Such as NAT vs Bridged networking). If not, you should still be able to follow the steps in this tutorial, but troubleshooting might become a challenging task.</p><h4>Introduction</h4><p>Virtualization is everywhere! It allows for increased <strong>flexibility</strong> and <strong>scalability</strong> of your IT organization and provides advanced features such as <strong>snapshots</strong> and <strong>live migrations</strong>. In addition to that it is also useful for individuals setting up a home lab for experimenting and learning, which is exactly what we will be covering in this 3-part tutorial.</p><ul><li><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-1-installing-the-operating-system-cfb4839fc796">Part 1</a> covers the installation of the Ubuntu operating system on a bare-metal machine.</li><li><a href="https://tadaweb.medium.com/8a19c44813e5?sk=63fd2e36080d1e8e5fbebd73a69bd331">Part 2</a> covers the setup and configuration of the <a href="https://linux-kvm.org/">KVM</a> and <a href="https://www.qemu.org/">QEMU</a> hypervisors with an API on top using <a href="https://libvirt.org/">libvirt</a>. We will also install our first virtual machine.</li><li><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-3-virtual-machine-management-cf4e5f64c0ac">Part 3</a> covers virtual machine management and the process of cloning virtual machines and using the <a href="https://www.libguestfs.org/virt-sysprep.1.html">virt-sysprep</a> tool to make the cloned machine unique in the network.</li></ul><p>If you decide to use your workstation or another machine that is already running Ubuntu 22.04 Server or Desktop, you can skip this part of the tutorial and jump directly to part 2.</p><h4>Installing the Operating System</h4><p>To get started, we will need a computer or laptop dedicated to becoming a hypervisor. We will be installing the <strong>Ubuntu 22.04 LTS Server Edition </strong>operating system on the machine to act as a base server for our hypervisor. You can download the installer image of Ubuntu <a href="https://ubuntu.com/download/server#downloads">here</a> for free. Take care to choose the right version of Ubuntu to have the most success following this tutorial.</p><p>We will install the server edition of Ubuntu since we do not need a graphical interface and it will make the installation more lightweight. You are free to choose the desktop edition if you also plan to use the machine as a workstation but, keep in mind that the installation process will be different.</p><p>The process of creating a bootable USB stick to install Ubuntu is already well-documented on the Ubuntu website and we will not cover it in this tutorial. Please follow the links below if you need help with this step.</p><ul><li><a href="https://ubuntu.com/tutorials/create-a-usb-stick-on-windows#1-overview">Create a USB stick on Windows</a></li><li><a href="https://ubuntu.com/tutorials/create-a-usb-stick-on-macos#1-overview">Create a USB stick on MacOS</a></li><li><a href="https://ubuntu.com/tutorials/create-a-usb-stick-on-ubuntu#1-overview">Create a USB stick on Ubuntu</a></li></ul><p>After booting your machine with the installation USB stick, you will see the grub bootloader. On this page select <strong>Try or Install Ubuntu Server </strong>by highlighting it and pressing the <strong>Return/Enter</strong> key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*eDU4UsQ4lNsVtf3CQqdHTg.png" /><figcaption>Image 1</figcaption></figure><p>You will be greeted by the Ubuntu installer. You can use your keyboard’s<strong> arrow keys</strong> to move around, press the <strong>Return/Enter </strong>key to select or confirm and press the <strong>space bar </strong>to toggle checkboxes. On the first page, choose your preferred language. We will select <strong>English</strong> by highlighting it and pressing the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*HQrSfLibVMdEYikcRvpavw.png" /><figcaption>Image 2</figcaption></figure><p>It is possible that you are prompted to update the installer to a newer version. Unless you are aware of a specific bug in the installer, you can skip this and select <strong>Continue Without Updating</strong> by highlighting the option and pressing the <strong>Return/Enter </strong>key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*d1WKfBTdv9qKI-Y1hBhesg.png" /><figcaption>Image 3</figcaption></figure><p>On the next screen, set the keyboard layout. We will be using <strong>English (US)</strong> but, feel free to change it to your preferred keyboard. When you are satisfied select <strong>Done </strong>and press the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*MWv-5f0jO2jzs8C_JQARCA.png" /><figcaption>Image 4</figcaption></figure><p>On the <strong>Choose type of install</strong> screen, we will select <strong>Ubuntu Server (minimized)</strong> option to keep the system lightweight (this is not selected by default). Then select <strong>Done </strong>and press the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*BW6ybi478sK6I5Ug6Kx60w.png" /><figcaption>Image 5</figcaption></figure><p>The <strong>Network Connections</strong> screen allows you to customize the networking of the machine and set a static IP address. For this tutorial we will be choosing the default DHCP option but, you may want to use a static IP address for convenience. Note that our IP address is 10.2.1.231/16. This is because we used a virtual machine to document the setup process. You are more likely to see an IP address within the 192.168.0.0/24 range if you are installing it on a machine in your home network. Select <strong>Done</strong> followed by pressing the <strong>Return/Enter </strong>key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*XopFdPUG81aAWotRNPZp5g.png" /><figcaption>Image 6</figcaption></figure><p>On the next screen you will have the option to configure an HTTP proxy. If you do not know what this is, it is unlikely that you are using one to access the internet. Leave the form blank and select <strong>Done</strong> followed by pressing the <strong>Return/Enter </strong>key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*OPnMfZUTQzpiY0eJe9m0lA.png" /><figcaption>Image 7</figcaption></figure><p>The installer will search for a suitable package repository mirror (this contains all the applications you can install on the system). It will select the one with the best performance (speeds and latency) based on a test. From our location, the Belgian mirror was selected. Select <strong>Done</strong> followed by pressing the <strong>Return/Enter </strong>key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*vU4skDwuPwYirXacxI4vmg.png" /><figcaption>Image 8</figcaption></figure><p>The <strong>Guided storage configuration </strong>screen will present you with the opportunity to customize the storage configuration (partitioning of disks). Note that the hard disk shown below indicates we are using a virtual machine. When installed on bare metal this will show the manufacturer make and model of the drive (For example: Seagate, Western Digital, Samsung, etc…) or it could just show /dev/sda. We will keep the default option, use the entire disk, and set up partitions using LVM (<a href="https://www.redhat.com/sysadmin/lvm-vs-partitioning">Logical Volume Manager</a>). This will make it easier to extend the storage of the partitions later by adding extra physical disks if needed.</p><p><strong>WARNING: If you are installing Ubuntu on a computer or hard drive that already has an operating system installed or has important data on the disk, that operating system and data on the drive will be removed and you will lose all data. This tutorial assumes that you are using a spare computer with a blank disk or disk that has no important data on it.</strong></p><p>If you are satisfied, select <strong>Done</strong> and press the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*-RQFfztyFw3QWzGdpEmmrQ.png" /><figcaption>Image 9</figcaption></figure><p>The next screen will show a summary of the changes that will be made to the system. Select <strong>Done</strong> followed by pressing the <strong>Return/Enter </strong>key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*XWh9Pq4NrcZDrUfMPoCeGA.png" /><figcaption>Image 10</figcaption></figure><p>You will be shown a final warning to prevent unwanted data loss. Select <strong>Continue</strong> and press the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*p6AVYLV9IgXOZ67bhefJ_w.png" /><figcaption>Image 11</figcaption></figure><p>The installer will prepare the disk and start the installation process in the background. In the meantime, you will be prompted to setup the machine name and configure primary user account on the server. Feel free to be creative in picking a username. For the tutorial I will just use my name and a machine name of <strong>kvm</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*ZWA6Cu5WCMyrVuQCJ52SxQ.png" /><figcaption>Image 12</figcaption></figure><p>On the next screen, you will be asked if you want to upgrade to Ubuntu Pro. For our lab setup, we do not need this. Select <strong>Skip for now</strong> followed by selecting <strong>Continue</strong> and pressing the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*NxBoDqH1hyOEVk67hXLeqQ.png" /><figcaption>Image 13</figcaption></figure><p>You will then be prompted by a screen asking you if you want to install the OpenSSH server. It is advisable to do so since this will allow you to remotely access the machine. Select the <strong>Install OpenSSH server</strong> option followed by selecting <strong>Done</strong> and pressing the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*74GAGUhjhL8vWNE_U3DcFA.png" /><figcaption>Image 14</figcaption></figure><p>You will be asked to install additional packages on the system during the installation. Do not select any and just select <strong>Done </strong>followed by pressing the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*kfwfuNI6haJgov2lYDy4GA.png" /><figcaption>Image 15</figcaption></figure><p>Finally, you will see the <strong>Install Complete! </strong>screen. The installation is still running and installing package updates or configuring the system. Wait until the <strong>Cancel update and reboot</strong> option changes to <strong>Reboot Now</strong>. When it becomes available, select the option <strong>Reboot Now</strong> and press the <strong>Return/Enter</strong> key to continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*U0H27ziw27jpNjIQoEGShg.png" /><figcaption>Image 16</figcaption></figure><p>You will see one more screen telling you to remove the installation medium (USB stick) and press ENTER to continue. Follow the instructions and press the <strong>Return/Enter</strong> key to reboot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*WcYwewNSdtcRK7lmU1VAKw.png" /><figcaption>Image 17</figcaption></figure><p>After a reboot, you will see the login prompt of your ubuntu server installation. You can enter to details provided in the installer to login. In our case the username was <strong>pascal</strong> with a password of <strong>password</strong> (this is just for the tutorial, use proper password hygiene on actual servers!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*MYjvtV99b6eFtT7ikkOzjw.png" /><figcaption>Image 18</figcaption></figure><p>Once you are logged in, you can use the following command to turn off the machine:</p><pre>sudo shutdown –h now</pre><p>(The <strong>–h</strong> flag tells the command to “halt” the system. You could use the <strong>-r</strong> flag instead to reboot)</p><h3>Summary</h3><p>In this part of the tutorial, we have created our base server using a lightweight Ubuntu Linux server installation. In part 2 of the tutorial, we will continue to use this machine to set up and configure the <strong>KVM </strong>and <strong>QEMU</strong> hypervisors and configure the <a href="https://libvirt.org/">libvirt</a> API to run on top. In part 3, the last part, we will create a first virtual machine and explain the process of cloning and sys-prepping the machine to be unique so it can be used to clone new virtual machines in our lab.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfb4839fc796" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/creating-a-professional-home-lab-setup-part-1-installing-the-operating-system-cfb4839fc796">Creating a Professional Home Lab Setup — Part 1: Installing the Operating System</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Employee Spotlight: Nicolas Dawans]]></title>
            <link>https://medium.com/tadaweb/employee-spotlight-nicolas-dawans-91f3e8455755?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/91f3e8455755</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Thu, 21 Dec 2023 11:41:19 GMT</pubDate>
            <atom:updated>2023-12-21T11:41:19.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vj19gBouUwtV9BYYkOsLXg.png" /></figure><p>Meet Nicolas, our Finance Manager. From auditing to financial controller, his career has seen an incredible trajectory. He has been vital in supporting the financial side of our scaling phase. Learn more about Nico here.</p><p>Nicolas (aka Nico. D) spent most of his early life abroad in desert filled landscapes before returning to Europe for university studies in Brussels. His degree in Business Engineering served as the starter for his career in finance.</p><p>After graduating, he moved to Luxembourg, where he began working in the audit industry, at a well-known Big-4 company, kicking off his career in finance. Nico’s passion for finance led him to the area of investment funds, where he gained a deep understanding of financial structures, investor reporting, consolidation processes, pipeline reviews, and controlling, working in collaboration with numerous teams spread in multiple time zones across the world! After some years, he moved into a management role, where he began to glean important insights about leading a team which he strongly cherished.</p><p>Five years later, Nico’s desire to continue learning drew him to Tadaweb, where he began working as a Financial Controller in 2021. He then evolved to the role of Finance Manager and now his role also consists of leading a small yet important team.</p><p>Nico sees finance as an essential part of the business, requiring integration and alignment with all operational teams and management. Especially as the company is developing and growing, implementing processes and structuring budgeting exercises is essential, providing insights on KPIs to other teams and leadership, to accurately track financial progress and take decisions accordingly.</p><p>He believes strongly in Tadaweb’s values, which he experiences in his daily life. For example, when he needed to prioritize family over an important meeting, Nico felt comforted by everyone’s ease of understanding that family always comes first.</p><p>Away from spreadsheets, Nico immerses himself in renovating his home with his wife, a task he relishes. He derives joy from handcrafting items (making gifts during Christmas becomes even more special!), going to concerts with loud guitars, but also spending quality time outdoors with his wife and dog, and just being caught up in the simple pleasures of life.</p><p>Kudos to our Finance Manager!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91f3e8455755" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/employee-spotlight-nicolas-dawans-91f3e8455755">Employee Spotlight: Nicolas Dawans</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mapping Our Company’s Path]]></title>
            <link>https://medium.com/tadaweb/mapping-our-companys-path-95477f8700c5?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/95477f8700c5</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Mon, 11 Dec 2023 13:53:19 GMT</pubDate>
            <atom:updated>2023-12-11T13:53:19.067Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Ehm6xBCgFJcmtW-18S-hA.png" /></figure><h4>The scaling journey is an exciting one, and at Tadaweb our COO and the operations teams are using a proof-tested model as a compass for our growth.</h4><h4>Foundation: The North Star, the Future</h4><p>Very largely inspired by the COO alliance model, we think of our growth as building a house. We start with the basics — four pillars holding up our company in the long run. These pillars are important because they’re ambitious, they will matter to us for a very long time, or a vision for the future that keeps our team excited and believing in our mission. What are these? The core purpose, our core values, a tangible 3–5-year vision, and big hairy audacious goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*bgYrY-U7YpZOfUom5Zi5iA.png" /></figure><h4>Walls: Everyday Stuff That Keeps Us Going</h4><p>In order to scale, we can’t just keep our sight on the long run, but also need daily systems (the house’s walls) to keep the engine running in a predictable way.</p><p><strong>Risk management systems </strong>— Financial processes, compliance models and all the right guidelines for everyone to know how to operate smoothly every day.</p><p><strong>Communication and information systems</strong> — Making sure everyone has the info they need when they need it. Communication is key — among leaders, within our team, and with everyone connected to what we do.</p><p><strong>People and office systems</strong> — Intentionally designing the employee experience in a way that engage our teams.</p><p><strong>Strategic planning systems</strong> — Planning goals and reviewing them in a regular cadence, to make sure the entire company is aligned on what we want to accomplish.</p><h4>Cultural Systems: Balancing Now and Later</h4><p>Right in the middle, we’ve got the culture systems. Those are a mix of short-term action sand long-term projects. We want specific traditions to be kept alive, and that requires coordinated and intentional actions. In simple terms, this model helps us understand how our long-term goals, daily operations, and adaptable culture fit into the overall scheme. Think of it as a practical roadmap, ensuring we’re not only running a business but also shaping our identity and success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95477f8700c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/mapping-our-companys-path-95477f8700c5">Mapping Our Company’s Path</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Employee Spotlight: Joel Spang]]></title>
            <link>https://medium.com/tadaweb/employee-spotlight-joel-spang-34d2aa6691ad?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/34d2aa6691ad</guid>
            <category><![CDATA[talent-acquisition]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[employee-experience]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 07:31:58 GMT</pubDate>
            <atom:updated>2023-11-09T07:31:58.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o4Fl5IUQyc9xbs4Cf_q-DQ.jpeg" /></figure><h4>Joel’s career kicked off at a thriving software company, where he found his passion for interactive solutions and nurturing talent. When he joined Tadaweb, Joel took on the challenge of balancing process implementation with preserving our unique culture. Read more about his journey at Tadaweb here.</h4><p>Joel’s journey with scale-ups began at a fast-rising software company, where he started as a front-end engineer during a crucial scaling phase. It was here that he discovered his love for building interactive solutions and nurturing talent. This marked the beginning of his career as a manager.</p><p>When Joel joined Tadaweb as an Engineering Manager, he set out to help implement processes while preserving our unique culture. He believes this phase is a balancing act: hiring the right people and fostering a high-performing team, all the while staying true to our values.</p><p>In the startup phase, the top priority was to build a product and bring value to our customers and users. Now we are shifting gears and making sure we are also providing a high level of quality (reliability, stability, performance). This shift in mindset isn’t always easy, so Joel and our other Engineering Managers thrive on a collaborative approach, where everyone feels heard and included.</p><p>One of his biggest challenges? Getting everyone on the same page. It’s about aligning on how things should be done without imposing a top-down approach. Joel emphasizes involving team members in decision-making, ensuring the process works for everyone.</p><p>What drives Joel? It’s the chance to bring fresh perspectives from the outside and share his expertise. He’s eager to offer coaching on technical and soft skills to his team, fostering growth in all aspects. In addition, values matter to him. He appreciates the flexibility that Tadaweb offers, allowing the team to balance work and life seamlessly, and cultivating an environment of trust and wellbeing.</p><p>But Joel is at least as passionate when he is not working. He’s an avid home project enthusiast, from gardening to home automation. Plus, he’s a budding baker (and we love that at Tadaweb!). Let’s not forget his passion for cubes; Joel successfully retired from his competitive speedcubing career.</p><blockquote>Fun Fact — Joel set 59 national records and solved a Rubik’s cube blindfolded in just over 5 minutes. How cool?</blockquote><p>Joel, we’re grateful for your dedication to helping us grow while staying true to our values. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34d2aa6691ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/employee-spotlight-joel-spang-34d2aa6691ad">Employee Spotlight: Joel Spang</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cultivating Well-being: Tadaweb’s Path to a Balanced Workplace]]></title>
            <link>https://medium.com/tadaweb/cultivating-well-being-tadawebs-path-to-a-balanced-workplace-f4c2fd5ab482?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4c2fd5ab482</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[wellbeing]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[worklife]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Mon, 06 Nov 2023 16:00:07 GMT</pubDate>
            <atom:updated>2023-11-06T16:00:07.319Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G8HwFOU0Dd6n83f_VuWCug.jpeg" /></figure><h4>At Tadaweb, our commitment to people is unwavering. Two years ago, we launched the Well-being Committee. With a strong focus on mental and physical health, our committee has successfully implemented initiatives to underscore their significance within our company. Read more here!</h4><p>We launched our Well-being Committee at the end of 2021. It all began thanks to some passionate individuals who care deeply about people’s welfare. Our primary focus was to continue supporting mental health and well-being while scaling.</p><p>As a small team, we were able to easily take care of each other and guarantee that everyone was feeling good. Once you have passed the start-up face, maintaining an enjoyable workplace becomes a task that needs more organization and that’s where the Wellbeing committee comes in. The Wellbeing Committee has currently multiple members from different teams and offices who ensure that the needs of various departments are listened to and considered.</p><p>Last year marked a significant milestone as the committee started introducing various initiatives, such as onsite massages, osteopath sessions, digital resources to promote mental health awareness, discussions on financial health, stretching videos across all our different locations, and more.</p><p>The committee is already gearing up for next year, focusing on further enhancing our values of inclusion, diversity, and mental and physical health. This is just the beginning of an ambitious plan to prioritize well-being at Tadaweb.</p><p>Kudos to the Well-being Committee for their accomplishments, and we eagerly await their future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4c2fd5ab482" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/cultivating-well-being-tadawebs-path-to-a-balanced-workplace-f4c2fd5ab482">Cultivating Well-being: Tadaweb’s Path to a Balanced Workplace</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Off-site 23' Edition]]></title>
            <link>https://medium.com/tadaweb/off-site-23-edition-c3eaae392758?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3eaae392758</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Thu, 26 Oct 2023 09:51:12 GMT</pubDate>
            <atom:updated>2023-10-26T09:51:12.373Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q_HoESw8YdfwyAvQJfNUqw.jpeg" /></figure><h4>Dive into an important part of the Tadaweb journey! From our strong culture to unifying team experiences, we’re sharing more about our last off-site. Read here about our commitment to growth, transparency, and fun</h4><p>From very early on at Tadaweb, our culture has remained strong and ever-present. As we started to grow, it became essential to ensure that everyone had access to the same information, promoting transparency. The annual off-site event is not just a time to spend with our colleagues; it’s also a valuable opportunity for sharing knowledge.</p><p>“Our annual team offsites are a critical pillar in building a stronger, more unified team” — <a href="https://www.linkedin.com/in/ACoAAALFLokB4E4ct232NwyxzmJwAxak2tHfLm4">Genna Elvin</a></p><p>Connecting all our locations for our company update, as we’ve done in the past, was a challenging task. After many many years of uniting our team from all around the world, our size made it no longer possible. The logistics of finding an environment for 130+ people to present their ideas, have fun, eat, sleep, and… well party was very challenging. Fortunately, thanks to the online world, we could bring everyone together simultaneously, creating a unified atmosphere.<br> <br>While we’ve been using Livestreams for some time, this year it was different. We made it possible for team members from all offices to participate. Our next challenge is to use technology to bring the Livestream to the next level, as we say, nothing is impossible.</p><p>As usual, each off-site has a unique team-building activity that was possible this year because of the support of our office managers and representatives in keeping us on track and adhering to schedules throughout the day. Charline oversaw the overall event organization, considering every detail, with Marcio’s assistance in managing branded swag and the Livestream presentation. And our speakers, who shared with us crucial information for continuing in this scaling journey.</p><p>Organizing our “Crack the code” offsite with simultaneous events at multiple locations involved meticulous planning and execution. It was a real challenge to provide a unique experience to all our offices and to create an engaging and special moment as well. At the end of the event, you are just proud to be part of such an amazing team! Let’s see how we will create memories for our next event.”- <a href="https://www.linkedin.com/in/ACoAABbpny4BOaArt1heHgjEjHTq7968IeAvjBU">Charline Jacques</a>, Executive Assistant.</p><p>We recognize the need for change and adaptation as we continue to scale, as was evident in the 2023 edition of our off-site. However, we were proud to have embraced our “hacker mentality” and found a unifying solution. We were able to continue to reinforce our culture by keeping an open communication channel, sharing knowledge despite the distance, and having fun in our respective locations. We, Tadaweb, are entrenched in our values, and that is one of the things we aim to maintain.</p><p>We look forward to seeing you next year!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3eaae392758" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/off-site-23-edition-c3eaae392758">Off-site 23&#39; Edition</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Employee Spotlight: Laurence Lambert]]></title>
            <link>https://medium.com/tadaweb/employee-spotlight-laurence-lambert-fc3de06decc6?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc3de06decc6</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Tue, 17 Oct 2023 13:26:43 GMT</pubDate>
            <atom:updated>2023-10-17T13:26:43.470Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1-wW7Kp-bsqDW12mBXKEJQ.jpeg" /></figure><h3>Employee Spotlight:Laurence Lambert</h3><h4>Meet Laurence — With diverse experience from her start as a headhunter to becoming an HR Manager, she quickly became a valued part of our family. Discover her remarkable journey with Tadaweb here.</h4><p>Please meet Laurence, our HR Manager! With a background in enterprise technology and a master’s in management, she brings to Tadaweb much-needed experience in managing talents in tech companies. Learn how Laurence is embracing the Tadaweb culture and helping us scale.</p><p>Laurence joined Tadaweb as L&amp;D Manager — but just four months in — she was offered the role of HR manager. Her ability to contribute across different aspects of the business and her passion for people and values was what we were looking for. She is now coordinating the team to ensure we attract, support, retain &amp; enable the talents inside Tadaweb.</p><p>She thrives on innovative solutions while preserving a human-centric approach, focusing on professionalism without losing sight of the people behind it. Laurence was essential to the team in this scaling phase. She successfully unified the team, clarified responsibilities, added a frame to better scale, and was ready to continue supporting this growth journey.</p><p>Regarding Tadaweb’s values, Laurence believes that every initiative we encourage must be aligned with our values and valued behaviours. They serve as a guiding light to ensure a strong company culture where the human element is never forgotten.</p><p>When Laurence is not at work, she’s a multi-talented individual. She enjoys renovating her house, a project she’s worked on for the past couple of years with her husband. Staying active is also a priority; you’ll often find her going for a run or engaging in sports during lunchtime. And, of course, spending quality time with her family and friends is an essential part of her week.</p><p>Laurence embodies the dedication and adaptability that define Tadaweb. Thank you, Laurence, for being an integral part of the Tadaweb Crew!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc3de06decc6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/employee-spotlight-laurence-lambert-fc3de06decc6">Employee Spotlight: Laurence Lambert</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building an Office Across Continents]]></title>
            <link>https://medium.com/tadaweb/building-an-office-across-continents-1306c6c20b88?source=rss-bf6e71b222f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1306c6c20b88</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[office]]></category>
            <dc:creator><![CDATA[Tadaweb]]></dc:creator>
            <pubDate>Wed, 11 Oct 2023 09:23:52 GMT</pubDate>
            <atom:updated>2023-10-11T09:23:52.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZJELH8OT8eqB0qTs_Gcarg.jpeg" /><figcaption>Wes x Jona</figcaption></figure><h4>The ultimate teamwork tale! From Luxembourg to Ottawa, follow the journey of Jona and Wes as they turned challenges into scaling milestones.</h4><p>Building an office from afar with a six-hour time difference was challenging for our colleagues, Jona and Wes. Not long ago, it wasn’t unusual to find them wrestling with wires on the floor or fiddling with equipment on the ceiling to make our offices functional. Covering everything from plumbing to electrical work was equally impressive and needed.</p><p>As we moved into the scaling phase, their approach had to evolve. In the early stages of a startup, you aim to handle as much as possible in-house. However, as our company expanded, the focus shifted towards careful planning and coordination.</p><p>Setting up our Canadian office was the prime example of executing at scale. The initial step involved partnering with external experts who not only possessed the necessary skills for the setup but also shared our vision and commitment to building an actual Tada-like office. Jona and Wes collaborated closely with a project manager, a designer, and an infrastructure company based in Ottawa.</p><p>Trust and teamwork were vital. Jona and his team prepared the equipment and set it up like they were in Ottawa. They also had remote meetings with the external company to ensure that all the pieces came together seamlessly. After a few months of preparation, our Canadian office was ready for our team.</p><p>Wes embarked on a final trip to Ottawa to attend to last-minute details, foster a sense of belonging, and put the final touches of the Tadaweb culture in place. It was a challenging journey, but in true Tadaweb spirit, Wes and Jona bridged the geographical gap to construct an office extending all the way from Luxembourg to Ottawa. Nothing is impossible!</p><p>We want to thank our Canadian team for their patience and hard work during this project. They’ve been right there, supporting Jona and Wes from a distance every step of the way. Their commitment to making this Canadian office a reality has been crucial. Also, thanks to Wes and Jona for helping us scale the Tadaweb way!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1306c6c20b88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tadaweb/building-an-office-across-continents-1306c6c20b88">Building an Office Across Continents</a> was originally published in <a href="https://medium.com/tadaweb">Tadaweb</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>