Differences

This shows you the differences between two versions of the page.

--- unix:virtualization:kvm:server [2020/10/31 21:05] – rodolico
+++ unix:virtualization:kvm:server [2022/05/19 02:13] – rodolico
@@ Line 17: / Line 17: @@
 You should see either vmx or svm in the output.
-Now, install the basic packages needed, a couple of utilities, but not all the extra crud.
+Now, install the basic packages needed, a couple of utilities, but not all the extra crud. //netcat-openbsd// is only needed if you're going to cluster and migrate virtuals from one hypervisor to another, from what I can tell. **virt-top** is a nice little //top// for seeing what is running and what resources they are using in real time.
 <code bash>
-apt install -y --no-install-recommends qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils libguestfs-tools genisoimage virtinst libosinfo-bin virt-top
+apt install -y --no-install-recommends qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils libguestfs-tools genisoimage virtinst libosinfo-bin virt-top netcat-openbsd
 reboot # brings libraries online
 </code>
@@ Line 174: / Line 174: @@
 I'm lazy, so I just created all three, then imported them all at one time.
-<code xml br_wan.xml>
+<code bash import_bridge.sh>
-<network>
+#! /usr/bin/env bash
-  <name>br_wan</name>
-  <forward mode="bridge"/>
-  <bridge name="br_wan"/>
-</network>
-</code>
-<code xml br_dmz.xml>
+# create the xml definitions. The br is prepended.
-<network>
+# Add/remove interfaces if needed
-  <name>br_dmz</name>
+for interface in wan lan dmz
-  <forward mode="bridge"/>
+do
-  <bridge name="br_dmz"/>
+cat << EOF > br_$interface.xml
-</network>
+       <network>
-</code>
+         <name>br_$interface</name>
+         <forward mode="bridge"/>
+         <bridge name="br_$interface"/>
+       </network>
+EOF
+done
+# uncomment this if you want to view your xml files but
+# not process them
+# exit
-<code xml br_lan.xml>
-<network>
-  <name>br_lan</name>
-  <forward mode="bridge"/>
-  <bridge name="br_lan"/>
-</network>
-</code>
-And imported them all at once.
+# find all xml files and do the net-define
+for interface in `ls *.xml`
+do
+   virsh net-define --file $interface
+done
-<code bash>
+# since the bridge name is followed by xml, simply remove that
-for interface in `ls *.xml` ; do virsh net-define --file $interface ; done
+# and set to autostart and start it
-for interface in `ls *.xml | cut -d'.' -f1` ; do virsh net-autostart $interface ; virsh net-start $interface ; done
+for interface in `ls *.xml | cut -d'.' -f1`
+do
+   virsh net-autostart $interface
+   virsh net-start $interface
+done
+# show me the list of network names
 virsh net-list
 </code>
-After the last command, you should see your three interfaces defined. That means you can now use them.
+This script assumes your network names are of the form br_//something// and it creates the file name as br_//something//.xml. It then looks for all XML files (so, you don't want any others in the current directory), the processes them.
+The last loop assumes there are no periods in the network name. Be warned.
 ===== Using Storage =====