Update install-qemu-kvm.md

boxcutter · Feb 10, 2024 · 0fd3342 · 0fd3342
1 parent 4f0bbb7
commit 0fd3342
Showing 1 changed file with 0 additions and 108 deletions.
diff --git a/docs/install-qemu-kvm.md b/docs/install-qemu-kvm.md
@@ -70,111 +70,3 @@ sudo apt-get install ovmf
 # Files are in /usr/share/AAVMF
 sudo apt-get install qemu-efi-aarch64
 ```
-
-## Configure bridged networking
-
-All the networking options for kvm are just different configurations for a virtual networking
-switch, also known as a bridge network interface.
-
-The default network created when libvirt is used is called `default` and uses NAT. It normally
-is configured to use a bridge network interface called `virbr0`. When a virtual machine is
-on a NAT network, it is on a separate subnet that prevents outside access to the VM directly,
-nwhile the VM itself can access any network the host can access.
-
-With bridged networking, the VM will be on the same network as the host. It can be accessed
-by all computers on your host network as if it were another computer directly connected to
-the same network.
-
-### Determine how the networking is configured on Ubuntu
-
-Ubuntu has multiple methods for persisting network configurations, so first you need to
-determine how the networking on your machine is configured.
-
-On Ubuntu, determine if the host interface is managed by `systemd-networkd` or `NetworkManager`.
-Usually if you are using Ubuntu Desktop, it's `NetworkManager`, and if you are using
-Ubuntu Server, it's `systemd-networkd`, but it can vary.
-
-Running `networkctl` will tell you is `systemd-networkd` is running and if an interface
-is being managed. The default configuration on Ubuntu Desktop should show that
-`systemd-networkd` is not running and the interfaces are not being managed (by `systemd-networkd`).
-
-```
-$ networkctl
-WARNING: systemd-networkd is not running, output will be incomplete.
-
-IDX LINK      TYPE     OPERATIONAL SETUP    
-  1 lo        loopback n/a         unmanaged
-  2 eno1      ether    n/a         unmanaged
-  3 wlp0s20f3 wlan     n/a         unmanaged
-  4 virbr0    bridge   n/a         unmanaged
-  5 docker0   bridge   n/a         unmanaged
-
-5 links listed.
-```
-
-By comparison, if `systemd-networkd` is running and interfaces are being managed, the
-output of `networkctl` looks more like this:
-
-```
-$ networkctl
-IDX LINK  TYPE     OPERATIONAL SETUP
-  1 lo    loopback carrier     unmanaged
-  2 ens33 ether    routable    configured
-
-2 links listed.
-```
-
-You can check to see if NetworkManager is being used by using `nmcli`. If the network
-interfaces are being managed by NetworkManager, the output will look something like
-this:
-
-```
-$ nmcli general
-STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
-connected  full          enabled  enabled  enabled  enabled
-
-$ nmcli connection
-NAME                UUID                                  TYPE      DEVICE  
-Wired connection 1  5297a82f-7244-31f3-9dad-c3fb49be0b33  ethernet  eno1    
-docker0             80651a82-b1af-4ed7-a4bb-e0a802d6f012  bridge    docker0 
-virbr0              d0da1989-df49-44dc-9c48-aa3c978fbb90  bridge    virbr0
-```
-
-But you're not done yet, you also need to check if netplan is being used to render
-configurations in `systemd-networkd` or `NetworkManager`. In Ubuntu 24.04, there will
-be a command called `netplan status` to check this. As of this writing, you are unlikely
-to be using this, so instead the best way to check is to see if there are configuration
-files in `/etc/netplan`. If `netplan` is being used on your system, it's probably
-easiest to add the configuration for the bridge configuration through netplan.
-
-Here's an example of a `systemd-networkd` configuration managed by `netplan`. It may
-or may not include a `renderer` stanza that says `renderer: networkd`, because it is
-the default:
-
-```
-$ ls /etc/netplan
-00-installer-config.yaml
-$ cat /etc/netplan/00-installer-config.yaml
-# This is the network config written by 'subiquity'
-network:
-  ethernets:
-    ens33:
-      dhcp4: true
-  version: 2
-```
-
-On the other hand, if a `NetworkManager` configuration is being managed by `netplan`,
-it will include a `renderer` stanza that says `renderer: NetworkManager`. It's not
-unusual for there to be any configuration in the netplan file, because currently,
-NetworkManager isn't very well integrated into netplan on Ubuntu. You can't use
-`netplan try` to experiment with new configurations, for example.
-
-```
-$ ls /etc/netplan/
-01-network-manager-all.yaml
-$ cat /etc/netplan/01-network-manager-all.yaml 
-# Let NetworkManager manage all devices on this system
-network:
-  version: 2
-  renderer: NetworkManager
-```