b1dc59b qemuTestDriverInit: init the driver lock too

Authored and Committed by mprivozn 8 years ago
    qemuTestDriverInit: init the driver lock too
    
    Even though usage of the lock is limited to a very few cases,
    it's still needed. Therefore we should initialize it too.
    Otherwise we may get some random test failures:
    
    ==1204== Conditional jump or move depends on uninitialised value(s)
    ==1204==    at 0xEF7F7CF: pthread_mutex_lock (in /lib64/libpthread-2.20.so)
    ==1204==    by 0x9CA89A5: virMutexLock (virthread.c:89)
    ==1204==    by 0x450B2A: qemuDriverLock (qemu_conf.c:83)
    ==1204==    by 0x45549C: virQEMUDriverGetConfig (qemu_conf.c:869)
    ==1204==    by 0x448E29: qemuDomainDeviceDefPostParse (qemu_domain.c:1240)
    ==1204==    by 0x9CC9B13: virDomainDeviceDefPostParse (domain_conf.c:4224)
    ==1204==    by 0x9CC9B91: virDomainDefPostParseDeviceIterator (domain_conf.c:4251)
    ==1204==    by 0x9CC7843: virDomainDeviceInfoIterateInternal (domain_conf.c:3440)
    ==1204==    by 0x9CC9C25: virDomainDefPostParse (domain_conf.c:4276)
    ==1204==    by 0x9CEEE03: virDomainDefParseXML (domain_conf.c:16400)
    ==1204==    by 0x9CEF5B4: virDomainDefParseNode (domain_conf.c:16582)
    ==1204==    by 0x9CEF423: virDomainDefParse (domain_conf.c:16529)
    
    Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
    
        
file modified
+5 -1