The documentation recommends you do this using virsh net update, but you'll need to read it very carefully to figure out exactly how -- because they provide you with only a
single example to work with.
Only the following virtual network components can be changed using net-update:
ip-dhcp-host
ip-dhcp-range (add/delete only, no modify)
forward-interface (add/delete only)
Tested on a Ubiquiti EdgeRouter 4 with dnsmasq enabled for DHCP (and DNS) serving.
These operations can also be carried out in the EdgeRouter web gui with the "DNS host names" Wizard (click the "Wizards" tab and then select "DNS host names" to access).
To see all currently statically mapped hosts:
$ cat /etc/hosts
NOTE: If you find yourself getting thinking you may have gotten way too far down into the weeds with this, you might want to consider a much less involved alternative: bash-git-prompt (that's what I'm now using on all my Linux machines).
To be clear, this gist will focus on Powerline for the Gnome terminal on Linux and for PowerShell Core on Windows 10, because those are the combinations I use in my daily work.
There are two different open source products that make it easier to implement Powerline for bash and PowerShell:
Oh My Bash for bash on
As an equal-opportunity employer, my notes on completely removing flatpak (may God have mercy on my soul):
Before starting, be sure to inventory what's installed:
$ flatpak list
Then run the following commands to remove all flatpaks and the flatpak service:
Launching gui apps on Linux remotely can be easy as
$ ssh -X test1.example.com
Back in the bad old days of Unix when X Windows was first being developed, it was decided that having the ability to remote into a machine and launch graphical apps was a good idea. All versions of X11 have retained this capability to one degree or another, but it's one of the features dropped by the Wayland project.
Ubuntu is a particularly difficult distro to work with virt-install for a lot of reasons, not the least of which is that it departs from its Debian base in many key respects: starting with disk images. What's more, those departures are mostly undocumented. Debian and CentOS are a lot easier. Given IBM's recent actions with regard to CentOS, I think Debian is the best choice going forward.
Main source for how to do this was:
How to install KVM on Ubuntu 20.04 LTS Headless Server
Two files, ubuntu.env for the environment variables, and inst-ubuntu.sh to run the commands.
This turned out to be easier than I thought it would, especially after struggling with Ubuntu.
Both procedures use a common debian.env file to hold environment variables applied in the script.
When installing Debian always be sure to select an apt mirror when prompted, if you don't you'll regret it.
In a file, debian.env:
The assumption here is that you're starting with a Ubuntu 20.04 LTS Server or newer, rather than Desktop, base (Ubuntu Desktop deploys NetworkManager rather than systemd-networkd by default). This box has an AMD Ryzen CPU.
The goal is networking configured for static addressing using using ifupdown, rather than the newer systemd-networkd and netplan, or (for Ubuntu Desktop) NetworkManager. It basically returns networking on Ubuntu to its Debian roots.
The physical network device name for the test machine was "ens3", it will be something else on different hardware.
NOTE: I am currently using netplan rather than ifupdown on my own Ubuntu servers. I'll keep these notes updated because the configuration is close enough to Debian that it may come in handy when I finally switch to Debian.