2024-01-22 23:48:52 +01:00
# `qemush` - A suckless QEMU wrapper written in shell
2023-12-04 12:00:35 +01:00
2023-12-05 22:24:41 +01:00
[![Please don't upload to GitHub ](https://nogithub.codeberg.page/badge.svg )](https://nogithub.codeberg.page)
2023-12-04 12:00:35 +01:00
## How does it work
2024-03-25 18:26:36 +01:00
`qemush` allows to run commands as Unix user `qemu` to manage virtual machines and their disks associated.
2023-12-04 16:21:53 +01:00
2023-12-04 12:00:35 +01:00
## Why
2024-03-25 18:26:36 +01:00
`qemush` is **daemonless** : no bloaty long running process is needed for `qemush` to work.
2023-12-04 16:21:53 +01:00
2024-03-25 18:26:36 +01:00
`qemush` is **lightweight** : it only consists in a shell script to automate repeated tasks and force good practices.
2023-12-04 16:21:53 +01:00
2024-03-25 18:26:36 +01:00
`qemush` needs **few dependencies** : see section [Dependencies ](#dependencies ) for details.
2023-12-04 16:21:53 +01:00
2024-03-25 18:26:36 +01:00
`qemush` is **hackable** : you can [write your own launching scripts ](#writing-a-launching-script ) to make it work as intended.
2023-12-04 16:21:53 +01:00
2024-03-25 18:26:36 +01:00
`qemush` is **easy to setup** : you can make it work in a few steps, see section [Installation instructions ](#installation-instructions ).
2023-12-04 12:00:35 +01:00
2023-12-04 22:42:48 +01:00
## Good practices?
Here is a list of good practices forced by `qemush` .
2024-03-25 18:26:36 +01:00
- **Processes running as user `qemu` **: members of group `qemu` can manage the same virtual machines
- **Modularization**: `qemush` launching scripts are intended to be stackable to reuse common `qemu` parameters in all virtual machines needing them keep track of them
- **Copy-on-write**: images are formatted using `qcow2` to use less space on disk
- **Process detachment**: you can log out and have your virtual machines still running, control them via Unix sockets
2023-12-04 22:42:48 +01:00
2024-03-25 14:51:52 +01:00
## Is it better than `libvirt` ?
No. `qemush` and `libvirt` are for different use cases. `qemush` will allow you to spin up virtual machines really fast and with as little setup as possible, and aims to be nothing more than a QEMU wrapper, while `libvirt` will offer better out-of-the-box experience, with already existing pre-configurations, associated tools like the `virt-manager` GUI and a friendlier process supervision. You should use `qemush` if you care about controlling every aspect of your virtual machines, and are already used to using bare QEMU without an abstraction layer.
2023-12-04 12:00:35 +01:00
## Dependencies
2024-03-25 14:52:12 +01:00
From version 0.9.0, `qemush` is written in pure POSIX shell! The previous dependency on `bash` was removed in consequence.
2024-03-25 18:26:36 +01:00
All dependencies are common packages for a distribution, you'll be able to grab them from your favorite packages sources.
2023-12-04 22:43:18 +01:00
2024-03-25 18:26:36 +01:00
- `qemu` - this is literally a QEMU wrapper so there's a chance you'll need it
2024-03-25 14:52:12 +01:00
- A POSIX compliant shell - `bash` (POSIX mode), `*ash` , `*ksh` are POSIX shells
2023-12-04 16:21:53 +01:00
- `coreutils` - used for basic OS operations
- `sudo` - execute commands as `qemu`
2024-01-22 23:38:39 +01:00
- `socat` - monitor machines via Unix sockets
2023-12-04 22:49:38 +01:00
- any text editor - used for builtin function to edit launching scripts
2023-12-04 12:00:35 +01:00
## Installation instructions
2023-12-04 16:21:53 +01:00
### QEMU user and group
2024-03-25 18:26:36 +01:00
`qemush` acts as Unix user `qemu` to manage virtual machines. You need to create a system user `qemu` that cannot login, with any home directory, in an Unix group of the same name. Example:
2023-12-04 16:21:53 +01:00
```sh
# Example if the qemu user doesn't exist
# Make sure /etc/shells contains /bin/nologin
useradd -r -s /bin/nologin qemu
```
2024-03-25 18:26:36 +01:00
For ease of use, you need to grant every user in the `qemu` group via `sudo` the right to execute commands as `qemu` . You can find an example `sudoers` rule in this repo's `etc/sudoers.d` folder.
2023-12-04 16:21:53 +01:00
2023-12-10 17:56:52 +01:00
### Via `Makefile` (recommended)
2023-12-04 16:21:53 +01:00
2024-03-25 18:26:36 +01:00
Just run the following command at the root of this repository to install `qemush` (previous step is **mandatory** ) :
2023-12-08 11:23:41 +01:00
```sh
2023-12-10 17:56:52 +01:00
make
2023-12-08 11:23:41 +01:00
```
2023-12-10 17:56:52 +01:00
> And what if I don't want to bindly run this obscure `Makefile` ???
2023-12-04 22:43:37 +01:00
2024-03-25 18:26:36 +01:00
You'd be right. The next section is the exhaustive list of steps handled by the `Makefile` for the installation process.
2023-12-08 10:59:49 +01:00
2023-12-10 17:56:52 +01:00
### Manual installation (what does the `Makefile` do)
2023-12-08 10:59:49 +01:00
2024-03-25 22:12:13 +01:00
- Create `disks` , `launchers` , `shared` , `sockets/monitors` , `socket/spice` and `bin` directories in `~qemu`
2024-03-25 18:26:36 +01:00
- Copy `qemush` scripts parts from `qemu/bin` in `~qemu/bin` with mode `740`
2023-12-10 17:56:52 +01:00
- Compile C programs from `src` in `~qemu/bin` with mode `740`
2024-03-25 22:13:09 +01:00
- Copy the default launching scripts to `~qemu/launchers` with mode `740` ; this is optional but the one called `kvm` is the reference `qemush` launching script!
2023-12-10 17:56:52 +01:00
- Copy `bin/qemush` to `/usr/local/bin/qemush` with mode `755`
2023-12-04 22:43:37 +01:00
2023-12-04 16:21:53 +01:00
## Usage
### Writing a launching script
2024-03-25 22:13:27 +01:00
The default text editor used by `qemush` is `vi` , but it can be overriden by the `EDITOR` environment variable.
2023-12-04 16:21:53 +01:00
2024-03-25 18:26:36 +01:00
Run the following command to start editing a launching script by the name of your choice:
2023-12-04 16:21:53 +01:00
```sh
qemush edit "$name"
```
2024-01-23 00:01:05 +01:00
Example scripts are available in this repo's `qemu/launchers` folder.
2023-12-04 16:21:53 +01:00
### Launching a virtual machine
2024-03-25 18:26:36 +01:00
Virtual machines are identified by the name of their launching scripts. You can launch any machine with the following command:
2023-12-04 16:21:53 +01:00
```sh
qemush start "$name"
```
2023-12-04 22:43:58 +01:00
2023-12-04 22:48:54 +01:00
You can also list all available virtual machines by running this command:
2023-12-04 22:43:58 +01:00
```sh
qemush ls
```
2023-12-06 11:25:39 +01:00
### Other uses
You can show the full list of possible actions by running this command:
```sh
qemush help
```