Description of problem: I am unable to create a VM on qemu:///session while it works on qemu:///system using the same settings. The error message I get: Unable to complete install: 'internal error: process exited while connecting to monitor: qemu-system-x86_64: -chardev socket,id=charchannel0,path=/home/mimox/.config/libvirt/qemu/lib/channel/target/fedora20.org.qemu.guest_agent.0,server,nowait: Failed to bind socket: No such file or directory chardev: opening backend "socket" failed ' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: qemu-system-x86_64: -chardev socket,id=charchannel0,path=/home/mimox/.config/libvirt/qemu/lib/channel/target/fedora20.org.qemu.guest_agent.0,server,nowait: Failed to bind socket: No such file or directory chardev: opening backend "socket" failed Version-Release number of selected component (if applicable): virt-manager-1.0.1-3.fc20.noarch libvirt-1.1.3.5-2.fc20.x86_64 qemu-kvm-1.6.2-5.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. connect to qemu:///session 2. try to create or import any VM
Same here (Kernel version 3.15.4-200.fc20.x86_64) However, creating VMs with gnome-boxes works fine (although it uses qemu:///session as well), and afterwards these VMs can be started with virt-manager as well.
Issue seems to be that libvirt isn't creating the .../target/channel directory automatically for qemu session
Still present in Fedora 21.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
On fedora 20 I can workaround by choosing "Customize configuration before install" and deleting the "Channel qemu-ga" from the tab sidebar. The machine seems to install with spice/qxl and a spice channel so I don't think I need to add the qemu-qa guest device after installation, right? None of the VMs created in F19 and earlier seem to have the qemu guest agent installed.
Does gnome-boxes install the qemu guest agent, or is it just virt-manager?
Patch posted upstream: https://www.redhat.com/archives/libvir-list/2015-April/msg01212.html
libvirt-1.2.13.1-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libvirt-1.2.13.1-1.fc22
Package libvirt-1.2.13.1-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libvirt-1.2.13.1-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7122/libvirt-1.2.13.1-1.fc22 then log in and leave karma (feedback).
libvirt-1.2.13.1-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.