similar to: [PATCH] Fix memory leak in libxenstore python bindings

Jiri Denemark <jdenemar@redhat.com> writes: > On Fri, Feb 17, 2017 at 12:38:24 +0100, Milan Zamazal wrote: >> Jiri Denemark <jdenemar@redhat.com> writes: >> >> > On Fri, Feb 10, 2017 at 21:50:19 +0100, Milan Zamazal wrote: >> >> Hi, is there a reliable way to find out to what kind of job does the >> >> information returned from

On Wed, Dec 14, 2016 at 4:35 AM, George Dunlap <George.Dunlap at citrix.com> wrote: > > > On Dec 6, 2016, at 4:18 PM, Sandro Bonazzola <sbonazzo at redhat.com> > wrote: > > > > > > > > On Fri, Dec 2, 2016 at 10:28 AM, Jiri Denemark <jdenemar at redhat.com> > wrote: > > Hi all, > > > > I talked to our oVirt developers who

Jiri Denemark <jdenemar@redhat.com> writes: > On Fri, Feb 10, 2017 at 21:50:19 +0100, Milan Zamazal wrote: >> Hi, is there a reliable way to find out to what kind of job does the >> information returned from virDomainGetJobStats or provided in >> VIR_DOMAIN_EVENT_ID_JOB_COMPLETED event callback belong to? > > No, libvirt expects that the caller knows what job it

On Tue, Jan 13, 2015 at 08:49:53AM -0700, Eric Blake wrote: > On 01/13/2015 07:21 AM, Kashyap Chamarthy wrote: [. . .] > > Seems like you're hitting an old bug[1] where 'blockcopy' (or > > 'blockcommit') missed to execute a cleanup routine which destroys a > > reference to the active block operation -- resulting in the error you're > > seeing

ok thanks , but then can we know which all list of feature are supported by QEMU/KVM release. http://www.linux-kvm.org/page/KVM_Features Does not seem to be all corect . On Thu, Feb 16, 2017 at 3:42 PM, Jiri Denemark <jdenemar@redhat.com> wrote: > On Mon, Feb 06, 2017 at 09:51:06 +0530, akhilesh rawat wrote: > > hi , > > > > I am creating Guest by Libvirt tool "

On Fri, Feb 17, 2017 at 12:38:24 +0100, Milan Zamazal wrote: > Jiri Denemark <jdenemar@redhat.com> writes: > > > On Fri, Feb 10, 2017 at 21:50:19 +0100, Milan Zamazal wrote: > >> Hi, is there a reliable way to find out to what kind of job does the > >> information returned from virDomainGetJobStats or provided in > >> VIR_DOMAIN_EVENT_ID_JOB_COMPLETED

As scheduled, libvirt 0.9.0 was tagged and pushed today, it's available from FTP at: ftp://libvirt.org/libvirt/ This is a large release w.r.t. the amount of features and changes, and well worth bumping the middle version number. We are also getting closer to a 1.0.0 release ! Features: - Support cputune cpu usage tuning (Osier Yang and Nikunj A. Dadhania) - Add public APIs for storage

[Starting to move to the development list.] Milan Zamazal <mzamazal@redhat.com> writes: > Jiri Denemark <jdenemar@redhat.com> writes: > >> On Fri, Feb 17, 2017 at 12:38:24 +0100, Milan Zamazal wrote: >>> >>> There are basically two problems: >>> >>> - When the job completion callback is called, I need to distinguish what >>>

Following Dan advice, I decided to not wait for more patches and push the current git head as the release. Let's plan to have another release by this month end with the QEmu debugging and hacking APIs. The release is available as usual at ftp://libvirt.org/libvirt Quite a lot of bug fixes during the two months since 0.8.1, and a few new feature. It also tagged more commits as being

As planned and after most of the clang detected problems got fixed (thanks Eric !) the new release is available at: ftp://libvirt.org/libvirt/ It's a mixed release, it includes a number of improvements as well as many bug fixes and a few new features: Features: - support various persistent domain updates (KAMEZAWA Hiroyuki) - improvements on memory APIs (Taku Izumi) - Add

