Turns out booting virtual machines from scratch using the KVM hypervisor with the virtualization manager Libvirt has some gotchas! We'll dispel any of that with this guide. We'll also show you how to expose your virtual machine to the public internet with an elastic IP.
All of Packet's hardware can be virtualized but for this guide, we'll be deploying a Tiny But Mighty server with Ubuntu 16.04 installed.
Note: This installation is completed entirely using the command line (no GUI!). Also, you will need a public /30 IPv4 block assigned to your account if you plan to route public traffic to your virtual machine. You can request the IP block from the portal, more info here.
Step 1: Install Virtualization Software
Once you're SSH'd into your server as root you'll need to install several packages to create and properly manage virtual machines.
- qemu-kvm: the hypervisor and emulator.
- virtinst: a suite of command line tools for installing and managing virtual machines with the operating system of your choosing.
- bridge-utils: used to create and manage bridge networks.
Good idea to do this...
apt-get update && apt-get upgrade -y
Then install the packages...
apt-get install bridge-utils qemu-kvm virtinst -y
Once you're done you can verify the install is successful by running
Restart your server so that the needed kvm and libvirt deamons come up.
Step 2: Configure the Network
When configuring the network for your virtual machines you can choose to run in NAT mode or in Route mode.
In NAT mode, each virtual machine gets a private IP and communicates with the public internet via the host's public IP.
In Route mode, each virtual machine gets their own public IP.
With either configuration, you'll need to create a bridge network - more about creating bridge networks here. In this guide, libvirt-bin is taking care of the bridge configuration and also the IP assignments using an XML configuration we provide. You can learn more about libvirt-bin networking here.
By default, libvirt comes with a preconfigured NATed network. It will usually assign 192.168.x.x IPs to the virtual machines you create. But we're not doing that here! We want our virtual machines to have their own public IPs so we will define our own network in an XML file.
Note: If you don't already have a public /30 IPv4 block assigned to your project, you'll need to request it from the portal; more here.
Go ahead and assign all the IPs to the server that you're on.
We'll be using the net-define command to configure the virtual machine.
The configuration needs to be in XML; for this example, we're creating a .xml file called network.xml in our root directory. The order in which we add our IPs matters! So have a look at the screenshot above to see which IP goes where in the configuration.
echo ' <network> <name>vmbr0</name> <forward mode="route"/> <bridge name="vmbr0" stp="on" delay="0"/> <ip address="220.127.116.11" netmask="255.255.255.252"> <dhcp> <range start="18.104.22.168" end="22.214.171.124"/> </dhcp> </ip> </network>' >> network.xml # These 2 commands will define and create our new network virsh net-define /root/network.xml virsh net-autostart vmbr0 # These 2 commands will delete the default private network virsh net-destroy default virsh net-undefine default
Lastly, restart the libvirt-bin daemon.
Now if you look at your interfaces you'll see a new interface named vmbr0 with our 126.96.36.199 IP.
Don't forget to enable IPv4 packet forwarding!
sed -i "/net.ipv4.ip_forward=1/ s/# *//" /etc/sysctl.conf
Step 3: Install a Virtual Guest Machine
To install a virtual machine we'll run virt-install.
virt-install --name ubuntu16 \ --ram 4096 \ --disk path=/var/lib/libvirt/images/ubuntu16.img,size=8 \ --vcpus 2 \ --os-type linux \ --os-variant ubuntu16.04 \ --network bridge=vmbr0 \ --graphics none \ --console pty,target_type=serial \ --location 'http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/installer-amd64/' \ --extra-args 'console=ttyS0,115200n8 serial'
The Ubuntu installer will hijack your console at some point soon after running the command and guide you through the rest of the install. The important part comes up during the end of the install where you'll be prompted with this
[!] Software selection At the moment, only the core of the system is installed. To tune the system to your needs, you can choose to install one or more of the following predefined collections of software. Choose software to install: [ ] Manual package selection [ ] Ubuntu Cloud Image (instance) [ ] DNS server [ ] Edubuntu desktop [ ] Kubuntu desktop [ ] Kubuntu full [ ] LAMP server [ ] Lubuntu minimal installation [ ] Lubuntu Desktop
Very important that you scroll all the way down using your arrow keys and select "OpenSSH Server" using the space bar before continuing. That's how we'll access the VM once it's up.
Step 5: Access Your VM
To access your VM you can SSH into it from the host machine.
But where is the IP address!?!?
Easy, first get the virtual machine's MAC address:
Next, find the IP address:
virsh domiflist ubuntu16
And of course:
arp -an | grep "the MAC address"
There you have it, KVM and Libvirt demystified! If you have any suggestions about this guide please leave a comment below.