When I create a VM with app-emulation/virt-manager-1.4.1 I get the error message: Unable to complete install: 'Domain has already been started!' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2288, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 455, in start_install raise RuntimeError(_("Domain has already been started!")) RuntimeError: Domain has already been started! and running: sudo virsh list --all returns: Id Name State ---------------------------------------------------- therefore this is not due to VMs that are already running with the same name. For further details here (https://forums.gentoo.org/viewtopic-p-8062596.html#8062596) is a Gentoo forum thread where I mentioned this issue. Downgrading virt-manager to 1.4.0-r3 fixes this error, so it is definitely related to 1.4.1 of virt manager. No matter how I change the details of the VM I still get this error.
That was with the USE flags: [ebuild R ] app-emulation/virt-manager-1.4.0-r3 USE="gtk (policykit) -debug -gnome-keyring -sasl" LINGUAS="-as -bg -bn_IN -bs -ca -cmn -cs -da -de -en_GB -es -fi -fr -gu -hi -hr -hu -is -it -ja -kn -ko -ml -mr -ms -nb -nl -or -pa -pl -pt -pt_BR -ro -ru -sk -sr -sr@latin -sv -ta -te -tr -uk -vi -zh_CN -zh_TW" PYTHON_TARGETS="python2_7" and QEMU: [ebuild R ] app-emulation/qemu-2.9.0-r1 USE="aio alsa bzip2 caps curl fdt filecaps gtk jpeg ncurses nls opengl pin-upstream-blobs png sdl seccomp vhost-net vnc xattr -accessibility -bluetooth -debug -glusterfs -gnutls -gtk2 -infiniband -iscsi -lzo -nfs -numa -pulseaudio -python -rbd -sasl -sdl2 (-selinux) -smartcard -snappy -ssh -static -static-user -systemtap -tci {-test} -virgl -virtfs -vte -xfs" LINGUAS="-bg -de_DE -fr_FR -hu -it -tr -zh_CN" PYTHON_TARGETS="python2_7" QEMU_SOFTMMU_TARGETS="x86_64 -aarch64 -alpha -arm -cris -i386 -lm32 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -moxie -nios2 -or1k -ppc -ppc64 -ppcemb -s390x -sh4 -sh4eb -sparc -sparc64 -tricore -unicore32 -xtensa -xtensaeb" QEMU_USER_TARGETS="-aarch64 -alpha -arm -armeb -cris -hppa -i386 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -mipsn32 -mipsn32el -nios2 -or1k -ppc -ppc64 -ppc64abi32 -ppc64le -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -tilegx -x86_64" and libvirt: [ebuild R ] app-emulation/libvirt-3.2.0 USE="caps dbus libvirtd macvtap nls (policykit) qemu udev vepa -apparmor -audit -firewalld -fuse -glusterfs -iscsi -libssh -lvm -lxc -nfs -numa -openvz -parted -pcap -phyp -rbd -sasl (-selinux) -uml -virt-manager -virtualbox -wireshark-plugins -xen -zeroconf -zfs"
oops I meant: [ebuild R ] app-emulation/virt-manager-1.4.1 USE="gtk (policykit) -debug -gnome-keyring -sasl" LINGUAS="-as -bg -bn_IN -bs -ca -cmn -cs -da -de -en_GB -es -fi -fr -gu -hi -hr -hu -is -it -ja -kn -ko -ml -mr -ms -nb -nl -or -pa -pl -pt -pt_BR -ro -ru -sk -sr -sr@latin -sv -ta -te -tr -uk -vi -zh_CN -zh_TW" PYTHON_TARGETS="python2_7"
That happens when a domain with said name has already been created (or started). This can sometimes happen when the domain creation wizard encounters an error.
