Milkey Mouse
Milkey Mouse
If a VM has complex chains of disks (e.g. you want to back up snapshots already created, or even just having a qcow2 with another backing disk before running) not...
See https://github.com/borgbackup/borg/pull/3731#issuecomment-376658214. Would only work if borgbackup/borg#2233 happens.
should probably mock libvirt instead of relying on the actual library. I'm leaning towards using the builtin `unittest` module instead of `nose` or `py.test` since it's supported on all python...
- [x] Refactor single file into module (e1b1519) - [x] Basic restore functionality (aae2c0e) - [ ] Create non-dummy implementation of `DiskLock` (see [libvirt source](https://libvirt.org/git/?p=libvirt.git;a=blob;f=src/locking/lock_driver_lockd.c;h=c3fc18a8a7686ca12251f7fe48d2a916c888e038;hb=291f68b5da78a303c58ca45b5d8be61e8047d328#l485), it doesn't look like this...
In order for libvirt to allow restoration, backup and restore ops would have to fully store the state of the snapshot in the backup so it can be tacked back...
libvirt has disk types other than the `file` and `block` that I've tried. See the [libvirt docs](https://libvirt.org/formatdomain.html#elementsDisks) (specifically the section on the `source` attribute).
These are common enough (especially on the web) that a new user might try to use a 3-digit hex color such as `#f00`. We might as well make this work...
These are common enough (especially on the web) that a new user might try to use a 3-digit hex color such as `#f00` (or one with transparency such as `#f008`)....
I set swaylock's background color to #000000 by default, which worked great until I got an OLED monitor. Now I can't tell if the screen is off (due to swayidle)...