KVM - Revision history

Merenber at 15:11, 7 August 2021

2021-08-07T15:11:16Z

← Older revision		Revision as of 10:11, 7 August 2021
Line 92:		Line 92:
	<br><br>		<br><br>
	Now, restart the VM.		Now, restart the VM.
			<br><br>
			References:
			* https://libvirt.org/firewall.html
			* https://libvirt.org/formatnwfilter.html#nwfconceptsvars
			* https://libvirt.org/formatdomain.html#network-interfaces

Merenber at 15:09, 7 August 2021

2021-08-07T15:09:02Z

← Older revision		Revision as of 10:09, 7 August 2021
Line 90:		Line 90:
	</pre>		</pre>
	Replace the IP and IPV6 values with the desired IPv4 and IPV6 addresses of the VM, respectively. Now, if someone inside the VM tries to change their IP or MAC address, the ebtables and iptables rules on the host will reject their packets.		Replace the IP and IPV6 values with the desired IPv4 and IPV6 addresses of the VM, respectively. Now, if someone inside the VM tries to change their IP or MAC address, the ebtables and iptables rules on the host will reject their packets.
			<br><br>
			Now, restart the VM.

Merenber at 15:03, 7 August 2021

2021-08-07T15:03:36Z

@@ Line 35: / Line 35: @@
 == Post-creation ==
 Make sure you run through the steps outlined in [[New CSC Machine]]. After you do that, you should be able to ditch the virsh console and SSH in from anywhere.
-<br>
+<br><br>
 Optional, but recommended: if the VM will be used by potentially untrusted people, it is a good idea to apply [https://libvirt.org/firewall.html libvirt firewall rules] to the VM to prevent IP/MAC/ARP spoofing.

Merenber: Created page with "Here are some recommendations for creating new virtual machines (VMs). == Prerequisites == Working with libvirt is much easier than working with the raw QEMU commands, so mak..."

2021-08-07T14:51:45Z

Created page with "Here are some recommendations for creating new virtual machines (VMs). == Prerequisites == Working with libvirt is much easier than working with the raw QEMU commands, so mak..."

New page

Here are some recommendations for creating new virtual machines (VMs).

== Prerequisites ==
Working with libvirt is much easier than working with the raw QEMU commands, so make sure to have it installed:
<pre>
apt install qemu-system libvirt-clients libvirt-daemon-system virtinst
</pre>

== VM Creation ==
Let's say we want to create a new VM for progcom. First, create a new volume for it:
<pre>
lvcreate -L 40G vg0 --name progcom
</pre>
Next, run virt-install:
<pre>
virt-install \
--connect qemu:///system \
--name progcom \
--virt-type kvm \
--memory 8192 \
--vcpus 4 \
--cpu host \
--disk path=/dev/vg0/progcom,format=raw,bus=virtio \
--network bridge=br0,model=virtio \
--graphics none \
--video virtio \
--serial pty \
--extra-args 'console=ttyS0,115200n8' \
--os-type linux \
--os-variant debian10 \
--location http://mirror.csclub.uwaterloo.ca/debian/dists/stable/main/installer-amd64
</pre>
This will start the Debian installer on your console. It should be possible to automate the installation using [https://www.debian.org/releases/stable/i386/apbs02.en.html preseeding].

== Post-creation ==
Make sure you run through the steps outlined in [[New CSC Machine]]. After you do that, you should be able to ditch the virsh console and SSH in from anywhere.
<br>
Optional, but recommended: if the VM will be used by potentially untrusted people, it is a good idea to apply [https://libvirt.org/firewall.html libvirt firewall rules] to the VM to prevent IP/MAC/ARP spoofing.