similar to: Compile error on centos 7 : undefined reference to `virConnectNetworkEventRegisterAnyCheckACL'

> Thanks for the report. That is disabling quite a lot of drivers (what > is still left, lxc?), so it's a combination that has not gotten a lot of > testing. I'll definitely look at fixing it before 1.2.8 is released, > although it may miss release candidate 0. It's no problem of configure options. Simple ./configure result: configure: configure: Configuration summary

Hello I apologize in advance for my English. I compiled the new version of libvirt 1.2.8 on an environment Development Linux from Scratch with the following configure: configure: Configuration summary configure: ===================== configure: configure: Drivers configure: configure: Xen: no configure: QEMU: yes configure: UML: yes configure: OpenVZ: no configure: VMware:

Hi all: Unable to install libvirt v5.5.0 correctly through the source code which clone from git. The error message is shown below. libtool: install: (cd /home/libvirt/src; /bin/sh /home/libvirt/libtool --silent --tag CC --mode=relink gcc -std=gnu99 -I/usr/include/libxml2 -fno-common -W -Waddress -Waggressive-loop-optimizations -Wall -Wattributes -Wbad-function-cast -Wbuiltin-macro-redefined

Thanks Guido, unfortunately no luck: root@<server>:~/debian# grep DEB_CONFIGURE_EXTRA_ARGS * grep: apparmor: Is a directory grep: patches: Is a directory grep: source: Is a directory root@<server>:~/debian# root@<server>:~/debian# root@<server>:~/debian# root@<server>:~/debian# grep DEB_CONFIGURE_EXTRA_ARGS */* root@<server>:~/debian#

On Thu, Sep 24, 2020 at 2:58 PM Ján Tomko <jtomko@redhat.com> wrote: > On a Thursday in 2020, Wei Wang wrote: > >Seems it didn't appear on the mailing list, resent it. > > > > Hi folks, > > > >I'm trying to build libvirt using meson with the latest upstream libvirt, > >but the compilation fails: > >(followed on

On 08/26/2014 05:37 AM, mxs kolo wrote: >> Thanks for the report. That is disabling quite a lot of drivers (what >> is still left, lxc?), so it's a combination that has not gotten a lot of >> testing. I'll definitely look at fixing it before 1.2.8 is released, >> although it may miss release candidate 0. > It's no problem of configure options. Simple

On 08/26/2014 03:41 AM, mxs kolo wrote: > Hi all > > Centos 7.0.1406, 3.10.0-123.el7.x86_64 > Configure libvirt-1.2.7 as: > ./configure --prefix=/usr --with-xen=no --with-qemu=no > --with-openvz=no --with-vmware=no --with-esx=no --with-parallels=no > --with-bhyve=no --with-uml=no --with-vbox=no --with-selinux=no > make Thanks for the report. That is disabling quite a

> So maybe we have a bug where the build depends on pre-installed files, > rather than building properly from the tarball. Good thing it's easy to > make a virgin VM to test this theory. Like I said, I'll try and > reproduce and fix this, but it may be a couple days. Some news. I get libvirt-1.2.8-rc1.tar.gz and successfully build it on my "problem" node, without

On Wed, Aug 08, 2018 at 10:58:50AM +0200, Holger Schranz wrote: > checking for JANSSON... no This is the problem. In 4.6.0 we just switched to using JANSSOn instead of yajl for JSON parsing. Your host doesn't have the development headers installed for jansson.... > configure: > configure: Configuration summary > configure: ===================== > configure: > configure:

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..0943bf305 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-M UI,

hello, I am getting such error: libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp 00007f4930711740 error 4 in libvirt.so.0.2000.0[7f4940678000+353000] when I am trying to start VM with graphic spice/vnc console - in headless mode(without graphic console) it is running I noticed this after update oVirt 4.0 to oVirt 4.1 however I noticed that also libvirtd and related packages were upgraded

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...

Hello, I am currently working on Redhat 6 - Kernel 2.6.32-358.el6.x86_64. It has by default libvirt 0.10.2. I wanted version 1.2.7. So I downloaded this and libvirt-1.2.7.tar.gz and I followed the following steps: 1. ./configure (with its default settings) 2. make 3. make install Currently, the installation is in: /usr/local and the source tree is in /export/home/libvirt. I stopped the

Hi, I am installing OpenStack on Red Hat 7.5. For Nova compute component, I choose libvirt and Xen. However, I am running into some problems. It seems libvirt is unable to communicate with Xen. Xen installation: I installed Xen410 using "Xen make easy" https://xen.crc.id.au/support/guides/install/. Here is a list of packages installed and verification that Xen is running. #

hello, I attached core dump - not sure if it was what you have asked for I am rather just admin not developer :) Regards, Rafal Wojciechowski W dniu 20.04.2017 o 16:44, Pavel Hrdina pisze: > On Thu, Apr 20, 2017 at 07:36:42AM +0200, Rafał Wojciechowski wrote: >> hello, >> >> I am getting such error: >> libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp

On Fri, Sep 25, 2020 at 10:03 AM Wei Wang <weiwangcloud2020@gmail.com> wrote: > On Thu, Sep 24, 2020 at 2:58 PM Ján Tomko <jtomko@redhat.com> wrote: > >> On a Thursday in 2020, Wei Wang wrote: >> >Seems it didn't appear on the mailing list, resent it. >> > >> > Hi folks, >> > >> >I'm trying to build libvirt using meson

With the -Wformat-truncation warnings fixed, finish the job started in commit a61ddb4393ad ("drm: enable (most) W=1 warnings by default across the subsystem"), and enable that warning too. Signed-off-by: Jani Nikula <jani.nikula at intel.com> --- Gut feeling says there are more issues, and my configs just don't catch them all, but let's see what the build bots have to