Language Selection

English French German Italian Portuguese Spanish

Getting started with GNOME Boxes virtualization

Filed under
GNOME
HowTos

I've been a fan of virtualization technology for many years, using many different products along the way. Virtualization has advantages for both the data center and the desktop: data centers use it to increase server hardware utilization, while desktop users use it for modeling, testing, and development work. One operating system running on top of a different one on the same hardware, all thanks to the concept of a virtual machine (VM).

I recently upgraded my laptop from Fedora 29 Workstation Edition Linux to version 30. I noticed GNOME Boxes, simply titled Boxes, in my application menu. The GNOME Project—whose members are the creators and maintainers of the GNOME Desktop Environment—describes GNOME Boxes as: "A simple GNOME application to view, access, and manage remote and virtual systems." Of course, I had to check this tool out.

This two part series article will cover two of the main features of Boxes. While writing this article, I used Boxes version 3.32.0.2-stable. Since the GNOME Boxes project refers to a VM as a "box," I'll use that terminology.

Read more

How to use GNOME Boxes' remote access capabilities

  • How to use GNOME Boxes' remote access capabilities

    In Part 1 of this series, I introduced GNOME Boxes, an open source virtualization tool maintained by the GNOME Project as part of its GNOME Desktop Environment. The GNOME Project describes Boxes as: "A simple GNOME application to view, access, and manage remote and virtual systems."

    In the previous article, I stepped through the process of creating a box running Fedora 30 Workstation. I showed how simple it is to get a box up and running with a wide range of operating systems. However, Boxes is not a one-trick pony; in addition to quickly creating a box locally, you can also connect to remote systems, both physical and virtual, using various protocols. Boxes' main screen then displays both local and remote boxes in a way that brings them together for easier access.

    Here in Part 2, I'll cover the remote access capabilities of Boxes. As in Part 1, I'll use Boxes' preferred terminology for a virtual machine, box.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Debian: CUPS, LTS and Archival

  • Praise Be CUPS Driverless Printing

    Last Tuesday, I finally got to start updating $work's many desktop computers to Debian Buster. I use Puppet to manage them remotely, so major upgrades basically mean reinstalling machines from scratch and running Puppet. Over the years, the main upgrade hurdle has always been making our very large and very complicated printers work on Debian. Unsurprisingly, the blog posts I have written on that topic are very popular and get me a few 'thank you' emails per month. I'm very happy to say, thanks to CUPS Driverless Printing (CUPS 2.2.2+), all those trials and tribulations are finally over. Printing on Buster just works. Yes yes, even color booklets printed on 11x17 paper folded in 3 stapled in the middle.

  • Freexian’s report about Debian Long Term Support, August 2019

    Like each month, here comes a report about the work of paid contributors to Debian LTS.

  • Louis-Philippe Véronneau: Archiving 20 years of online content

    mailman2 is pretty great. You can get a dump of an email list pretty easily and mailman3's web frontend, the lovely hyperkitty, is well, lovely. Importing a legacy mailman2 mbox went without a hitch thanks to the awesome hyperkitty_import importer. Kudos to the Debian Mailman Team for packaging this in Debian for us. But what about cramming a Yahoo! Group mailing list in hyperkitty? I wouldn't recommend it. After way too many hours spent battling character encoding errors I just decided people that wanted to read obscure emails from 2003 would have to deal with broken accents and shit. But hey, it kinda works! Oh, and yes, archiving a Yahoo! Group with an old borken Perl script wasn't an easy task. Hell, I kept getting blacklisted by Yahoo! for scraping too much data to their liking. I ended up patching together the results of multiple runs over a few weeks to get the full mbox and attachments. By the way, if anyone knows how to tell hyperkitty to stop at a certain year (i.e. not display links for 2019 when the list stopped in 2006), please ping me.

Running The AMD "ABBA" Ryzen 3000 Boost Fix Under Linux With 140 Tests

Last week AMD's AGESA "ABBA" update began shipping with a fix to how the boost clock frequencies are handled in hopes of better achieving the rated boost frequencies for Ryzen 3000 series processors. I've been running some tests of an updated ASUS BIOS with this adjusted boost clock behavior to see how it performs under Linux with a Ryzen 9 3900X processor. The AGESA 1.0.0.3 ABBA update has an improved boost clock frequency algorithm along with changes to the idle state handling. This AGESA update should better position AMD Ryzen 3000 processors with the boost clock behavior expected by users with better hitting the maximum boost frequency and doing so more aggressively. Read more

Stable kernels 5.2.16, 4.19.74, and 4.14.145

  • Linux 5.2.16
    I'm announcing the release of the 5.2.16 kernel. All users of the 5.2 kernel series must upgrade. The updated 5.2.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.2.y and can be browsed at the normal kernel.org git web browser: https://git.kernel.org/?p=linux/kernel/git/stable/linux-s...
  • Linux 4.19.74
  • Linux 4.14.145

Linux Container Technology Explained (Contributed)

State and local governments’ IT departments increasingly rely on DevOps practices and agile development methodologies to improve service delivery and to help maintain a culture of constant collaboration, iteration, and flexibility among all stakeholders and teams. However, when an IT department adopts agile and DevOps practices and methodologies, traditional IT problems still need to be solved. One long-standing problem is “environmental drift,” when the code and configurations for applications and their underlying infrastructure can vary between different environments. State and local IT teams often lack the tools necessary to mitigate the effects of environmental drift, which can hamper collaboration and agility efforts. Read more