Description of problem: Here's an example. I want to do something with my rawhide VM. The steps I have to take are as follows: 1. Start virt-manager 2. Double-click on 'localhost (QEMU)' 3. Enter a password 4. Double-click on the VM name 5. Click on the 'run' button Shouldn't there be some way to create a simple one-click 'run this VM' button? Version-Release number of selected component (if applicable): virt-manager-0.8.2-1.fc12.noarch
For 1-3, you can enable the virt-manager system icon via Edit->Preferences and leave the app running. Then its just a matter of navigating menus. You can also set the connection to autostart via Edit->Host Details, which would eliminate step 2. A default run of virt-manager should set this up for you, and manually adding a connection should default to it. You could use manual polkit config to kill step 3, but its always going to be an issue until we switch to using qemu/kvm usermode by default. For 4-5, there are other options: Right click->Run, or use the manager toolbar. Do you have toolbars disabled? Any specific ideas?
(In reply to comment #1) > For 1-3, you can enable the virt-manager system icon via Edit->Preferences and > leave the app running. Then its just a matter of navigating menus. > > You can also set the connection to autostart via Edit->Host Details, which > would eliminate step 2. A default run of virt-manager should set this up for > you, and manually adding a connection should default to it. Aha. I suppose I've been running v-m since before this was added, as it wasn't set. > Any specific ideas? Maybe I'm nuts, but something like integration in the gnome menu, where you'd have something in the Places menu that either had each VM listed, or something that popped up a nautilus window with an icon for each VM. Choosing the icon would then start the VM console viewer (and the domain if necessary.)
I think the major preliminary step for fixing this whole scenario is proper use of qemu:///session for desktop virt: things like 'Places' integration could extend from there since VMs would be clearly owned by a single user, and not the current hack of working with the system libvirtd instance. *** This bug has been marked as a duplicate of bug 557103 ***