similar to: compile error libvirt-python 4.5.0 - error: unknown type name ?virNWFilterBindingPtr?

Displaying 20 results from an estimated 200 matches similar to: "compile error libvirt-python 4.5.0 - error: unknown type name ?virNWFilterBindingPtr?"

2018 Jul 09
0
Re: compile error libvirt-python 4.5.0 - error: unknown type name ?virNWFilterBindingPtr?
On Sat, Jul 07, 2018 at 09:34:27PM +0200, Holger Schranz wrote: > Hello, > > I have tried to upgrade libvirt / libvort-python from 4.4.0 to 4.5.0 [snip] > -I/usr/include/python2.7 -c libvirt-override.c -o > build/temp.linux-x86_64-2.7/libvirt-override.o > In file included from libvirt-override.c:24:0: > typewrappers.h:114:5: error: unknown type name ?virNWFilterBindingPtr?
2010 Jul 08
2
Bug#588477: network-bridge: start: 95 sec sleep/bridge without a default gateway
Package: xen-utils-common Version: 4.0.0-1 Severity: normal Tags: patch do_ifup() in network-bridge exits badly, if the interface doesn't have a default gateway. Since it's wrapped in xen's locking script it causes it to be retied 100 times and sleep for 95 seconds before it continues. In my setup this amounts to: 16 vlans without a default gateway * 95 secs / bridge = 25 minutes
2012 Jul 09
3
Bug#588477: [PATCH] hotplug: network-bridge: fix for interfaces with no gateway
# HG changeset patch # User Ian Campbell <ian.campbell at citrix.com> # Date 1341877305 -3600 # Node ID 310aa4c07d02168234a36e113a76d0d4eef373a7 # Parent 1d33f934dd675a1b91d2d4e0fa2d2a873a8debf5 hotplug: network-bridge: fix for interfaces with no gateway This comes from an old Debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588477 which refers to
2014 May 13
1
strange and annoying messages from lib-virtd
Hi, Since a few weeks I'm getting lot of messages in syslog in FC20 sent by libvirt. I've tried to find the reason using our best friend, but all I can find is some kind of bug related to CPU feature reporting. I'm not really interested what is the reason of the message (I'm sure it will be fixed in an upcoming release), but I would like to get rid of these annoying messages
2010 Nov 24
18
System reboots after "Scrubbing free RAM" Xen 4.0.1 linux 2.6.37-rc3
Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,
2010 Nov 24
18
System reboots after "Scrubbing free RAM" Xen 4.0.1 linux 2.6.37-rc3
Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,
2017 Dec 23
2
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
Hello, thanks for the information. Please let me ask: If understand correctly this issue occoured and reported in 3.9? And the fix is for 3.11 or 4.0? Best regards Holger Am 22.12.2017 um 22:27 schrieb Jim Fehlig: > On 12/22/2017 02:21 AM, Holger Schranz wrote: >> Thread 1 (Thread 0x7f0d525ab700 (LWP 10729)): >> #0  virStorageFileReportBrokenChain (errcode=2, >>
2017 Nov 14
2
Re: Urgent: virsh - change-media run into a promptly close of libvirt
Hi Daniel, here are any informations. A little bit strange, coredumpctl showthe libvirtd. coredumpctl dump libvirt and info libvirt  no information. Best regards Holger -------------------------------------------------------------------------- etcsvms5:/var/adm # coredumpctl TIME                            PID   UID   GID SIG PRESENT EXE Tue 2017-11-07 16:22:57 CET     485     0     0  11
2017 Nov 14
2
Urgent: virsh - change-media run into a promptly close of libvirt
Hello, I use the virsh change-media command and since the combination of: etcsvms5:/kvm/CS8400/M1 # virsh version Compiled against library: libvirt 3.9.0 Using library: libvirt 3.9.0 Using API: QEMU 3.9.0 Running hypervisor: QEMU 2.10.1 etcsvms5:/kvm/CS8400/M1 # I got the following problem: ---------------------- etcsvms5:/kvm/CS8400/M1 # virsh change-media S5VCS84M1-VLP0 hdc --eject
2018 Aug 08
3
Re: LIBVIRT-4.6.0 can't work with QEMU 3.0.0
2016 Mar 14
1
Re: [help] How to modify the vgamem value ?
On Mon, Mar 14, 2016 at 09:41:36AM +0100, Holger Schranz wrote: > Hi Luo, > > the vgamem is limited inside. Myself, I use QEMU 2.5/Virgil3D to expand > the vgamem. It's not limited and can be modified inside the xml, the only limitation is that the value has to be a power of 2 and for QXL the value must be at least 1024. There is an exception, qemu can and in some cases updates
2017 Dec 23
1
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
On 12/23/2017 10:20 AM, Holger Schranz wrote: > Sorry for an additional question: > > In the bug report where Jim was wrote in his answer: > https://libvirt.org/git/?p=libvirt.git;a=commit;h=2d07f1f0ebd44b0348daa61afa0de34f3f838c22 > > is a pointer to the report: > https://bugzilla.redhat.com/show_bug.cgi?id=1522682 > > In this report the fixed version is:
2018 Aug 08
2
LIBVIRT-4.6.0 can't work with QEMU 3.0.0
2018 Aug 08
1
Re: LIBVIRT-4.6.0 can't work with QEMU 3.0.0
On Wed, Aug 08, 2018 at 10:06:12 +0100, Daniel Berrange wrote: > 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.... > > > >
2016 Mar 14
2
[help] How to modify the vgamem value ?
Dear everyone Do you know how to modify vgamem value in the .xml file ? such as :<video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/> // from instance-0000015e.xml <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/</video> I
2017 Nov 15
2
Re: Urgent: virsh - change-media run into a promptly close of libvirt
On Tue, Nov 14, 2017 at 07:19:01PM +0100, Holger Schranz wrote: > Ups ... my fault ... > > libvirtd instead libvirt .... > > > etcsvms5:/var/lib/systemd/coredump # coredumpctl info libvirtd >            PID: 10177 (libvirtd) >            UID: 0 (root) >            GID: 0 (root) >         Signal: 11 (SEGV) >      Timestamp: Tue 2017-11-14 10:11:32 CET (9h ago)
2017 Nov 15
1
Re: Urgent: virsh - change-media run into a promptly close of libvirt
On 11/15/2017 06:54 AM, Holger Schranz wrote: > Thread 1 (Thread 0x7f4a069cc700 (LWP 10178)): > #0 0x00007f49ff969170 in qemuDomainChangeEjectableMedia ( > driver=driver@entry=0x7f49f841b700, vm=vm@entry=0x7f49ec02fbd0, > disk=disk@entry=0x7f49ec0375d0, newsrc=0x7f49e8014d10, force=force@entry=false) > at qemu/qemu_hotplug.c:303 This is fixed in current upstream by
2017 Dec 22
2
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
Hi Daniel, sorry. Here the requested stack trace. Best regards Holger ===================================================================================== Thread 18 (Thread 0x7f0d495e0700 (LWP 10742)): #0  0x00007f0d55e690bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 No symbol table info available. #1  0x00007f0d5892176a in virCondWait (c=c@entry=0x5557f238db28,
2017 Dec 22
2
[BUG] Not exiting media forced a promptly close of libvirt 3.10
Hello, In the .xml file I use a media which is no longer available. In the past, I got the information media not available and the creation of the VM was stopped - O.k. behavior. Since 3.10 the libvirtd stopped promptly and all open consoles windows and the virt-manager closed promptly. For diagnose: etcsvms1:/kvm/CS8200/M5 # coredumpctl TIME PID UID GID SIG
2012 Dec 08
0
unicorn 4.5.0 (final) - check_client_connection option
Changes: The new check_client_connection option allows unicorn to detect most disconnected local clients before potentially expensive application processing begins. This feature is useful for applications experiencing spikes of traffic leading to undesirable queue times, as clients will disconnect (and perhaps even retry, compounding the problem) before unicorn can even start processing the