Ryan Sawhill Aroha
Ryan Sawhill Aroha
I wrote upvm with only `virt-builder` and local libvirt in mind. One of my colleagues pointed out that it would be pretty cool if it could spin up the new...
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 │...
network interface, that is. Not sure if I should use the same name as `virsh` or come up with something else
Not sure about what to call it but `attach-disk` is already in `virsh`
corresponding with `virsh send-key` for sending keystrokes This could be used to send sysrq or ctrl-alt-del ... I dunno.