You are not logged in.
Hi there,
i use the current virt-manager from aur (0.8.2-1) and libvirt (0.7.5-1).
But libvirt crashes when virt-manager tries to connect:
Dec 27 19:30:42 q9400-arch libvirtd: 19:30:42.997: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:42 q9400-arch libvirtd: 19:30:42.997: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:42 q9400-arch libvirtd: 19:30:42.998: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:42 q9400-arch libvirtd: 19:30:42.998: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:42 q9400-arch libvirtd: 19:30:42.998: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:42 q9400-arch libvirtd: 19:30:42.999: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:42 q9400-arch libvirtd: 19:30:42.999: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.000: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.000: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.002: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.003: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.004: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.012: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.022: error : virLibNodeDeviceError:618 : invalid node device pointer in virNodeDeviceFree
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.023: error : qemudDomainGetVcpus:4095 : Requested operation is not valid: cannot list vcpu pinning for an inactive domain
Dec 27 19:30:43 q9400-arch libvirtd: 19:30:43.025: error : qemudDomainGetVcpus:4095 : Requested operation is not valid: cannot list vcpu pinning for an inactive domain
Dec 27 19:30:43 q9400-arch kernel: libvirtd[4344] general protection ip:7f969935c7c2 sp:7f9696449c08 error:0 in libc-2.11.1.so[7f96992e1000+14d000]
What's wrong there? Or do i something wrong?
Regards
Last edited by LukeGee (2009-12-27 18:40:06)
Offline
If you have upgraded glibc after installing/building libvirt, try rebuilding libvirt.
Offline
If you have upgraded glibc after installing/building libvirt, try rebuilding libvirt.
I did, but I get the same error :S
I also completely reinstalled virt-manager and libvirt and removed all config files etc.
Offline
This seems to be a general protection fault, which is a sign of a programming error or similar.
In any case I suggest you take this upstream: http://libvirt.org/
Offline
mh I see in the aur at virt-manager;
Comment by: kidoz on Mon, 28 Dec 2009 10:04:39 +0000
Broken with libvirt 0.7.5-1 x86_64.
Offline
Do you get anymore information if you run libvirtd like:
# /etc/rc.d/libvirtd stop
# libvirtd -v
Offline
Do you get anymore information if you run libvirtd like:
# /etc/rc.d/libvirtd stop
# libvirtd -v
Nope, just that from the first post.
I tried the libvirt-git package and I don't get this error, but it says that there is no hypervisor drvier for qemu:///system.
Offline
In your guest configs do you have more than 1 vcpu assigned to each guest? May try brining it down to just 1 if thats the case
Offline
No I don't have any configurated guests. I can't start virt-manager again. It says now:
Jan 22 18:31:04 q9400-arch libvirtd: 18:31:04.860: error : virLibConnError:441 : no hypervisor driver available for qemu:///system
Offline
No I don't have any configurated guests. I can't start virt-manager again. It says now:
Jan 22 18:31:04 q9400-arch libvirtd: 18:31:04.860: error : virLibConnError:441 : no hypervisor driver available for qemu:///system
Did you install the git version from aur? What about from virtsh
# virtsh --readonly -c qemu:///system
This is of course assuming it can actually see the kvm drivers
Offline
LukeGee wrote:No I don't have any configurated guests. I can't start virt-manager again. It says now:
Jan 22 18:31:04 q9400-arch libvirtd: 18:31:04.860: error : virLibConnError:441 : no hypervisor driver available for qemu:///system
Did you install the git version from aur? What about from virtsh
# virtsh --readonly -c qemu:///system
This is of course assuming it can actually see the kvm drivers
Yes, I installed git libvirt version from aur.
[lukas@q9400-arch:~]$ virsh --readonly -c qemu:///system
Fehler: no hypervisor driver available for qemu:///system
Fehler: Verbindung zum Hypervisor scheiterte
But the kvm modules are loaded:
[lukas@q9400-arch:~]$ lsmod | grep kvm
kvm_intel 42750 0
kvm 254528 1 kvm_intel
Offline
Ive seen other problems with the git version of libvirt; i suggest removing it and going back to the latest released version and attempt to get readonly access as before
Offline
Ive seen other problems with the git version of libvirt; i suggest removing it and going back to the latest released version and attempt to get readonly access as before
With the latest version I can connect readonly (_and_ regular readwrite) with virsh (but with virt-manager libvirt segfaults)
Offline
I would append the following on the ./configure line of the PKGBUILD
--enable-debug=yes
That will give you a better step by step up until the point of failure then maybe we can figure out why you are getting those invalid device node pointers.
Offline
I cannot make head or tail of it:
http://lg.ath.cx/downloads/misc/libvirt.debug
Offline
I updated libvirt to git-20100125. The crashes are gone, but when I try to install a guest, virtinst crashes with the following output:
Starting install...
ERROR internal error unable to start guest: chardev: opening backend "pty" failed
Domain installation may not have been
successful. If it was, you can restart your domain
by running 'virsh start vzoltan0'; otherwise, please
restart your installation.
ERROR internal error unable to start guest: chardev: opening backend "pty" failed
Traceback (most recent call last):
File "/usr/bin/virt-install", line 943, in <module>
main()
File "/usr/bin/virt-install", line 839, in main
start_time, guest.start_install)
File "/usr/bin/virt-install", line 894, in do_install
dom = install_func(conscb, progresscb, wait=(not wait))
File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 660, in start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 758, in _do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib/python2.6/site-packages/libvirt.py", line 1097, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: internal error unable to start guest: chardev: opening backend "pty" failed
I have tried almost everything, from reverting to older git checkouts and the 0.6.5 stable release to updating virtinst, virtviewer and virt-manager to the latest hg builds. None of this worked, and I can't seem to find anything about this error on google either.
Does anyone have a solution?
Offline
In case anyone else was plagued by this crash, building without libcap-ng seemed to resolve the problem
Offline
great blob! I had the exact same problem as LuckyGee... using libvirt-git without libcap solved all my kvm woes (up until now, that is )
Mat
Offline
great blob! I had the exact same problem as LuckyGee... using libvirt-git without libcap solved all my kvm woes (up until now, that is
)
Mat
Mh, doesn't work for me. Same error: "no kvm driver..."
Offline
LukeGee: Enable qemu "--with-qemu" and disable libcap "--without-capng" in the libvirtd-git PKGBUILD. That worked for me.
Offline
LukeGee: Enable qemu "--with-qemu" and disable libcap "--without-capng" in the libvirtd-git PKGBUILD. That worked for me.
Ah yay, "--with-qemu" was missing. I just built it with "--without-capng".
Now it works for me. Thanks alot!!!
Offline