- Devel - libvirt List Archives

[libvirt] [PATCH] Fix migration in xend driver
by Jim Fehlig 12 Jan '10

12 Jan '10

Upstream xen has changed parameters to the migration operation several times over the past 18 months. Changeset 17553 removed the resouce parameter, Changesets 17709, 17753, and 20326 added ssl, node, and change_home_server parameters respectively. Fortunately, testing has revealed that xend will fail the operation if a parameter is missing but happily honor it if unknown parameters are provided. Thus all currently supported parameters can be provided, satisfying current xend but not regressing older versions. --- src/xen/xend_internal.c | 14 ++++++++++---- 1 files changed, 10 insertions(+), 4 deletions(-) diff --git a/src/xen/xend_internal.c b/src/xen/xend_internal.c index be033f5..d9bfa15 100644 --- a/src/xen/xend_internal.c +++ b/src/xen/xend_internal.c @@ -4553,15 +4553,21 @@ xenDaemonDomainMigratePerform (virDomainPtr domain, DEBUG("hostname = %s, port = %s", hostname, port); - /* Make the call. */ + /* Make the call. + * NB: xend will fail the operation if any parameters are + * missing but happily accept unknown parameters. This works + * to our advantage since all parameters supported and required + * by current xend can be included without breaking older xend. + */ ret = xend_op (domain->conn, domain->name, "op", "migrate", "destination", hostname, "live", live, "port", port, - "node", "-1", - "ssl", "0", - "resource", "0", /* required, xend ignores it */ + "node", "-1", /* xen-unstable c/s 17753 */ + "ssl", "0", /* xen-unstable c/s 17709 */ + "change_home_server", "0", /* xen-unstable c/s 20326 */ + "resource", "0", /* removed by xen-unstable c/s 17553 */ NULL); VIR_FREE (hostname); -- 1.6.0.2

2 1

[libvirt] Start external programm on network-setup
by Dominik Bruhn 12 Jan '10

12 Jan '10

Hy, im using libvirt-bin on debian and configured the network of libvirt to be a standalone bridge. Is there a possibility to run a program after the bridge has successfully and completly set up by libvirtd? I would like to restart shorewall (a firewall) when the bridge is set up to activate MASQ and DNAT and other policies which I need. I would also like to start my own configured dnsmasq when the interface is up (can't start it realier because it has to bind to the interface). I hope thats the right place to ask such a question, if not, please direct me. Thanks for the help -- Dominik mailto: dominik(a)dbruhn.de

2 1

[libvirt] Problem: cannot make libvirtd listen to TCP sockets
by Motiejus Jakštys 12 Jan '10

12 Jan '10

Hello, I don't know if I am writing to the proper place, but I've been struggling quite a long time with connecting to libvirtd. Any information would help. My goal is to start remote tcp connection (afterwards - tls, but later) and connect to the libvirtd. http://libvirt.org/uri.html#URI_remote There are some nitoces when starting libvirtd: -~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~- xen:/usr/local/etc# libvirtd 17:53:42.153: error : virRun:847 : internal error '/sbin/iptables --table filter --insert FORWARD --destination 192.168.122.0/255.255.255.0 --out-interface virbr0 --match state --state ESTABLISHED,RELATED --jump ACCEPT' exited with non-zero status 1 and signal 0: iptables: No chain/target/match by that name 17:53:42.153: error : networkAddMasqueradingIptablesRules:615 : failed to add iptables rule to allow forwarding to 'virbr0': Invalid argument 17:53:42.354: warning : qemudStartup:1067 : Unable to create cgroup for driver: No such device or address 17:53:42.372: warning : lxcStartup:1755 : Unable to create cgroup for driver: No such device or address 17:53:43.259: warning : qemudDispatchSignalEvent:385 : Shutting down on signal 2 -~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~- libvirtd keeps running, however it does not open ANY new ports to listening state. Extract from /usr/local/etc/libvirt/libvirtd.conf : (full conf here: http://pastebin.com/f6e0f572) listen_tls = 1 listen_tcp = 1 /usr/local/var/log/libvirt has 3 empty directories: {lxc,qemu,uml}, so nothing logged. xen:/# virsh list shows my current running domains, so looks like libvirt is fine. I have compiled XEN and libvirt from source (0.7.4, then upgraded 0.7.5, got same errors on both versions). Additional information: I am running three guest domains, all bridged to eth0 (peth0 ethernet card -> eth0 bridge -> vifs), from xend-config.sxp: (network-script network-bridge) Debian lenny Linux xen 2.6.18.8-xen0 #1 SMP Fri Nov 27 18:17:01 EET 2009 x86_64 GNU/Linux (here is kernel config: http://pastebin.com/f393c78f0) Note: I compiled iptables as a module manually, however without IMQ support, since it failed to compile. I have installed Xen 3.4.2, however virsh thinks it's 3.4.0 -~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~- virsh # version Compiled against library: libvir 0.7.5 Using library: libvir 0.7.5 Using API: Xen 3.0.1 Running hypervisor: Xen 3.4.0 -~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~--~*~- Any suggestions how to properly start libvirtd, pointers to other related mailing-lists or forums are very welcome. Thank you! Motiejus Jakštys

2 2

[libvirt] [PATCH 0/5] Fix various error squashing issues
by Cole Robinson 12 Jan '10

12 Jan '10

The following series adds internal APIs that help prevent legitimate errors from being overwritten by other errors (for example in cleanup routines). The majority of this series is a patch from Dan[1] which makes error callbacks explictly triggered when exiting an API call, rather than when an error is raised (I've updated this to cover the current codebase) [1] http://gitorious.org/~berrange/libvirt/staging/commits/error-callbacks Cole Robinson (4): virterror: Add virSetError qemu: migrate: Save MigratePerform error in MigrateFinish. libvirt.c: Preserve MigratePerform failure qemu: Disable errors in qemudShutdownVMDaemon Daniel P. Berrange (1): Ensure error handling callback functions are called from safe context src/libvirt.c | 849 +++++++++++++++++++++++------------------ src/libvirt_private.syms | 1 + src/qemu/qemu_driver.c | 18 + src/util/virterror.c | 102 +++--- src/util/virterror_internal.h | 4 +- 5 files changed, 548 insertions(+), 426 deletions(-)

3 12

[libvirt] Nice libvirt article on IBM developer works
by Hugh O. Brock 12 Jan '10

12 Jan '10

http://www.ibm.com/developerworks/linux/library/l-libvirt/index.html?ca=dgr… Maybe we can get more like this (despite the factual errors...) --H -- ======================================================== Hugh Brock, hbrock(a)redhat.com, +1-215-564-3232 Deltacloud API + Portal http://deltacloud.org Libvirt virtualization library http://libvirt.org ========================================================

1 0

Re: [libvirt] Segfault in event-test.c example
by pspreadborough＠comcast.net 12 Jan '10

12 Jan '10

----- pspreadborough(a)comcast.net wrote: > ----- "Matthias Bolte" <matthias.bolte(a)googlemail.com> wrote: > > > 2010/1/11 <pspreadborough(a)comcast.net>: > > > > > > ----- "Matthias Bolte" <matthias.bolte(a)googlemail.com> wrote: > > > > > >> 2010/1/10 <pspreadborough(a)comcast.net>: > > >> > > > >> > ----- "Matthias Bolte" <matthias.bolte(a)googlemail.com> wrote: > > >> > > > >> >> 2010/1/10 <pspreadborough(a)comcast.net>: > > >> >> > > > >> >> > Hello, > > >> >> > > > >> >> > I have been trying to use the domain event C code example > but > > >> >> > unfortunately it segfaults (signal 11) every time I run it: > > >> >> > > > >> >> > [root@Spring events-c]# ./event-test > > >> >> > myEventAddHandleFunc:221: Add handle 5 1 0xf081a0 0x8f727f8 > > >> >> > myEventAddHandleFunc:221: Add handle 7 1 0xf09990 0x8f727f8 > > >> >> > myEventAddHandleFunc:221: Add handle 8 1 0xed7940 0x8f727f8 > > >> >> > myEventAddTimeoutFunc:251: Adding Timeout -1 0xedefa0 > > 0x8f727f8 > > >> >> > myEventAddHandleFunc:221: Add handle 11 1 0xed7940 0x8f727f8 > > >> >> > myEventAddTimeoutFunc:251: Adding Timeout -1 0xedefa0 > > 0x8f727f8 > > >> >> > main:322 :: Registering domain event cbs > > >> >> > Segmentation fault (core dumped) > > >> >> > > > >> >> > Core was generated by > > >> >> > > > >> >> > > >> > > > `/root/libvirt-0.7.5/examples/domain-events/events-c/.libs/lt-event-test'. > > >> >> > Program terminated with signal 11, Segmentation fault. > > >> >> > [New process 21806] > > >> >> > [New process 21822] > > >> >> > #0 remoteDomainEventQueueFlush (timer=-1, opaque=0x8f727f8) > > at > > >> >> > remote/remote_driver.c:8720 > > >> >> > 8720 tempQueue.count = priv->domainEvents->count; > > >> >> > (gdb) bt > > >> >> > #0 remoteDomainEventQueueFlush (timer=-1, opaque=0x8f727f8) > > at > > >> >> > remote/remote_driver.c:8720 > > >> >> > #1 0x080490d3 in main (argc=Cannot access memory at address > > 0x1 > > >> >> > ) at event-test.c:347 > > >> >> > > > >> >> > The stack looks corrupted so I'm doubtful that this trace if > > of > > >> much > > >> >> value. > > >> >> > I have built > > >> >> > and installed libvirt-0.7.5 and it and it's tools seem to be > > >> >> operating > > >> >> > correctly. > > >> >> > > >> >> I tried the event-test with libvirt-0.7.5 and QEMU/Xen and > both > > >> are > > >> >> working as expected. No segfaults. > > >> >> > > >> >> Could you inspect the values of priv and priv->domainEvents in > > GDB > > >> >> using 'p priv' to see if they are NULL and try to dereference > > them > > >> in > > >> >> GDB using 'p *priv' to see if they point to valid memory > areas? > > >> >> > > >> >> Yes the backtrace looks corrupted. If there is stack/heap > > >> corruption > > >> >> involved valgrind may reveal it, so try to run the event-test > > in > > >> >> valgrind and see if that gives any hints. > > >> >> > > >> >> You can also try the GIT version of libvirt. There was a > > invalid > > >> free > > >> >> call (resulting in heap corruption) in the node device code > > fixed > > >> >> after the 0.7.5 release. But that should have no effect on the > > >> >> event-test. > > >> >> > > >> >> Matthias > > >> > > > >> > Matthias, > > >> > > > >> > priv->domainEvents is NULL, here's the gdb output: > > >> > > >> This explains the segfault. The next question is, why is it NULL? > > >> > > >> > (gdb) p *priv > > >> > $1 = {lock = {lock = {__data = {__lock = 1, __count = 0, > __owner > > = > > >> 21806, __kind = 0, __nusers = 1, {__spins = 0, __list = { > > >> > __next = 0x0}}}, __size = > > >> > > > "\001\000\000\000\000\000\000\000.U\000\000\000\000\000\000\001\000\000\000\000\000\000", > > >> > __align = 1}}, sock = 150469168, watch = 3, pid = 4, > > uses_tls = > > >> 1982791681, is_secure = 1815048801, session = 0x782f6269, > > >> > > >> Seeing uses_tls and is_secure being large numbers and knowing > that > > >> both are used as boolean values in the code and should have > values > > of > > >> 0 or 1 make me think that priv points to already freed memory > > here. > > >> > > >> > type = 0x2f646e65 <Address 0x2f646e65 out of bounds>, counter > = > > >> 1684956536, localUses = 1668248365, > > >> > hostname = 0x74656b <Address 0x74656b out of bounds>, debugLog > > = > > >> 0x0, saslconn = 0x0, saslDecoded = 0x0, saslDecodedLength = 0, > > >> > > >> type and hostname are char pointers, but the seem to point into > > >> nowhere, confirms that this is either freed memory or priv itself > > got > > >> overwritten due to heap corruption. > > >> > > >> > saslDecodedOffset = 0, saslEncoded = 0x0, saslEncodedLength = > > 0, > > >> saslEncodedOffset = 0, > > >> > buffer = '\0' <repeats 68 times>, > > >> > > > "n\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\bQ�\b��\030\034�\b\000\000\000\000�\033�\b\001\000\000\000\002\000\000\000�\033�\b\000\000\000\000\025|�\000\a", > > >> '\0' <repeats 11 times>, "X\000�\b", '\0' <repeats 12 times>, > > >> "\021\000\000\000\002\000\000\000P��\b\000\000\000\000\021", '\0' > > >> <repeats 15 times>, > > >> > > > "\021\000\000\0008\036�\b\f\000\000\000\020\000\000\000\021\000\000\000\a\000\000\000\b\000\000\000\t\000\000\000\021\000\000\000\002\000\000\000\230\034�\b\000\000\000\000A\000\000\000\003\000\000\000\001\000\000\000\001\000"..., > > >> bufferLength = 0, > > >> > bufferOffset = 0, callbackList = 0x0, domainEvents = 0x0, > > >> eventFlushTimer = 0, domainEventDispatching = 1, wakeupSendFD = > 0, > > >> > wakeupReadFD = 0, waitDispatch = 0x0, streams = 0x0} > > >> > > > >> > I'll try a run with valgrind and post the results. > > >> > > > >> > Pete > > >> > > > >> > > >> Could you test the Python version of this example found in > > >> examples/domain-events/events-python/event-test.py? Does this > > work? > > >> > > >> Otherwise lets see if valgrind gives any hints. > > >> > > >> Matthias > > > > > > > > > During initialization I notice that the myEventAddHandleFunc() > > method is > > > called multiple times, each time with a different fd value (5,7,8 > > and 11). > > > The way the code is written only the last fd value is recorded and > > then > > > used in the poll() call. Is this the intended? if so why are the > > preceding > > > fds ignored? > > > > > > myEventAddHandleFunc:223: Add handle 5 1 0xf13480 0x97b97d8 > > > myEventAddHandleFunc:223: Add handle 7 1 0xf14c70 0x97b97d8 > > > Allocating domainEvents:0x97c6b10 > > > myEventAddHandleFunc:223: Add handle 8 1 0xee2940 0x97b97d8 > > > myEventAddTimeoutFunc:260: Adding Timeout -1 0xee9fc0 0x97b97d8 > > > Allocating domainEvents:0x97c5780 > > > myEventAddHandleFunc:223: Add handle 11 1 0xee2940 0x97b97d8 > > > myEventAddTimeoutFunc:260: Adding Timeout -1 0xee9fc0 0x97b97d8 > > > main:333 :: Registering domain event cbs > > > > > > > > > Regards, > > > > > > Pete > > > > > > > That's strange. I can't reproduce this neither. I always get exactly > > one call to myEventAddHandleFunc: > > > > myEventAddHandleFunc:221: Add handle 3 1 0x7ff116f68b00 0x1d97f00 > > myEventAddTimeoutFunc:251: Adding Timeout -1 0x7ff116f68750 > 0x1d97f00 > > main:322 :: Registering domain event cbs > > myEventUpdateHandleFunc:232: Updated Handle 0 0 > > myEventUpdateHandleFunc:232: Updated Handle 0 1 > > > > You could try to run the event-test in GDB and set a breakpoint on > > myEventAddHandleFunc to see where 4 additional calls to > > myEventAddHandleFunc come from. > > > > In my case I get this backtrace when setting a breakpoint on > > myEventAddHandleFunc: > > > > (gdb) bt > > #0 myEventAddHandleFunc (fd=6, event=1, cb=0x7f1be6ec3b00 > > <remoteDomainEventFired>, opaque=0xc68f00, ff=0) at event-test.c:220 > > #1 0x00007f1be6ecbaaf in doRemoteOpen (conn=0xc68f00, > > priv=0x7f1be7350010, auth=0x0, flags=0) at > remote/remote_driver.c:893 > > #2 0x00007f1be6ece053 in remoteOpen (conn=0xc68f00, auth=0x0, > > flags=13007744) at remote/remote_driver.c:1076 > > #3 0x00007f1be6eb155d in do_open (name=0x7fff48400968 > > "qemu:///system", auth=0x0, flags=0) at libvirt.c:1117 > > #4 0x0000000000400eb3 in main (argc=<value optimized out>, > > argv=<value optimized out>) at event-test.c:313 > > > > Matthias > > > Matthias > > Here are the four stack traces, one for each time > myEventAddHandleFunc() was > called. > > #0 myEventAddHandleFunc (fd=8, event=1, cb=0x85b480 > <xenStoreWatchEvent>, opaque=0x824a7d8, ff=0) at event-test.c:223 > #1 0x007ccf55 in virEventAddHandle (fd=8, events=1, cb=0x85b480 > <xenStoreWatchEvent>, opaque=0x824a7d8, ff=0) > at util/event.c:45 > #2 0x0085b291 in xenStoreOpen (conn=0x824a7d8, auth=0x0, flags=<value > optimized out>) at xen/xs_internal.c:339 > #3 0x00844287 in xenUnifiedOpen (conn=0x824a7d8, auth=0x0, flags=0) > at xen/xen_driver.c:352 > #4 0x00811d05 in do_open (name=0xbf8c49d4 "xen:///", auth=0x0, > flags=0) at libvirt.c:1117 > #5 0x08048e92 in main (argc=Cannot access memory at address 0x2 > ) at event-test.c:325 > (gdb) c > Continuing. > (gdb) b > Note: breakpoint 1 also set at pc 0x8048bc9. > Breakpoint 2 at 0x8048bc9: file event-test.c, line 223. > (gdb) bt > #0 myEventAddHandleFunc (fd=10, event=1, cb=0x85cc70 > <xenInotifyEvent>, opaque=0x824a7d8, ff=0) at event-test.c:223 > #1 0x007ccf55 in virEventAddHandle (fd=10, events=1, cb=0x85cc70 > <xenInotifyEvent>, opaque=0x824a7d8, ff=0) at util/event.c:45 > #2 0x0085c827 in xenInotifyOpen (conn=0x824a7d8, auth=0x0, flags=0) > at xen/xen_inotify.c:460 > #3 0x008444f1 in xenUnifiedOpen (conn=0x824a7d8, auth=0x0, flags=0) > at xen/xen_driver.c:391 > #4 0x00811d05 in do_open (name=0xbf8c49d4 "xen:///", auth=0x0, > flags=0) at libvirt.c:1117 > #5 0x08048e92 in main (argc=Cannot access memory at address 0x1 > ) at event-test.c:325 > (gdb) c > Continuing. > (gdb) bt > #0 myEventAddHandleFunc (fd=11, event=1, cb=0x82a940 > <remoteDomainEventFired>, opaque=0x824a7d8, ff=0) at event-test.c:223 > #1 0x007ccf55 in virEventAddHandle (fd=11, events=1, cb=0x82a940 > <remoteDomainEventFired>, opaque=0x824a7d8, ff=0) > at util/event.c:45 > #2 0x0082c478 in doRemoteOpen (conn=0x824a7d8, priv=0xb7534008, > auth=0x0, flags=0) at remote/remote_driver.c:894 > #3 0x00830448 in remoteOpenSecondaryDriver (conn=0x824a7d8, auth=0x0, > flags=0, priv=0xbf8c2668) at remote/remote_driver.c:1006 > #4 0x0083082a in remoteNetworkOpen (conn=0x824a7d8, auth=0x0, > flags=0) at remote/remote_driver.c:3549 > #5 0x00811e2f in do_open (name=0xbf8c49d4 "xen:///", auth=0x0, > flags=0) at libvirt.c:1137 > #6 0x08048e92 in main (argc=1, argv=0xbf8c28b4) at event-test.c:325 > (gdb) c > Continuing. > (gdb) bt > #0 myEventAddHandleFunc (fd=14, event=1, cb=0x82a940 > <remoteDomainEventFired>, opaque=0x824a7d8, ff=0) at event-test.c:223 > #1 0x007ccf55 in virEventAddHandle (fd=14, events=1, cb=0x82a940 > <remoteDomainEventFired>, opaque=0x824a7d8, ff=0) > at util/event.c:45 > #2 0x0082c478 in doRemoteOpen (conn=0x824a7d8, priv=0x8258ab0, > auth=0x0, flags=0) at remote/remote_driver.c:894 > #3 0x00830448 in remoteOpenSecondaryDriver (conn=0x824a7d8, auth=0x0, > flags=0, priv=0xbf8c2668) at remote/remote_driver.c:1006 > #4 0x0083078a in remoteInterfaceOpen (conn=0x824a7d8, auth=0x0, > flags=0) at remote/remote_driver.c:4104 > #5 0x00811f4e in do_open (name=0xbf8c49d4 "xen:///", auth=0x0, > flags=0) at libvirt.c:1156 > #6 0x08048e92 in main (argc=1, argv=0xbf8c28b4) at event-test.c:325 > > Regards, > > Pete > > > -- > Libvir-list mailing list > Libvir-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvir-list Matthias, Using the UIR xen+unix:/// works! I'm curious to know why when using the UIR xen:/// multiple myEventAddHandleFunc() calls occurred. Are there and fields I could use to identify and ignore the spurious calls? I'd like to use the event monitoring for several remote Xen hosts. I assume I'll have to modify the code to connect remotely to each host and hope for just one myEventAddHandleFunc() call per host. Thanks for your assistance it's much apprecied, Regards, Pete

2 2

[libvirt] [PATCH] remote_driver.c: fix a NULL dereference in remoteDomainEventQueueFlush().
by kakuma 12 Jan '10

12 Jan '10

Hi, all. There is a case of a NULL dereference in function remoteDomainEventQueueFlush() in remote_driver.c In the case of local connection conn->privateData->domainEvents isn't reserved. In this case it will occurs segment fault. (for example examples/domain-events/events-c/event-test.c) I think the following patch will be available. Thanks. --- src/remote/remote_driver.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c index d6f5fce..b112fd3 100644 --- a/src/remote/remote_driver.c +++ b/src/remote/remote_driver.c @@ -8709,7 +8709,7 @@ void remoteDomainEventQueueFlush(int timer ATTRIBUTE_UNUSED, void *opaque) { virConnectPtr conn = opaque; - struct private_data *priv = conn->privateData; + struct private_data *priv = conn->networkPrivateData; virDomainEventQueue tempQueue; remoteDriverLock(priv); -- 1.5.6.1 -- kakuma <f-kak(a)ksh.biglobe.ne.jp>

2 2

Re: [libvirt] Segfault in event-test.c example
by pspreadborough＠comcast.net 12 Jan '10

12 Jan '10

----- "Matthias Bolte" <matthias.bolte(a)googlemail.com> wrote: > 2010/1/10 <pspreadborough(a)comcast.net>: > > > > ----- "Matthias Bolte" <matthias.bolte(a)googlemail.com> wrote: > > > >> 2010/1/10 <pspreadborough(a)comcast.net>: > >> > > >> > Hello, > >> > > >> > I have been trying to use the domain event C code example but > >> > unfortunately it segfaults (signal 11) every time I run it: > >> > > >> > [root@Spring events-c]# ./event-test > >> > myEventAddHandleFunc:221: Add handle 5 1 0xf081a0 0x8f727f8 > >> > myEventAddHandleFunc:221: Add handle 7 1 0xf09990 0x8f727f8 > >> > myEventAddHandleFunc:221: Add handle 8 1 0xed7940 0x8f727f8 > >> > myEventAddTimeoutFunc:251: Adding Timeout -1 0xedefa0 0x8f727f8 > >> > myEventAddHandleFunc:221: Add handle 11 1 0xed7940 0x8f727f8 > >> > myEventAddTimeoutFunc:251: Adding Timeout -1 0xedefa0 0x8f727f8 > >> > main:322 :: Registering domain event cbs > >> > Segmentation fault (core dumped) > >> > > >> > Core was generated by > >> > > >> > `/root/libvirt-0.7.5/examples/domain-events/events-c/.libs/lt-event-test'. > >> > Program terminated with signal 11, Segmentation fault. > >> > [New process 21806] > >> > [New process 21822] > >> > #0 remoteDomainEventQueueFlush (timer=-1, opaque=0x8f727f8) at > >> > remote/remote_driver.c:8720 > >> > 8720 tempQueue.count = priv->domainEvents->count; > >> > (gdb) bt > >> > #0 remoteDomainEventQueueFlush (timer=-1, opaque=0x8f727f8) at > >> > remote/remote_driver.c:8720 > >> > #1 0x080490d3 in main (argc=Cannot access memory at address 0x1 > >> > ) at event-test.c:347 > >> > > >> > The stack looks corrupted so I'm doubtful that this trace if of > much > >> value. > >> > I have built > >> > and installed libvirt-0.7.5 and it and it's tools seem to be > >> operating > >> > correctly. > >> > >> I tried the event-test with libvirt-0.7.5 and QEMU/Xen and both > are > >> working as expected. No segfaults. > >> > >> Could you inspect the values of priv and priv->domainEvents in GDB > >> using 'p priv' to see if they are NULL and try to dereference them > in > >> GDB using 'p *priv' to see if they point to valid memory areas? > >> > >> Yes the backtrace looks corrupted. If there is stack/heap > corruption > >> involved valgrind may reveal it, so try to run the event-test in > >> valgrind and see if that gives any hints. > >> > >> You can also try the GIT version of libvirt. There was a invalid > free > >> call (resulting in heap corruption) in the node device code fixed > >> after the 0.7.5 release. But that should have no effect on the > >> event-test. > >> > >> Matthias > > > > Matthias, > > > > priv->domainEvents is NULL, here's the gdb output: > > This explains the segfault. The next question is, why is it NULL? > > > (gdb) p *priv > > $1 = {lock = {lock = {__data = {__lock = 1, __count = 0, __owner = > 21806, __kind = 0, __nusers = 1, {__spins = 0, __list = { > > __next = 0x0}}}, __size = > "\001\000\000\000\000\000\000\000.U\000\000\000\000\000\000\001\000\000\000\000\000\000", > > __align = 1}}, sock = 150469168, watch = 3, pid = 4, uses_tls = > 1982791681, is_secure = 1815048801, session = 0x782f6269, > > Seeing uses_tls and is_secure being large numbers and knowing that > both are used as boolean values in the code and should have values of > 0 or 1 make me think that priv points to already freed memory here. > > > type = 0x2f646e65 <Address 0x2f646e65 out of bounds>, counter = > 1684956536, localUses = 1668248365, > > hostname = 0x74656b <Address 0x74656b out of bounds>, debugLog = > 0x0, saslconn = 0x0, saslDecoded = 0x0, saslDecodedLength = 0, > > type and hostname are char pointers, but the seem to point into > nowhere, confirms that this is either freed memory or priv itself got > overwritten due to heap corruption. > > > saslDecodedOffset = 0, saslEncoded = 0x0, saslEncodedLength = 0, > saslEncodedOffset = 0, > > buffer = '\0' <repeats 68 times>, > "n\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\001\000\000\000\000\000\000\000\001\000\000\000\bQ�\b��\030\034�\b\000\000\000\000�\033�\b\001\000\000\000\002\000\000\000�\033�\b\000\000\000\000\025|�\000\a", > '\0' <repeats 11 times>, "X\000�\b", '\0' <repeats 12 times>, > "\021\000\000\000\002\000\000\000P��\b\000\000\000\000\021", '\0' > <repeats 15 times>, > "\021\000\000\0008\036�\b\f\000\000\000\020\000\000\000\021\000\000\000\a\000\000\000\b\000\000\000\t\000\000\000\021\000\000\000\002\000\000\000\230\034�\b\000\000\000\000A\000\000\000\003\000\000\000\001\000\000\000\001\000"..., > bufferLength = 0, > > bufferOffset = 0, callbackList = 0x0, domainEvents = 0x0, > eventFlushTimer = 0, domainEventDispatching = 1, wakeupSendFD = 0, > > wakeupReadFD = 0, waitDispatch = 0x0, streams = 0x0} > > > > I'll try a run with valgrind and post the results. > > > > Pete > > > > Could you test the Python version of this example found in > examples/domain-events/events-python/event-test.py? Does this work? > > Otherwise lets see if valgrind gives any hints. > > Matthias During initialization I notice that the myEventAddHandleFunc() method is called multiple times, each time with a different fd value (5,7,8 and 11). The way the code is written only the last fd value is recorded and then used in the poll() call. Is this the intended? if so why are the preceding fds ignored? myEventAddHandleFunc:223: Add handle 5 1 0xf13480 0x97b97d8 myEventAddHandleFunc:223: Add handle 7 1 0xf14c70 0x97b97d8 Allocating domainEvents:0x97c6b10 myEventAddHandleFunc:223: Add handle 8 1 0xee2940 0x97b97d8 myEventAddTimeoutFunc:260: Adding Timeout -1 0xee9fc0 0x97b97d8 Allocating domainEvents:0x97c5780 myEventAddHandleFunc:223: Add handle 11 1 0xee2940 0x97b97d8 myEventAddTimeoutFunc:260: Adding Timeout -1 0xee9fc0 0x97b97d8 main:333 :: Registering domain event cbs Regards, Pete

3 3

[libvirt] [PATCH] Document the domain XML cache attribute for disk devices
by Matthias Bolte 12 Jan '10

12 Jan '10

--- docs/formatdomain.html.in | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 46ab0ac..af31699 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -343,7 +343,7 @@ <pre> ... <disk type='file'> - <driver name="tap" type="aio"> + <driver name="tap" type="aio" cache="default"> <source file='/var/lib/xen/images/fv0'/> <target dev='hda' bus='ide'/> <encryption type='...'> @@ -383,7 +383,9 @@ <dd>If the hypervisor supports multiple backend drivers, then the optional <code>driver</code> element allows them to be selected. The <code>name</code> attribute is the primary backend driver name, while the optional <code>type</code> - attribute provides the sub-type. <span class="since">Since 0.1.8</span> + attribute provides the sub-type. The optional <code>cache</code> attribute + controls the cache mechanism, possible values are "default", "none", + "writethrough" and "writeback". <span class="since">Since 0.1.8</span> </dd> <dt><code>encryption</code></dt> <dd>If present, specifies how the volume is encrypted. See -- 1.6.0.4

2 2

[libvirt] [PATCH] qemu: Fix a memory leak in qemudExtractTTYPath
by Matthias Bolte 12 Jan '10

12 Jan '10

qemudWaitForMonitor calls qemudReadLogOutput with qemudFindCharDevicePTYs as callback. qemudFindCharDevicePTYs calls qemudExtractTTYPath to assign a string to chr->data.file.path. Afterwards qemudWaitForMonitor may call qemudFindCharDevicePTYsMonitor that overwrites chr->data.file.path without freeing the old value. This results in leaking the memory allocated by qemudExtractTTYPath. Report an OOM error if the strdup in qemudFindCharDevicePTYsMonitor fails. --- src/qemu/qemu_driver.c | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index daa6f94..8817565 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -1433,7 +1433,13 @@ qemudFindCharDevicePTYsMonitor(virConnectPtr conn, return -1; \ } \ \ + VIR_FREE(chr->data.file.path); \ chr->data.file.path = strdup(path); \ + \ + if (chr->data.file.path == NULL) { \ + virReportOOMError(conn); \ + return -1; \ + } \ } \ } -- 1.6.0.4

2 2