Bugzilla – Bug 405767
Floating point exception when local connection to Xen with Virt-manager
Last modified: 2008-07-03 23:49:42 UTC
linux-o2zd:/home/admin # virt-manager --no-fork Floating point exception strace -p 6477 [...] read(18, "e", 1) = 1 read(18, "\r", 1) = 1 read(18, "\n", 1) = 1 read(18, "C", 1) = 1 read(18, "a", 1) = 1 read(18, "c", 1) = 1 read(18, "h", 1) = 1 read(18, "e", 1) = 1 read(18, "-", 1) = 1 read(18, "c", 1) = 1 read(18, "o", 1) = 1 read(18, "n", 1) = 1 read(18, "t", 1) = 1 read(18, "r", 1) = 1 read(18, "o", 1) = 1 read(18, "l", 1) = 1 read(18, ":", 1) = 1 read(18, " ", 1) = 1 read(18, "n", 1) = 1 read(18, "o", 1) = 1 read(18, "-", 1) = 1 read(18, "c", 1) = 1 read(18, "a", 1) = 1 read(18, "c", 1) = 1 read(18, "h", 1) = 1 read(18, "e", 1) = 1 read(18, "\r", 1) = 1 read(18, "\n", 1) = 1 read(18, "\r", 1) = 1 read(18, "\n", 1) = 1 read(18, "(node (system Linux) (host linux"..., 905) = 905 close(18) = 0 --- SIGFPE (Floating point exception) @ 0 (0) --- Process 6477 detached I already experienced this problem on Debian Etch with backported Xen/Libvirt/Virt-manager and this problem is a Libvirt 0.4.0 specific bug. Upgrade to Libvirt 0.4.1 or 0.4.2 will correct this problem.
I have run into the same problem. How do I get the newer code?
The Libvirt sources are available here : http://libvirt.org/sources The latest stable release seems to be the 0.4.4. It could be also great if the last version of Virt-manager (0.5.4, released march 10th, 2008) should be included in OpenSUSE 11.0 (instead of the 0.5.3)... The sources can be found here : http://virt-manager.org/download.html
The home:syntron/openSUSE_11.0 repository (http://download.opensuse.org/repositories/home:/syntron/openSUSE_11.0) seems to contain Libvirt 0.4.4 but when I try to install it I get the following error message : "nothing provides libgnutls.so.13()(64bit) needed by libvirt-0.4.4-12.1.x86_64".
I downgraded Libvirt to 0.3.0-30.5 (the last update from OpenSUSE 10.3) and Virt-manager seems to run successfully. So I can confirm the problem comes from Libvirt 0.4.0.
Yes, we have isolated the offending call in libvirt and we'll be looking at it next week. See bug #398932 for more details... *** This bug has been marked as a duplicate of bug 398932 ***
Removing "resolved duplicate" because duplicate bug is internal.
Reopening bug.
*** This bug has been marked as a duplicate of bug 398932 ***