Jiri Denemark <jdenemar@redhat.com> writes: > On Fri, Dec 07, 2018 at 11:52:38 +0100, Milan Zamazal wrote: >> Hi, some custom CPU models are reported from >> virConnectGetDomainCapabilities as usable='yes' on a physical machine > >> while as usable='no' inside a VM running on the same machine. That's >> not completely surprising. >>

hello , thanks for comments . I tried now with force options for CPU flag which were not supported . Now the command with non fully supported CPU model gets executed , But i am surprised to see that still Guest cpu model is not changed and still same as host cpu model(SAndy Bridge) Why don't i see the model as HAswell now , could you please comment. Command used : virt-install

As planned the new release is available at: ftp://libvirt.org/libvirt/ It is a rather large release with near 400 commits included. From an user point of view the main improvement is likely to be when using migration as various work has been done to extend the protocol and to avoid having the migration command stop other concurrent operations (like virsh list). See below for a number of

On Tue, Dec 11, 2018 at 10:45:12 +0100, Milan Zamazal wrote: > Jiri Denemark <jdenemar@redhat.com> writes: > > > On Fri, Dec 07, 2018 at 11:52:38 +0100, Milan Zamazal wrote: > >> Hi, some custom CPU models are reported from > >> virConnectGetDomainCapabilities as usable='yes' on a physical machine > > > >> while as usable='no'

14.09.2018 15:43, Jiri Denemark пишет: > On Thu, Sep 13, 2018 at 19:37:00 +0400, Dmitry Melekhov wrote: >> >> 13.09.2018 18:57, Jiri Denemark пишет: >>> On Thu, Sep 13, 2018 at 18:38:57 +0400, Dmitry Melekhov wrote: >>>> 13.09.2018 17:47, Jiri Denemark пишет: >>>>> On Thu, Sep 13, 2018 at 10:35:09 +0400, Dmitry Melekhov wrote:

On Fri, Sep 14, 2018 at 16:00:43 +0400, Dmitry Melekhov wrote: > 14.09.2018 15:43, Jiri Denemark пишет: > > On Thu, Sep 13, 2018 at 19:37:00 +0400, Dmitry Melekhov wrote: > >> > >> 13.09.2018 18:57, Jiri Denemark пишет: > >>> On Thu, Sep 13, 2018 at 18:38:57 +0400, Dmitry Melekhov wrote: > >>>> 13.09.2018 17:47, Jiri Denemark пишет: >

13.09.2018 18:57, Jiri Denemark пишет: > On Thu, Sep 13, 2018 at 18:38:57 +0400, Dmitry Melekhov wrote: >> >> 13.09.2018 17:47, Jiri Denemark пишет: >>> On Thu, Sep 13, 2018 at 10:35:09 +0400, Dmitry Melekhov wrote: >>>> After some mistakes yesterday we ( me and my colleague ) think that it >>>> will be wise for libvirt to check config file existence

On Thu, Sep 13, 2018 at 19:37:00 +0400, Dmitry Melekhov wrote: > > > 13.09.2018 18:57, Jiri Denemark пишет: > > On Thu, Sep 13, 2018 at 18:38:57 +0400, Dmitry Melekhov wrote: > >> > >> 13.09.2018 17:47, Jiri Denemark пишет: > >>> On Thu, Sep 13, 2018 at 10:35:09 +0400, Dmitry Melekhov wrote: > >>>> After some mistakes yesterday we ( me

13.09.2018 17:47, Jiri Denemark пишет: > On Thu, Sep 13, 2018 at 10:35:09 +0400, Dmitry Melekhov wrote: >> After some mistakes yesterday we ( me and my colleague ) think that it >> will be wise for libvirt to check config file existence on remote side > Which config file? > VM config file, namely qemu. We forgot to mount shared storage (namely gluster volume), on which we

On Thu, Jan 14, 2016 at 03:54:29PM +0000, Richard W.M. Jones wrote: > > FYI I'm testing the attached patch (written by Jiri Denemark). The > tests usually take a day to run. Yes this patch appears to fix all the problems. Can it be applied to libvirt? Rich. > diff --git i/src/security/security_dac.c w/src/security/security_dac.c > index 80709fe..378b922 100644 > ---