If a QEMU front-end is to be used (other than of libvirt and virsh), disregard the rest of this wiki page and consult the specific QEMU front-ends for the desire network configuration.
If other virtualization software exists (other than QEMU/libvirt), then co-existance of multiple virtualization management is outside the scope of this article.
If the host OS is not a Gentoo OS, consult the corresponding OS guide on network installation and replace the following Gentoo Ethernet device names throughout the document with that OS's device name nomenclature.
- virbr0 netdev - virtual bridge with NAT
- enp3s0 netdev - slave to virbr0 - WAN-side
And optionally have the following netdevs/IP-links:
- enp4s0 netdev - DMZ-side (optional)
- enp5s0 netdev - Internal LAN-side (optional)
- virbr1 netdev - closed network
Ensure that any existing firewall setup does not already use the chain name nat, for libvirt already owns nat chain name.
Check that the libvirt package is installed, the libvirtd service is started and get a positive response from the libvirtd daemon:
<sysinfo type='smbios'> <bios> <entry name='vendor'>Dell Inc.</entry> <entry name='version'>A22</entry> <entry name='date'>11/29/2018</entry> <entry name='release'>4.6</entry> </bios> <system> <entry name='manufacturer'>Dell Inc.</entry> <entry name='product'>OptiPlex 3010</entry> <entry name='version'>01</entry> <entry name='serial'>JRJ0SW1</entry> <entry name='uuid'>4c4c4544-0052-4a10-8030-cac04f535731</entry> <entry name='sku'>OptiPlex 3010</entry> <entry name='family'>Not Specified</entry> </system> <baseBoard> <entry name='manufacturer'>Dell Inc.</entry> <entry name='product'>042P49</entry> <entry name='version'>A00</entry> <entry name='serial'>/JRJ0SW1/CN701632BD05R5/</entry> <entry name='asset'>Not Specified</entry> <entry name='location'>Not Specified</entry> </baseBoard> <chassis> <entry name='manufacturer'>Dell Inc.</entry> <entry name='version'>Not Specified</entry> <entry name='serial'>JRJ0SW1</entry> <entry name='asset'>Not Specified</entry> <entry name='sku'>To be filled by O.E.M.</entry> </chassis> <processor> <entry name='socket_destination'>CPU 1</entry> <entry name='type'>Central Processor</entry> <entry name='family'>Core i5</entry> <entry name='manufacturer'>Intel(R) Corporation</entry> <entry name='signature'>Type 0, Family 6, Model 58, Stepping 9</entry> <entry name='version'>Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz</entry> <entry name='external_clock'>100 MHz</entry> <entry name='max_speed'>3200 MHz</entry> <entry name='status'>Populated, Enabled</entry> <entry name='serial_number'>Not Specified</entry> <entry name='part_number'>Fill By OEM</entry> </processor> <memory_device> <entry name='size'>8 GB</entry> <entry name='form_factor'>DIMM</entry> <entry name='locator'>DIMM1</entry> <entry name='bank_locator'>Not Specified</entry> <entry name='type'>DDR3</entry> <entry name='type_detail'>Synchronous</entry> <entry name='speed'>1600 MT/s</entry> <entry name='manufacturer'>8C26</entry> <entry name='serial_number'>00000000</entry> <entry name='part_number'>TIMETEC-UD3-1600</entry> </memory_device> <memory_device> <entry name='size'>8 GB</entry> <entry name='form_factor'>DIMM</entry> <entry name='locator'>DIMM2</entry> <entry name='bank_locator'>Not Specified</entry> <entry name='type'>DDR3</entry> <entry name='type_detail'>Synchronous</entry> <entry name='speed'>1600 MT/s</entry> <entry name='manufacturer'>8C26</entry> <entry name='serial_number'>00000000</entry> <entry name='part_number'>TIMETEC-UD3-1600</entry> </memory_device> <oemStrings> <entry>Dell System</entry> <entry>1</entry> <entry>3[1.0] </entry> <entry>12[www.dell.com] </entry> <entry>14</entry> <entry>15</entry> </oemStrings> </sysinfo>
If it hang or has no output, then start the libvirtd daemon:
For OpenRC initd
rc-service libvirtd start
- Before version 243-rc1, use:
systemctl start libvirtd
- After version 243-rc1, the new modular architecture for systemd has been introduced; we use the virtnetworkd unit service instead:
systemctl start virtnetworkd
Network management controller
Most importantly, one has to decide which network controller will be responsible for the online state of IP interfaces, including as a host OS for the guest containers and QEMU-based virtual machines.
The choices of host-side network management (along with its configuration file path) are:
- libvirtd, /etc/libvirt/qemu/networks/default.xml
- OpenRC, /etc/conf.d/net
- systemd-networking, /etc/systemd/network
The libvirtd is the recommended network controller for VMs/containers. libvirtd comes with DHCP server as a default (and that is optional too).
The rest of this article focus only on openly libvirtd-managed networking for VMs/containers; however route tables, firewall and/or /sys/net/ipv4[/<netdev>]/ip_forward must be updated for additional network security.
There are three camps of current network setups:
- default network connection is provided by libvirt at install time.
- No IP interface nor bridge defined; fresh OS install
- multiple IP netdevs/links already configured.
1. Default network connection
Check the libvirtd for any existing network connections; a fresh install of app-emulation/libvirt should leave at least a default network:
Name State Autostart Persistent ---------------------------------------------- default active yes yes
default network is only used by libvirt-managed virtual machines and containers.
2. Existing network - simple
If a default network connection exist, skip this section and go on to "Multiple IP Links Configured" section.
If this is an existing setup is Gentoo Handbook-guided, but its default network became missing sometime after a sys-emulation/libvirt installation, that means the app-emulation/libvirt may not have been installed correctly or that default network may have been deleted.
To recreate and restore the default network using libvirt default settings, execute:
cp -i /usr/share/libvirt/networks/default.xml /etc/libvirt/qemu/networks/default.xml
Inform the libvirtd of the new default network settings:
virsh net-define /usr/share/libvirt/networks/default.xml
Network test defined from /usr/share/libvirt/networks/default.xml
To change the IP address, IP subnet, gateway, and/or DHCP IP range on this host for the VMs/containers, execute:
virsh net-edit default
then save the network XML file.
Test the default network by asking the libvirtd daemon to see this new default network, that will only be used by virtual machines and containers:
virsh net-list --all
Name State Autostart Persistent ---------------------------------------------- default inactive no yes
Enable the default network so that it starts during boot-up time:
virsh net-autostart default
Network test marked as autostarted
Start the default network:
virsh net-start default
Network default started
Assuming that you do not have prior virtualization support being installed on your host, the bare minimum criteria to hosting VMs/containers is to provide a virtual bridge (or MACVLAN). Such virtual bridge may or may not have NAT, and may or may not have a physical Ethernet port-slaved to its bridge.
If an existing bridge exists, is properly configured, and is a suitable candidate for hosting all the guest VM/containers, then replace throughout this documentation page the virbr0 notation with that bridge device name.
If no bridge is available for hosting the guest, then one Ethernet netdev (802.3/USB/Wireless/tunnel) must be available and not a slave to any other bridges; then go back to step 1 above.
Else if non-slave Ethernet interface is not available, then add another Ethernet NIC card or replan your host network configuration.
- Virtualization — the concept and technique that permits running software in an environment separate from a computer operating system.
- QEMU — a generic, open source hardware emulator and virtualization suite.
- QEMU/QEMU front-ends — user interface application to the QEMU/libvirt API/library.
- Libvirt — a virtualization management toolkit.
- Libvirt/QEMU_guest — covers libvirt and its creation of a virtual machine (VM) for use under the soft-emulation mode QEMU hypervisor Type-2, notably using virsh command.
- Virt-manager — desktop user interface for management of virtual machines and containers through the libvirt library
- Virt-manager/QEMU_guest — QEMU creation of a guest (VM or container)