virtception –
We took Gnome Boxes for a quick spin — it has promise but needs more work.
: 406 am UTC
Yes, you can just install Gnome Boxes from Software Center — but I’m a sysadmin at heart; I used apt instead. Jim Salter I really like the Welcome Tutorial that Boxes gives you. It’s short, to the point, and exposes features you’d likely miss otherwise. Jim Salter The easy downloads is a pretty nifty feature — you don’t need to hunt down install ISOs; Boxes already knows where they are and will fetch them for you. Jim Salter The drag-and-drop functionality works as advertised — with a Linux guest and a Gnome3 desktop, anyway. Jim Salter
Gnome Boxes
- Yes, you can just install Gnome Boxes from Software Center — but I’m a sysadmin at heart; I used apt instead. Jim Salter I really like the Welcome Tutorial that Boxes gives you. It’s short, to the point, and exposes features you’d likely miss otherwise. Jim Salter The easy downloads is a pretty nifty feature — you don’t need to hunt down install ISOs; Boxes already knows where they are and will fetch them for you. Jim Salter The drag-and-drop functionality works as advertised — with a Linux guest and a Gnome3 desktop, anyway. Jim Salter
Gnome Boxes
-
Clicking the plus sign begins the fun — time to install a new VM in Boxes. Jim Salter -
I have to admit, the searchable distribution screen was cool. As I typed “open,” the list automatically populated with matching known distros. Jim Salter
- We immediately hit problems in our OpenBSD VM, still in the installer. For example, there’s awful keybounce — a problem I haven’t seen since TRS – s! Jim Salter
The OpenBSD install wouldn’t complete at all under Boxes — but under virt-manager, as seen here, it “just worked” without so much as a hiccup. Jim Salter Although I led with a good experience above, the Ubuntu Focal guest wasn’t actually the first thing I tried. Boxes specifically aims to give inexperienced users “a very safe and easy way to try out new operating systems” —so that’s just what I did, shooting for the moon with an OpenBSD install attempt on my first try.
Searching for OpenBSD under the Create VM dialog went extremely well — as I typed “open” into the search box, it dynamically populated the list of known distros with matching results. I skipped down past OpenSUSE and went directly to OpenBSD, which I’d never run before. This seemed to go well at first — it downloaded the ISO quickly, and jumped right into an installation — but the installation itself had severe problems, and I never got a working guest out of it. OpenBSD’s installer is quite primitive and could not cope with some of the choices Boxes had made for its environment. It could not successfully find its own files on the virtual CD it had booted from, it did quite understand the network stack (interpreting its IP address as static rather than DHCP), and it had incredibly bad keybounce
. (If you had to click that link to figure out what keybounce is, I don’t blame you.) By contrast, OpenBSD installed without a hitch under virt-manager. Although I did need to download an OpenBSD 6.6 ISO manually and point virt-manager to it — and select the number of vCPUs as well as how much RAM and disk space to allocate — the actual install there went flawlessly. In less than five minutes total, virt-manager delivered a working OpenBSD guest without so much as a hiccup. Brittle installation environment aside, Boxes will probably frustrate fellow KVM veterans immensely. Guests running under Boxes can’t be managed or inspected with the usual libvirt-related commands — you won’t see a running Boxes guest under virt-top , (virsh list) , or similar tools. The papercuts continue I appreciate how easy it is to pass USB devices down into a Boxes guest. Jim Salter that places the cursor over the Memory or Disk Size sliders … at which point it’s suddenly moving that slider. Yikes! Jim Salter OpenBSD problems aside, Boxes was pretty painful even with better-supported guests. It automatically hibernated my Ubuntu Focal Fossa VM when I closed the main Boxes window — and when I tried to open Boxes again, the entire application timed out waiting for the Fossa guest to reboot. I had to click Boxes from the launcher a second time, several seconds later, before anything visible happened at all. Presumably, the idea here is to make it less likely for a very inexperienced user to waste system resources on entirely idle VMs. There’s a (Run in background) option in the VM’s Properties dialog that should prevent the automatic hibernation — but that dialog is dangerous even to look at. The content of Properties is taller than the dialog itself, necessitating vertical scrolling.
Scrolling down the guest properties dialog with the mouse-wheel works — until that scrolling places the (Memory) or (Maximum Disk Size) slider under your mouse cursor. At that point, the focus suddenly shifts — and you’re suddenly resizing your guest’s RAM or hard drive. Yikes. A quick look at virt-manager This is a basic virt-manager overview — a list of all connected VM hosts and their VMs. Next to that, w have a console window open to a Windows domain controller VM, running on one of the remote hosts. Jim Salter - This peek at the hardware configuration of my Wi-Fi access point controller VM gives you a good idea of what virt-manager is all about — cleanly exposing all the bits and bobs. Jim Salter
- The button all the way on the right gives access to create and manage QEMU snapshots — which worked here, but failed under Boxes. Jim Salter
Virt-manager does not offer all the fancy download or desktop integration features Boxes does — but it’s considerably more capable and reliable.
A virt-manager VM won’t automatically hibernate itself when its console window is closed. It also won’t resize its desktop resolution to fit the window, or automatically feed a dropped file into a magic download. Seen from a sysadmin’s perspective, this lack is a feature, not a bug — it means that the guest is properly isolated , exposing it and the host to the minimum of weirdness (let alone security problems) from one another. Virt-manager also offers nearly effortless administration of multiple physical VM hosts. The view you see in the gallery above gives you some idea — in addition to the two hosts running in my home network, sharp eyes can spot five more hosts with hostnames ending in .wg, which in my case means they’re on the other side of a WireGuard tunnel.
A single virt-manager instance on a workstation can easily manage tens or even hundreds of separate hosts, connected by SSH tunnels using shared-key authentication. A double-click pops a graphical console window into the local or remote VM, using either Spice or VNC as the remote-control protocol. In the toolbar of a virt-manager console window, a simple set of start, pause, and power icons do exactly that — another offers the ability to create and manage snapshots (which Boxes failed at), and the Info button gives acce ss to inspect and modify the VM’s virtual hardware and related settings. Conclusions () Enlarge / No, we did not download the latest bleeding-edge version of Boxes from Flathub — but our Focal Fossa package is only a single minor point-release out of date.
Jim Salter I like the idea of Boxes, and I think there’s a definite market for it. The allure of incredibly safe, simple, and easy distro-hopping isn’t lost on me — and I particularly liked the integrated download mechanism. Unfortunately, I don’t think Boxes is ready for prime time yet. The number of sharp edges I encountered even with a very modern Linux guest OS running a Gnome3 desktop outweighed Boxes’ simplicity — let alone the completely broken install environment for OpenBSD, as compared to a “just works” experience on virt-manager. (The good)
- (Easy, dynamic search of available distros to install and play with Dynamic resolution changes to fit host window
Simple drag-and-drop operations to get files from host to guest — if the desktop environment in the guest supports it (The bad)
- Extreme lack of configurability Broken environments in distros that ” just work “on virt-manager Broken QEMU snapshot management (default allocation of) (all) host CPU threads to the guest
Lack of discoverability — where are the downloaded ISOs? Where are the guests’ virtual drives? (The ugly)
- (Focus-stealing, mouse-wheel resizing of the guest hard disk — what?!
Apparently broken re-launching due to guest hibernation No visibility to standard libvirt tools like (virsh) , (virt-top) , or virt-manager Buggy, odd ambiguation of normal remote control with guest management — trying to be too many things to too many people (Easy mode needs to be) (easy) , and at version 3. 406 and counting, Boxes just isn’t there yet. (Listing image by Jim Salter (Read More) (Full coverage and live updates on the Coronavirus (Covid -) ) -
- We had good results with an Ubuntu Focal Fossa guest, running on our Ubuntu Focal Fossa host system. Jim Salter
- When we resize the Boxes window, the Ubuntu Focal guest within it automatically changes its own video resolution to fit. Jim Salter
The extra integration is most evident when running Linux guests (virtual machines), where virtio drivers are always available and libvirt integration is at a maximum. When we tested an Ubuntu Focal Fossa guest, the guest’s video resolution dynamically and automatically as we resized its window on the host operating system — and files dragged from the host’s file explorer onto the Boxes window were automatically transferred into the guest, where they showed up in the logged-in user’s Downloads folder.
GIPHY App Key not set. Please check settings