Description of problem: I ran virt-install; it popped up virt-viewer. I moved the viewer to a different workspace. Eventually the install finished, and the guest rebooted. When it did, virt-viewer jumped to the active workspace. Version-Release number of selected component (if applicable): virt-viewer-0.0.3-4.fc11.x86_64 python-virtinst-0.400.3-1.fc11.noarch
Ah yes - we don't actually reboot; we shut down the guest and start it again We need to do this because the config will have changed - e.g. you initially boot with vmlinuz/initrd but after install you want to boot with grub Upshot is that we launch virt-viewer multiple times and there's no straightforward way of staying on the same workspace Perhaps we could have a flag to not have virt-viewer shutdown when the guest shuts down, but rather automatically re-connect when the guest is started again Not going to be a huge problem for most people, moving upstream.
Upstream virt-viewer (non-released) code does now have ability to wait for non-running VMs to startup, and also wait for them to restart upon shutdown, instead of exiting. There's a few more changes we need before we can release this code, so its a F12 kind of feature realistically.
there is -w option for quite some time. Apparently virt-install makes use of it for quite some time. closing