Aha, thank you! That’s just a weird enough concept to “attach to” a local QEMU user session (where virt-manager will be the guy spinning it off anyway) that I would never have seen it.
Every newbie article about virt-manager starts with a filled list of connections, so I was down to figuring that it’s cleverly detecting a missing dependency or permission and silently eliminating list entries for me.
Glad it helped! The idea is that virt-manager is semi backend agnostic. It’ll doe Xen, Qemu, and LXC via libvirt, and it can do those as root, or unprivileged as well as connect to remote sessions via ssh. Pretty darn cool!
Aha, thank you! That’s just a weird enough concept to “attach to” a local QEMU user session (where virt-manager will be the guy spinning it off anyway) that I would never have seen it.
Every newbie article about virt-manager starts with a filled list of connections, so I was down to figuring that it’s cleverly detecting a missing dependency or permission and silently eliminating list entries for me.
Glad it helped! The idea is that virt-manager is semi backend agnostic. It’ll doe Xen, Qemu, and LXC via libvirt, and it can do those as root, or unprivileged as well as connect to remote sessions via ssh. Pretty darn cool!
Don’t you hate it when a newbie how-to doesn’t start from where a newbie will, with a fresh install and nothing configured and no prior knowledge?