valine
valine copied to clipboard
Easy qcow & LVM snapshot management of libvirt guests with intelligent tab-completion
I think this should be added as a note in the README. When running valine I received the following error message: ``` root@helios:~# v column: invalid option -- 'o' usage:...
On Fedora 27 I'm getting escape color codes instead of the actual colors for snapshots:  On RHEL 7.4 it works fine.
Summary: Use parameter substitution to do dirname not basename. Reproducing: Run valine while the /var/lib/valine directory does not exist. Expected: mkdir: cannot create directory ‘/var/lib/valine’: Permission denied Error: Missing [and...
When running valine on a Fedora25 for the first time, I receive, one per each VM in my libvirt: ``` ./valine/valine: riga 330: /var/lib/valine/centos7-prometheus: No such file or directory ./valine/valine:...
Sourcing `/etc/bash_completion.d/valine-bash-completion.bash` with zsh works, but it's not loaded automatically.
Not sure about the name, but of course the goal would be to launch virt-viewer for you.
What if we moved all the multiline snapshot details from the main `valine` output and into the per-VM output (e.g., `valine SOMEVM`) ...? We could then keep the main `valine`...
I literally forgot about `virt-top` ... haven't touched it in a couple years. It's too awesome not to use.
I'm leaning toward yes. E.g., mockup: ``` ─────────┬───┬──────────────┬───────┬─────────┬─────────────────────────────────────────── DOMAIN │ ⚡ │ MEMORY │ VCPU │ STORAGE │ SNAPSHOTS ─────────┼───┼──────────────┼───────┼─────────┼─────────────────────────────────────────── r67 │ ◉ │ 2048M │ 2 │ qcow2 │...