You are not logged in.

#1 2014-02-21 23:13:40

syamajala
Member
From: here, there, everywhere
Registered: 2005-01-25
Posts: 613
Website

[SOLVED] virt-manager opening backend socket failed

I'm trying to install fedora using virt-manager. I get the following error when I click finish in the create a new virtual machine dialog.

Unable to complete install: 'internal error: process exited while connecting to monitor: qemu-system-x86_64: -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/fedora20.org.qemu.guest_agent.0,server,nowait: Failed to bind socket: Permission denied
qemu-system-x86_64: -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/fedora20.org.qemu.guest_agent.0,server,nowait: 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 1781, in do_install
    guest.start_install(meter=meter)
  File "/usr/share/virt-manager/virtinst/guest.py", line 400, in start_install
    noboot)
  File "/usr/share/virt-manager/virtinst/guest.py", line 464, in _create_guest
    dom = self.conn.createLinux(start_xml or final_xml, 0)
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 3199, 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=/var/lib/libvirt/qemu/channel/target/fedora20.org.qemu.guest_agent.0,server,nowait: Failed to bind socket: Permission denied
qemu-system-x86_64: -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/fedora20.org.qemu.guest_agent.0,server,nowait: chardev: opening backend "socket" failed

Last edited by syamajala (2014-03-31 12:55:29)

Offline

#2 2014-02-26 18:16:27

zosodk69
Member
Registered: 2005-01-30
Posts: 30

Re: [SOLVED] virt-manager opening backend socket failed

I see the same thing when I choose Fedora 20 as my guest OS type.  All other guest types appear to work.


-=[dave]=-

Offline

#3 2014-02-27 14:37:28

zosodk69
Member
Registered: 2005-01-30
Posts: 30

Re: [SOLVED] virt-manager opening backend socket failed

RHEL 7 appears to exhibit the same problem.


-=[dave]=-

Offline

#4 2014-03-01 23:42:16

ktdassoff
Member
Registered: 2013-09-09
Posts: 1

Re: [SOLVED] virt-manager opening backend socket failed

I was having this problem (with Fedora 20 too, as it happens). What I tried, and has worked so far was that I noticed in /etc/libvirt/qemu.conf, there are the lines

#user = "root"
group = "kvm"

It seems then QEMU is being started by libvirtd under user 'nobody' (since the user line is commented out, 'nobody' seems to be the default) and group 'kvm'. In /var/lib/libvirt, the qemu subdirectory and its subdirectories are all owned by nobody:kvm except for the channel and dump directories on my system. So I changed the ownership of those directories with

$ cd /var/lib/libvirt/qemu
$ sudo chown -R nobody:kvm channel dump

And after that I was able to create and run the VM just fine!

Just did this, so I haven't had a chance to check that libvirtd doesn't modify the permissions on startup, but hopefully this will stick.

Offline

#5 2014-03-31 12:53:41

maevius
Member
From: Greece
Registered: 2009-09-10
Posts: 135
Website

Re: [SOLVED] virt-manager opening backend socket failed

Exact same problem with a Fedora machine. I can confirm what ktdassoff posted. This can be marked as SOLVED smile

Offline

#6 2014-03-31 12:55:17

syamajala
Member
From: here, there, everywhere
Registered: 2005-01-25
Posts: 613
Website

Re: [SOLVED] virt-manager opening backend socket failed

I haven't tried the solution, but if you say it works, I'll mark it solved.

Offline

#7 2014-04-12 09:36:24

carepack
Member
Registered: 2014-02-14
Posts: 12

Re: [SOLVED] virt-manager opening backend socket failed

ktdassoff wrote:

I was having this problem (with Fedora 20 too, as it happens). What I tried, and has worked so far was that I noticed in /etc/libvirt/qemu.conf, there are the lines

#user = "root"
group = "kvm"

It seems then QEMU is being started by libvirtd under user 'nobody' (since the user line is commented out, 'nobody' seems to be the default) and group 'kvm'. In /var/lib/libvirt, the qemu subdirectory and its subdirectories are all owned by nobody:kvm except for the channel and dump directories on my system. So I changed the ownership of those directories with

$ cd /var/lib/libvirt/qemu
$ sudo chown -R nobody:kvm channel dump

And after that I was able to create and run the VM just fine!

