Skip to content

Latest commit

 

History

History
230 lines (176 loc) · 9.14 KB

README.md

File metadata and controls

230 lines (176 loc) · 9.14 KB
Raw
Table of Contents
  1. Overview
  2. Getting Started
  3. Usage
  4. Roadmap
  5. Contributing
  6. License
  7. Contact
  8. Acknowledgments

Status

This package is still under construction. This readme needs more work. The script is feature complete for the initial feature set, tested, and deployeed in my home lab. Tested on Debian 10 (soon Debian 12). However this needs significant testing by others in a variety of uses. I welcome new issue submissions and, ideally, pull requests with fixes.

Overview

virt-compose is a script that mirrors lifecycle aspects of virsh and virt-install commands reading necessary inputs from a simple VM definition file in YAML. It also dynamically manages USB host device passthrough with udev/systemd.

Motivation

In needed a small, simple system to manage the lifecycle of KVM VMs on a home lab server. Something similar to the functionality that Docker Compose brings to containers. There are fully functional systems already available for KVM, mostly as GUIs, but those have steep learning curves and rapidly evolving feature sets that create breaking functionality churn. I just wanted something simple to remember that is too small to need rapidly evolving functionality (i.e. stable over time). A system where consumers can know that backward compatibility is always maintained. The system just needs a few features that are primarily motivated by the need to manage hot-plug events for USB host passthrough while managing the lifecycle of VMs. Base requirements:

  • Manage USB host passthrough devices
  • Start VMs at host startup
  • Stop VMs at host shutdown
  • Build VMs from a templated config defining VMs

Supported Actions

Actions read VM configuration from: /etc/virt-compose/vm/{vm_name}/{vm_name}.yaml

  • install {vm_name}
    • Calls: virt-install
    • This command will do all the things necessary to define the VM but does not start the VM. There is more than you think (e.g. prepping the boot device, creating the cloud-init CDROM image, etc.)
    • Creates the systemd service called by udev on USB host device hot-plug event
  • start {vm_name}
    • Calls: virsh attach-device, virsh start
    • Wraps the virsh attach-device command, locating the IDs, creating the necessary XML file, etc.
    • Wraps the virsh start command
    • Creates the udev rules for each defined USB host device hot-plug event
  • start-all
    • Calls: start for each VM definition where autoStart=true
  • shutdown {vm_name}
    • Calls: virsh shutdown, virsh detach-device
    • Wraps the virsh shutdown command
    • Deletes the udev rules for each defined USB host device hot-plug event
  • shutdown-all
    • Calls: shutdown for every VM definition where autoStart=true
  • attach-device {vm_name} {$devpath}
    • Calls: virsh attach-device
    • Wraps the virsh attach-device command, locating the IDs, creating the necessary XML file, etc.
    • Called by systemd when udev fires events for a USB host device hot-plug event
  • detach-device {vm_name} {$devpath}
    • Calls: virsh detach-device
    • Wraps the virsh detach-device command, locating the IDs, creating the necessary XML file, etc.
  • undefine {vm_name}
    • Calls: virsh undefine
    • Deletes the systemd service called by udev on USB host device hot-plug event
    • Will not allow undefine on VMs that are not shutdown first as a safety interlock

Systemd Services

  • virt-compose.service On host startup, starts all VMs designated as auto-start. On host shutdown, stops all services, if the service is running Calls virt-compose [start|shutdown] --all
  • virt-compose-{vm_name}@.service Triggers attach USB host device when udev rules detect monitored devices Calls virt-compose attach-device {$VM} {$devpath}

Getting Started

Prerequisites

  • A Debian 10 or later system (systemd based distribution)
  • A working qemu-kvm installation with virsh and virt-install
  • sudo, yq, xorriso, qemu-utils

Installation

  1. Install yq manually if your package manager does not support yq

    sudo wget https://github.com/mikefarah/yq/releases/latest/download/yq_linux_amd64 \
    -O /usr/bin/yq && sudo chmod +x /usr/bin/yq

  2. Install virt-compose from github

    git clone https://github.com/mstovenour/virt-compose.git virt-compose.git
cd virt-compose.git
./install.sh --config ./virt-compose.yaml

  3. Edit /etc/virt-compose/vm/example_vm1/example_vm1.yaml:

    • Update imageLocation for a Debian generic qcow2
    • Update usbHostDev for currently installed usb devices
    vi /etc/virt-compose/vm/example_vm1/example_vm1.yaml

  4. Test the VM lifecycle

    virt-compose install example_vm1
virt-compose start example_vm1
virt-compose shutdown example_vm1
virt-compose undefine example_vm1

(back to top)

Usage

virt-compose

Usage: virt-compose [-h|--help] [-c|--config] {action} [vm_name] [device_path]

virt-compose is a script that mirrors lifecycle aspects of virsh and virt-install commands
reading necessary inputs from a simple VM definition file in YAML.  It also dynamically
manages USB host device passthrough with udev/systemd.

Optional arguments:
 -h, --help          Show this help message and exit
 -c, --config        Specify full config file path
                       (default: /etc/virt-compose/virt-compose.yaml)
 [vm_name]           Unique name of the KVM VM (no hyphens)
 [device_path]       Specifies the device path for use with attach/detach

Required arguments:
 {action}            install {vm_name}
                     start {vm_name}
                     start-all
                     shutdown {vm_name}
                     shutdown-all
                     attach-device {vm_name} {device_path}
                     detach-device {vm_name} {device_path}
                     undefine {vm_name}

(back to top)

Roadmap

See the open issues for a list of proposed features (and known issues).

(back to top)

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement" but you may not find someone willing to write the code.

Don't forget to give the project a star! Thanks again!

  1. Fork the Project on Github
  2. Create a clone on your workspace (git clone https://github.com/{your-user-name}/virt-compose.git)
  3. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  4. Code away and don't forget to TEST
  5. Commit your Changes (git commit -m 'Add some AmazingFeature')
  6. Push the Branch to your Github repository (git push origin feature/AmazingFeature)
  7. Open a Pull Request in Github

(back to top)

License

Distributed under the Apache 2.0 License. See LICENSE for more information.

Copyright

Copyright 2024 Michael Stovenour

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

(back to top)

Contact

Project Link: https://github.com/mstovenour/virt-compose

(back to top)

Acknowledgments

This README.md is based on https://github.com/othneildrew/Best-README-Template

(back to top)