Displaying 20 results from an estimated 800 matches similar to: "event handler"
2013 Oct 14
2
Re: event handler
Michal Privoznik писал 2013-10-14 08:48:
> On 14.10.2013 02:42, Alexandr wrote:
>> good day to all.
>> i still have not solved my problem with event handling.
>> currently i have following code
>>
>>
>> void libvirt_eventloop_thr_func()
>> {
>> while(true) //TODO: stop somehow on exit
>> {
>>
2013 Oct 14
2
Re: event handler
Michal Privoznik писал 2013-10-14 11:39:
> On 14.10.2013 10:33, Alexandr wrote:
>> Michal Privoznik писал 2013-10-14 08:48:
>>> On 14.10.2013 02:42, Alexandr wrote:
>>>> good day to all.
>>>> i still have not solved my problem with event handling.
>>>> currently i have following code
>>>>
>>>>
>>>> void
2013 Aug 22
1
Re: virConnectDomainEventRegisterAny problem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
21.08.2013 12:58, Alexandr пишет:
> 21.08.2013 12:39, Daniel P. Berrange пишет:
>> On Wed, Aug 21, 2013 at 12:36:06PM +0300, Alexandr wrote:
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>
>>> 21.08.2013 09:46, Alexandr пишет:
>>>> 21.08.2013 09:32, Martin Kletzander пишет:
>>>>> On
2013 Aug 21
2
Re: virConnectDomainEventRegisterAny problem
On Wed, Aug 21, 2013 at 12:36:06PM +0300, Alexandr wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 21.08.2013 09:46, Alexandr пишет:
> > 21.08.2013 09:32, Martin Kletzander пишет:
> >> On Wed 21 Aug 2013 01:03:37 AM CEST, Alexandr wrote:
> >>>
> >>> good day. i trying to make callback function for
> >>>
2013 Oct 14
0
Re: event handler
On 14.10.2013 10:57, Alexandr wrote:
> Michal Privoznik писал 2013-10-14 11:39:
>> On 14.10.2013 10:33, Alexandr wrote:
>>> Michal Privoznik писал 2013-10-14 08:48:
>>>> On 14.10.2013 02:42, Alexandr wrote:
>>>>> good day to all.
>>>>> i still have not solved my problem with event handling.
>>>>> currently i have following
2013 Oct 14
0
Re: event handler
On 14.10.2013 10:33, Alexandr wrote:
> Michal Privoznik писал 2013-10-14 08:48:
>> On 14.10.2013 02:42, Alexandr wrote:
>>> good day to all.
>>> i still have not solved my problem with event handling.
>>> currently i have following code
>>>
>>>
>>> void libvirt_eventloop_thr_func()
>>> {
>>> while(true) //TODO:
2013 Oct 14
0
Re: event handler
On 14.10.2013 02:42, Alexandr wrote:
> good day to all.
> i still have not solved my problem with event handling.
> currently i have following code
>
>
> void libvirt_eventloop_thr_func()
> {
> while(true) //TODO: stop somehow on exit
> {
> if(virEventRunDefaultImpl() < 0)
> {
> virErrorPtr err = virGetLastError();
>
2013 Jul 08
2
Re: deadlock on connection loosing
On 07.07.2013 01:53, Александр wrote:
> В письме от Воскресенье, 30-июн-2013 03:41:37 пользователь Александр написал:
>> В письме от Вторник, 25-июн-2013 11:47:10 пользователь Michal Privoznik
....
>
> i have found source of problem, my code looks like this:
>
> int count = virConnectListAllDomains(connection, NULL, 0);
> ....
> domain = virDomainDefineXML(connection,
2013 Aug 20
2
virConnectDomainEventRegisterAny problem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
good day. i trying to make callback function for
VIR_DOMAIN_EVENT_ID_LIFECYCLE, i have successfully registering callback,
but it never called, i need to know when domain started, stopped or
crashed, i have write following code
static int domain_event_handler(virConnectPtr conn, virDomainPtr dom,
int event, int detail, void * opaque)
{
2013 Aug 21
2
Re: virConnectDomainEventRegisterAny problem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
21.08.2013 09:32, Martin Kletzander пишет:
> On Wed 21 Aug 2013 01:03:37 AM CEST, Alexandr wrote:
>>
>> good day. i trying to make callback function for
>> VIR_DOMAIN_EVENT_ID_LIFECYCLE, i have successfully registering
>> callback, but it never called, i need to know when domain
>> started, stopped or crashed, i have
2020 Apr 02
1
can libvirt.so use jemalloc to manage mem ?
HI, all
My daemon exists a libvirt API call:
virEventRegisterDefaultImpl();
once I called the virEventRegisterDefaultImpl() ,must be core ,the bt stack is:
(gdb) bt
#0 free (ptr=0x1) at include/jemalloc/internal/arena.h:652
#1 0x00007f57690a488a in virFree () from /lib64/libvirt.so.0
#2 0x00007f57690c3562 in virResetError () from /lib64/libvirt.so.0
#3 0x00007f57690c49ad in
2020 Jan 10
5
[PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
libguestfs usually needs qemu. However it only requires an emulator
for the same architecture, not for all architectures.
libvirt-daemon-kvm pulls in qemu which pulls in emulators for all
architectures, as well as a bunch of other stuff we don't need at all
like network interface support and nwfilter.
There are no Fedora TCG-only arches, so drop the conditional section.
I also made support
2013 Feb 28
7
[PATCH 0/7] Fix SELinux security contexts so we can access shared disks (RHBZ#912499).
https://bugzilla.redhat.com/show_bug.cgi?id=912499
(especially comments 7 & 10)
This patch set is the final fix so that we can access disks in use by
other guests when SELinux and sVirt are enabled.
Previously such disks were inaccessible because sVirt labels the disks
with a random SELinux label to prevent other instances of qemu from
being able to read them. So naturally the libguestfs
2016 Jan 19
2
[PATCH libguestfs v3] lib: Handle slow USB devices more gracefully.
Libvirt has a fixed 15 second timeout for qemu to exit. If qemu is
writing to a slow USB key, it can hang (in D state) for much longer
than this - many minutes usually.
The solution is to check specifically for the libvirt EBUSY error when
this happens, and retry the virDomainDestroyFlags operation
(indefinitely).
See also the description here:
2016 Sep 20
1
[PATCH] libvirt: read disk paths from pools (RHBZ#1366049)
A disk of type 'volume' is stored as
<source pool='pool_name' volume='volume_name'/>
and its real location is inside the 'volume_name', as 'pool_name': in
this case, query libvirt for the actual path of the specified volume in
the specified pool.
Adjust the code so that:
- for_each_disk gets the virConnectPtr, needed to do operations with
libvirt
2014 Apr 01
3
set keep alive
Can anyone explain what is happening.
After call
virConnectOpen
virEventRegisterDefaultImpl()
call virConnectSetKeepAlive returns
VirtError(1): internal error: the caller doesn't
support keepalive protocol; perhaps it's missing
event loop implementation,
but the next call this sequence of commands returns success.
Why virConnectSetKeepAlive not work right the first time?
--
Fl at sh
2013 Jun 24
3
deadlock on connection loosing
libvirtd will lock if for example kill programm which established connection,
only sigkill + restart helps., to reproduce:
virConnectPtr libvirt_connection = virConnectOpen("qemu:///system");
if(libvirt_connection == NULL)
{
std::cout<<"failed to connect to qemu:///system\n";
exit(-1);
}
exit(0);
2013 Jul 08
0
Re: deadlock on connection loosing
В письме от Понедельник, 08-июл-2013 14:39:57 Вы написали:
> On 07.07.2013 01:53, Александр wrote:
> > В письме от Воскресенье, 30-июн-2013 03:41:37 пользователь Александр
написал:
> >> В письме от Вторник, 25-июн-2013 11:47:10 пользователь Michal Privoznik
>
> ....
>
> > i have found source of problem, my code looks like this:
> >
> > int count =
2016 Sep 22
1
[PATCH v2] libvirt: read disk paths from pools (RHBZ#1366049)
A disk of type 'volume' is stored as
<source pool='pool_name' volume='volume_name'/>
and its real location is inside the 'volume_name', as 'pool_name': in
this case, query libvirt for the actual path of the specified volume in
the specified pool.
Adjust the code so that:
- for_each_disk gets the virConnectPtr, needed to do operations with
libvirt
2016 Nov 16
3
[PATCH 1/2] libvirt: un-duplicate XPath code
Move the checks for empty xmlXPathObjectPtr, and for extracting the
result string out of it, to a new helper functions.
This is just code motion, there should be no behaviour changes.
---
src/libvirt-domain.c | 122 +++++++++++++++++++++------------------------------
1 file changed, 50 insertions(+), 72 deletions(-)
diff --git a/src/libvirt-domain.c b/src/libvirt-domain.c
index 4d4142d..baab307