Jan 06 10:27:20 Osuse13 libvirtd[1396]: this function is not supported by the connection driver: virDomainGetMetadata
Jan 06 10:27:20 Osuse13 libvirtd[1396]: this function is not supported by the connection driver: virDomainMemoryStats
Jan 06 10:27:20 Osuse13 kernel: libvirtd[1429]: segfault at ffffffffffffffff ip 00007fb2e1214614 sp 00007fb2da2440d8 error 7 in libc-2.19.so[7f
Jan 06 10:27:20 Osuse13 libvirtd[4655]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_vbox_network.so not accessible
Jan 06 10:27:20 Osuse13 libvirtd[4655]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_vbox_storage.so not accessible
Jan 06 10:27:20 Osuse13 libvirtd[4655]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so not accessible
Jan 06 10:27:20 Osuse13 libvirtd[4655]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not accessible
Jan 06 10:27:20 Osuse13 libvirtd[4655]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_uml.so not accessible
Jan 06 10:27:20 Osuse13 libvirtd[4655]: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_vbox.so not accessible
Jan 06 10:27:20 Osuse13 libvirtd[4655]: no connection driver available for qemu:///system
Something seems to have caused your virtualization services to come to a screeching halt.
Have you tried rebooting and re-trying to install a new Guest?
Which packages are installed as far as your virtualization environment is concerned? Do a rpm -qa | egrep ‘libvirt|xen’ and check for the installed drivers (if any). As far as I can tell from the error log it seems that none of the drivers necessary for virtualization are installed. In YaST, enter libvirt-daemon as a search term and try to select anything that you may get - both the various daemons and their respective drivers.
[QUOTE=tsu2;2687795]Something seems to have caused your virtualization services to come to a screeching halt.
Have you tried rebooting and re-trying to install a new Guest?
Occurred to me…
If the error occurred after trying to read the DVD install source, this might be a bug I discovered many versions ago in libvirt but after it was fixed raised its ugly head again once again later. If the bug re-appeared once, maybe it showed up again.
Verify…
The path to the install media is exactly correct. If you don’t know whether it’s correct, copy and paste the path here.
IIRC the first time I found this bug, it repeated a string twice in the path, making the path invalid.
But, the entire path should be checked.
I am Trying to create new VM, as I was used to in opensuse 12.3, i.e.
I go with GUI -> Virtual Machine Manager -> Vm-install
disk paths are specified as:
phy:/dev/sr0
file:/var/lib/libvirt/images/opensuse13-1/disk0.raw
then after all configurations are specified, hit OK, then small window with title “Creating the Virtual Machine”, with progress bar "Please wait … Preparing to start the installation "
and then ERROR “End of file while reading data: Input/outpu error”.
Where should I check the path ???
I did twice, one as paravirtualized, one as full virtualized.
The Same error appears.
in the journalctl I found “libvirtd: … failed” listings. Unfortunately I don’t understand enough what does it mean.
Please help,
thank you for previous assistance
Jan 19 15:19:41 Osuse13 libvirtd[1528]: libvirtd: libxl_fork.c:350: sigchld_installhandler_core: Assertion ((void)"application must negotiate with libxl about SIGCHLD", !(sigchld_saved_action.sa_flags & 4) && (sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 0) || sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 1)))' failed. Jan 19 15:19:42 Osuse13 libvirtd[3313]: Failed to query host NUMA topology, disabling NUMA capabilities Jan 19 15:19:42 Osuse13 libvirtd[3313]: Failed to get host CPU Jan 19 15:19:42 Osuse13 libvirtd[3313]: Failed to query host NUMA topology, disabling NUMA capabilities Jan 19 15:21:02 Osuse13 libvirtd[3313]: this function is not supported by the connection driver: virDomainMemoryStats Jan 19 15:21:12 Osuse13 libvirtd[3313]: libvirtd: libxl_fork.c:350: sigchld_installhandler_core: Assertion ((void)“application must negotiate with libxl about SIGCHLD”, !(sigchld_saved_action.sa_flags & 4) && (sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 0) || sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 1)))’ failed.
Jan 19 15:21:12 Osuse13 libvirtd[3398]: Failed to query host NUMA topology, disabling NUMA capabilities
Jan 19 15:21:12 Osuse13 libvirtd[3398]: Failed to get host CPU
Jan 19 15:21:12 Osuse13 libvirtd[3398]: Failed to query host NUMA topology, disabling NUMA capabilities
Jan 19 15:21:33 Osuse13 libvirtd[3398]: this function is not supported by the connection driver: virDomainListAllSnapshots
Jan 19 15:25:03 Osuse13 kernel: SFW2-INext-DROP-DEFLT IN=br0 OUT= MAC= SRC=fe80:0000:0000:0000:c634:6bff:feb8:1110 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
Jan 19 15:30:01 Osuse13 cron[3467]: pam_unix(crond:session): session opened for user root by (uid=0)
Jan 19 15:30:01 Osuse13 CRON[3467]: pam_unix(crond:session): session closed for user root
Jan 19 15:31:19 Osuse13 libvirtd[3398]: libvirtd: libxl_fork.c:350: sigchld_installhandler_core: Assertion ((void)"application must negotiate with libxl about SIGCHLD", !(sigchld_saved_action.sa_flags & 4) && (sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 0) || sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 1)))' failed. Jan 19 15:31:19 Osuse13 libvirtd[3495]: Failed to query host NUMA topology, disabling NUMA capabilities Jan 19 15:31:19 Osuse13 libvirtd[3495]: Failed to get host CPU Jan 19 15:31:19 Osuse13 libvirtd[3495]: Failed to query host NUMA topology, disabling NUMA capabilities Jan 19 15:38:32 Osuse13 libvirtd[3495]: libvirtd: libxl_fork.c:350: sigchld_installhandler_core: Assertion ((void)“application must negotiate with libxl about SIGCHLD”, !(sigchld_saved_action.sa_flags & 4) && (sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 0) || sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 1)))’ failed.
Jan 19 15:38:33 Osuse13 libvirtd[3825]: Failed to query host NUMA topology, disabling NUMA capabilities
Jan 19 15:38:33 Osuse13 libvirtd[3825]: Failed to get host CPU
Jan 19 15:38:33 Osuse13 libvirtd[3825]: Failed to query host NUMA topology, disabling NUMA capabilities
Jan 19 15:42:07 Osuse13 kernel: SFW2-INext-DROP-DEFLT IN=br0 OUT= MAC= SRC=fe80:0000:0000:0000:c634:6bff:feb8:1110 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
Although the error is thrown and the connection of Virtual Machine Manager is lost,
when I reconnect the Virtual Machine Manager I can see and edit virtual Machine details.
However VM guest is unable to start with the deiscribed error.
When I set in the libvirtd.conf:
log_level = 1
log_outputs=“1:syslog:libvirtd”
I have lot of debug output lines but only 3 with “error” designation in the journalctl output
Jan 26 11:14:22 Osuse13 libvirtd[1618]: 1665: error : virDomainGetMetadata:10305 : this function is not supported by the connection driver: virDomainGetMetadata
Jan 26 11:14:22 Osuse13 libvirtd[1618]: 1667: error : virDomainMemoryStats:8277 : this function is not supported by the connection driver: virDomainMemoryStats
…
Jan 26 11:14:40 Osuse13 libvirtd[2689]: 2689: error : virNetSocketReadWire:1571 : End of file while reading data: Input/output error
My previous suggestion to check the virtual cdrom path during installation would be relevant only if you had a problem installing the VM in the first place, and just before you click the button to verify your install and begin installing, the install source path should be obvious.
Since you might be saying the install might have run and is now trying to start, an alternative way to check this issue might be to look at the virtual disk properties and inspect the size (of course from the Host). If the file is only a few KB or MB, then the install didn’t really work and you can look for the virtual cdrom path again. But, if the file is well over 500MB (likely over 1GIG if you installed a Desktop), then source files were likely read and your install wrote to the virtual disk.
