Michal Privoznik b1dc59b395 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>
2015-09-22 17:05:16 +02:00
..
2014-09-03 09:36:13 -06:00
2015-05-21 18:13:18 +02:00
2015-04-23 17:08:48 -04:00
2015-06-25 09:11:15 +02:00
2015-09-22 13:56:59 +02:00
2015-09-22 13:56:59 +02:00
2015-04-27 16:03:31 +02:00
2013-07-29 13:09:39 -06:00
2015-05-21 18:13:18 +02:00
2015-05-04 15:01:27 +02:00
2015-04-23 17:08:48 -04:00
2014-11-25 08:47:12 -07:00
2013-10-14 10:31:01 +01:00
2015-04-14 19:33:02 +02:00
2015-04-14 19:33:02 +02:00
2014-04-08 11:15:55 +01:00
2015-04-23 17:08:48 -04:00