Just did this, so I haven't had a chance to check that libvirtd doesn't modify the permissions on startup, but hopefully this will stick.



thx. this did the trick to me..... magic wink

Offline

#8 2016-03-07 18:39:07

Dravigon
Member
Registered: 2015-10-15
Posts: 3

Re: [SOLVED] virt-manager opening backend socket failed

[Mon, 07 Mar 2016 23:49:31 virt-manager 2592] DEBUG (create:2065) Starting OS detection thread for media=/run/media/dravigon/80942DA5942D9EA2/Downloads/en_windows_10_pro_10240_x64_dvd/win10.iso
[Mon, 07 Mar 2016 23:49:31 virt-manager 2592] DEBUG (storagebrowse:66) Closing storage browser
[Mon, 07 Mar 2016 23:49:31 virt-manager 2592] DEBUG (distroinstaller:514) installer.detect_distro returned=None
[Mon, 07 Mar 2016 23:49:31 virt-manager 2592] DEBUG (create:2143) Finished UI OS detection.
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (connection:1309) Error polling connection lxc:///
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1289, in tick_from_engine
    self._tick(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/connection.py", line 1179, in _tick
    self._hostinfo = self._backend.getInfo()
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 3804, in getInfo
    if ret is None: raise libvirtError ('virNodeGetInfo() failed', conn=self)
libvirtError: internal error: client socket is closed
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (connection:842) conn.close() uri=lxc:///
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (connection:853) Failed to deregister events in conn cleanup
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 848, in close
    self._backend.domainEventDeregisterAny(eid)
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 4890, in domainEventDeregisterAny
    if ret == -1: raise libvirtError ('virConnectDomainEventDeregisterAny() failed', conn=self)
libvirtError: internal error: client socket is closed
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (connection:1309) Error polling connection qemu:///system
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1289, in tick_from_engine
    self._tick(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/connection.py", line 1179, in _tick
    self._hostinfo = self._backend.getInfo()
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 3804, in getInfo
    if ret is None: raise libvirtError ('virNodeGetInfo() failed', conn=self)
libvirtError: internal error: client socket is closed
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (connection:568) conn=lxc:/// changed to state=Disconnected
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (error:99) error dialog message:
summary=Error polling connection 'lxc:///': internal error: client socket is closed
details=Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 385, in _handle_tick_queue
    conn.tick_from_engine(**kwargs)
  File "/usr/share/virt-manager/virtManager/connection.py", line 1319, in tick_from_engine
    raise e  # pylint: disable=raising-bad-type
libvirtError: internal error: client socket is closed

[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (connection:842) conn.close() uri=qemu:///system
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (connection:853) Failed to deregister events in conn cleanup
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 848, in close
    self._backend.domainEventDeregisterAny(eid)
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 4890, in domainEventDeregisterAny
    if ret == -1: raise libvirtError ('virConnectDomainEventDeregisterAny() failed', conn=self)
libvirtError: internal error: client socket is closed
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (connection:568) conn=qemu:///system changed to state=Disconnected
[Mon, 07 Mar 2016 23:49:34 virt-manager 2592] DEBUG (error:99) error dialog message:
summary=Error polling connection 'qemu:///system': internal error: client socket is closed
details=Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 385, in _handle_tick_queue
    conn.tick_from_engine(**kwargs)
  File "/usr/share/virt-manager/virtManager/connection.py", line 1319, in tick_from_engine
    raise e  # pylint: disable=raising-bad-type
libvirtError: internal error: client socket is closed

[Mon, 07 Mar 2016 23:59:35 virt-manager 2592] DEBUG (create:205) Closing new vm wizard
[Tue, 08 Mar 2016 00:00:47 virt-manager 2592] DEBUG (manager:214) Closing manager
[Tue, 08 Mar 2016 00:00:47 virt-manager 2592] DEBUG (engine:405) window counter decremented to 0
[Tue, 08 Mar 2016 00:00:47 virt-manager 2592] DEBUG (engine:467) No windows found, requesting app exit
[Tue, 08 Mar 2016 00:00:47 virt-manager 2592] DEBUG (engine:491) Exiting app normally.



this is the log i get while i try to create a windows kvm and i tried ur sugession but still not working

Offline

Board footer

Powered by FluxBB