Installation (KVM) - Revision history

Sstrutt: /* Networking */ Added Ubuntu 18 instructions

2020-04-10T18:27:20Z

Networking: Added Ubuntu 18 instructions

← Older revision		Revision as of 18:27, 10 April 2020
Line 21:		Line 21:

	== Networking ==		== Networking ==
			By default, you'll end up with a new <code>virbr0</code> interface, on which all virtual machines will be deployed to. These will not be accessible to the outside world, which is sometimes fine for a private lab environment, but otherwise fairly useless. In order to all your VMs to be accessible, you need to create a new bridge interface, and move your server's IP address onto that. Once done, VMs can also be provisioned onto the same interface, and will be as accessible as your KVM server.

			=== Ubuntu 18.04 ===
			Network config is achieved via Netplan, for an existing config such as show...
			<pre>
			root@kvm-svr:~# cat /etc/netplan/50-cloud-init.yaml.orig
			# This file is generated from information provided by the datasource. Changes
			# to it will not persist across an instance reboot. To disable cloud-init's
			# network configuration capabilities, write a file
			# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
			# network: {config: disabled}
			network:
			ethernets:
			eno1:
			addresses:
			- 192.168.1.50/24
			gateway4: 192.168.10.1
			nameservers:
			addresses:
			- 192.168.1.1
			- 8.8.8.8
			- 8.8.4.4
			search:
			- vwiki.co.uk
			version: 2
			</pre>

			...add a new bridge network and move most of the config over...
			<pre>
			root@media-svr:~# cat /etc/netplan/50-cloud-init.yaml
			# This file is generated from information provided by the datasource. Changes
			# to it will not persist across an instance reboot. To disable cloud-init's
			# network configuration capabilities, write a file
			# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
			# network: {config: disabled}
			network:
			version: 2
			ethernets:
			eno1:
			dhcp4: no
			dhcp6: no
			bridges:
			br0:
			interfaces:
			- eno1
			dhcp4: no
			addresses:
			- 192.168.1.50/24
			gateway4: 192.168.1.1
			nameservers:
			addresses:
			- 192.168.1.1
			- 8.8.8.8
			- 8.8.4.4
			search:
			- vwiki.co.uk
			</pre>

			...and apply using...
			netplan apply

	== Configuration ==		== Configuration ==

Sstrutt: /* Installation */ Updated

2020-04-10T18:09:09Z

Installation: Updated

← Older revision		Revision as of 18:09, 10 April 2020
Line 16:		Line 16:
	Install using the following command		Install using the following command
	apt install qemu qemu-kvm libvirt-bin bridge-utils virt-manager		apt install qemu qemu-kvm libvirt-bin bridge-utils virt-manager

			Once completed, ensure libvirtd is running
			systemctl status libvirtd

	== Networking ==		== Networking ==

Sstrutt: /* Installation */ Updated

2020-04-10T18:06:24Z

Installation: Updated

← Older revision		Revision as of 18:06, 10 April 2020
Line 15:		Line 15:
	== Installation ==		== Installation ==
	Install using the following command		Install using the following command
	apt~~-get~~ install qemu-kvm libvirt-bin ~~virtinst~~ bridge-utils ~~cpu~~-~~checker~~		apt install qemu qemu-kvm libvirt-bin bridge-utils virt-manager

	== Networking ==		== Networking ==

Sstrutt: /* Prerequisites */ Updated

2020-04-10T18:05:30Z

Prerequisites: Updated

← Older revision		Revision as of 18:05, 10 April 2020
Line 2:		Line 2:
	This guide assumes you have a working Ubuntu Server with one physical NIC that will used for networking to the host server, and also for a bridged network for guest virtual machines.		This guide assumes you have a working Ubuntu Server with one physical NIC that will used for networking to the host server, and also for a bridged network for guest virtual machines.

	Ensure your server has CPU's that support hardware virtualisation, you should get one output of flags per CPU (which will include either <code>svm</code> or <code>vmx</code>)		Ensure your server has CPU's that support hardware virtualisation, you should get one output of flags per CPU (which will include either <code>svm</code> or <code>vmx</code>). If you don't, reboot the server into BIOS and see if there is an option to enable CPU Virtualisation features or VT, if you don't your hardware may too old to support virtualisation. If your hardware is recent, it should, so consult your vendors documentation (either for the server, or for the server's motherboard).
	egrep '(vmx\|svm)' /proc/cpuinfo		egrep '(vmx\|svm)' /proc/cpuinfo


			Ensure your server can run KVM hardware acceleration. Install <code>cpu-checker</code> and run as follows...
			apt install cpu-checker
			kvm-ok
			...which should return...
			INFO: /dev/kvm exists
			KVM acceleration can be used

	== Installation ==		== Installation ==

Sstrutt: Added Allow VNC Console Access

2018-02-17T22:21:52Z

Added Allow VNC Console Access

← Older revision		Revision as of 22:21, 17 February 2018
Line 11:		Line 11:
	== Networking ==		== Networking ==

			== Configuration ==
			=== Allow VNC Console Access ===
			By default virtual machine consoles are bound to 127.0.0.1 on the host KVM server. So you can't connect from a remote machine using VNC to see the VM's console (unless you tunnel through SSH). Bind to 0.0.0.0 to make remote console access. Note that the VM configuration also needs to be changed to listen on 0.0.0.0.

			# Edit <code>/etc/libvirt/qemu.conf </code> and uncomment the following line
			#* <code> vnc_listen = "0.0.0.0" </code>
			# Restart libvirtd
			#* <code>service libvirtd restart</code>

	[[Category:KVM]]		[[Category:KVM]]
	[[Category:Ubuntu]]		[[Category:Ubuntu]]

Sstrutt: WIP

2018-02-14T09:28:53Z

WIP

New page

== Prerequisites ==
This guide assumes you have a working Ubuntu Server with one physical NIC that will used for networking to the host server, and also for a bridged network for guest virtual machines.

Ensure your server has CPU's that support hardware virtualisation, you should get one output of flags per CPU (which will include either <code>svm</code> or <code>vmx</code>)
egrep '(vmx|svm)' /proc/cpuinfo

== Installation ==
Install using the following command
apt-get install qemu-kvm libvirt-bin virtinst bridge-utils cpu-checker

== Networking ==

[[Category:KVM]]
[[Category:Ubuntu]]