similar to: virConnectClose

libvirt version: 3.4.0 architecture: x86_64 ubuntu16.04-server hypervisor: kvm,qemu My program use libvirt event , the program is a module(.so) file in cloud application, when unload the module, program will dump in virEventPoolRunOnce call. program frame virInitialize virEventAddTimeOut virEventRunDefaultImpl virConnectXXX virConnectDomainEventRegisterAny ... virConnectDomainEventDeregisterAny

hi, all I do a hotplug detach a network in a thread, because virDomainDetachDeviceFlags maybe asynchronous, so I do like follow: cb_para->cluster_id = info->cluster_id; cb_para->group_id = info->group_id; cb_para->vsys_id = info->vsysid; cb_para->vnf_id = info->vnf_id; cb_para->conn = conn; cb_para->time_out = 20*1000;//20s

libvirt version: 3.4.0 When use libvirt event in program, if I create more than one thread loop call virEventRunDefaultImp(), Is this invocation correct. If correct ,what happen when event occur.is many thread process event? If I invocation virEventRegisterDefault before any hypervisor connect, and invocation virEventRunDefaultImp.Then I connect a hypervisor(qemu) and register some event on

Hey! It seems that if I close a connection while a domain event callback is in progress, I can easily have a crash. Here is a backtrace: #v+ #0 virFree (ptrptr=0x0) at ../../../src/util/viralloc.c:582 save_errno = <optimized out> #1 0x00007fc8328a4ad2 in virObjectEventCallbackListPurgeMarked (cbList=0xadfc30) at ../../../src/conf/object_event.c:282 freecb = <optimized

On 04.03.2016 16:24, Predrag Ivanovic wrote: > Hi. > > Since the update to libvirt-1.3.2, virsh keeps disconnecting from qemu:///session. > Weirdly enough, qemu:///session works fine for root, and qemu:///system works for both the user and the root. > With the same configuration(tarball with files from /etc/libvirt attached), libvirt-1.3.1 works without problems. > > From

Hi. Since the update to libvirt-1.3.2, virsh keeps disconnecting from qemu:///session. Weirdly enough, qemu:///session works fine for root, and qemu:///system works for both the user and the root. With the same configuration(tarball with files from /etc/libvirt attached), libvirt-1.3.1 works without problems. From the virsh debug log(attached): --- grep error virsh.log.1.3.2 2016-03-03

hi, all: I create a vm with six nic, after the vm start, i delete tree nics. all the three nic delete logic will happen in a thread , every nic delete has the following process: int vnf_control_del_network(void *arg) { 。。。。。 call_id = virConnectDomainEventRegisterAny(conn, dom, VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED, VIR_DOMAIN_EVENT_CALLBACK(vnf_control_del_network_cb), cb_para,

On Mon, May 04, 2020 at 09:33:47AM -0700, PGNet Dev wrote: > I've setup for use of modular daemons with systemd sockets, rather than monolithic libvirtd snip > virsh -c xen:///system?socket=/var/run/libvirt/libvirt-sock > error: failed to connect to the hypervisor > error: internal error: Unexpected driver type 'Xen' opened > > What's missing/incorrect in

Author: tha-guest Date: 2006-03-03 18:08:48 +0000 (Fri, 03 Mar 2006) New Revision: 70 Modified: trunk/xen-3.0/debian/changelog trunk/xen-3.0/debian/control trunk/xen-3.0/debian/xen-utils-3.0.postinst Log: The "Sorry for the step back, but I guess it''s more a 2 steps forwards" commit - Added the xen package again, because we believe there is a valid upgrade

Dear All, Please find few minutes from your time and guide us with some pointers if possible. We are facing a libvirtd crash when we are trying to connect to qemu by default TLS transport. i.e libvirt crash when trying to inquiry libvirt version using curl with TLS # virsh -c qemu+tls://localhost/system version error: authentication failed: TLS handshake failed A TLS packet with unexpected

On 4/29/19 5:42 PM, lameventanas@gmail.com wrote: > > > On 29/04/2019 22.01, Michal Privoznik wrote: >> On 4/29/19 1:06 PM, lameventanas@gmail.com wrote: >>> I want to run libvirtd as a special user, and allowing users that belong >>> to a special group to connect via qemu+unix:///system (eg: unix socket). >>> >>> I did everything necessary to

Replaced the previous HostWrapper class with the new HostAgent class, which more closely resembles the style of the ProcessorsAgent class. Deleted the HostWrapper class entirely. Refactored the daemon entry point to reduce the number of methods invoked in order to start or stop the HostAgent instance. Moved the NICWrapper's setupQMFObject method from private to public so that it can be

Dear All, Please find few minutes from your time and guide us with some pointers if possible. We are facing a libvirtd crash when we are trying to connect to qemu by default TLS transport. # virsh -c qemu+tls://localhost/system version error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. error: failed to connect to the hypervisor I used my own CA

I'm setting up for libvirt remote access on a xend host. On the host, xl info | egrep "release|xen_version" release : 5.6.10-24.gde48f93-default xen_version : 4.13.0_12-lp151.700 systemctl --version systemd 234 I've installed rpm -qa libvirt-daemon-xen libvirt-daemon-xen-6.2.0-lp151.890.1.x86_64 libvirtd --version libvirtd (libvirt)

hi, i removed all libvirt things form my system and i installed libvirt-0.9.12 frm my repository. then i installed libvirt-1.1.2 from the source with following commands. ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-xen=yes --with-libxl=yes make make install now its works with XM. but with xl its not working... i attached the corresponding screenshots also. kindly

Processing commands for control at bugs.debian.org: > close 545224 3.4.0-1 Bug #545224 [src:xen] grub-pc: Makes xen-hypervisor-3.2-1-amd64 hang with "early fatal page fault" on boot Bug #516610 [src:xen] xen-hypervisor-3.2-1-amd64: Xen hypervisor does not boot on Core2 Duo CPU P8600 The source 'xen' and version '3.4.0-1' do not appear to match any binary packages

libvirt version: 3.4.0 architecture: x86_64 ubuntu16.04-server hypervisor: kvm,qemu when I want make a memery snapshot for a vm ,and I call virsh save ,but tell me this error: error: Failed to save domain 177 to /datapool/mm.img error: operation failed: domain save job: unexpectedly failed xml configure: <domain type='kvm' id='177'> <name>virt23</name>

Hi all, I registe node device lifecycle event callback function after connect qemu. In the callback function, I printf the event and detail. When I plug a USB into host, and then pull out, but there is nothing happen. The callback was not called. Could you tell me Why? And what dose node device mean? I want to auto-hotplug usb devices by using libvirt. Bellow the call of libvirt: // node

hi, i prepared my xen-4.2.1 document with this mail. kindly refer the below attachment. i installed libvirt 1.1.1 like this it giving the following error: ./autogen.sh --system --with-xen=yes make /daemon/libvirtd -d then i checked with the virsh ->version virsh # version error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to

hi, i found something im my log: (libvirtd.log) i dont know about this. but it may be helpful for you. So i am forwarding this. 2013-09-26 11:43:58.507+0000: 10718: error : virDriverLoadModule:78 : failed to load module /usr/local/lib/libvirt/connection-driver/libvirt_driver_libxl.so /usr/lib/libxenlight.so.2.0: undefined symbol: xs_check_watch 2013-09-26 11:43:58.790+0000: 10729: error :