Partially revert "qemu: fix missing error reports in capabilities probing"

This partially reverts commit 5331c4804f.

The original commit mistakenly thought virFileCacheLookup did not set
an error. In fact the only case it doesn't set an error for is when
the cache key is NULL. This in fact the fault of the caller for passing
an invalid cache key, so doesn't need to be handled.

This caller bug was fixed by checking for a NULL binary in the
virQEMUCapsCacheLookupDefault method.

Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
Daniel P. Berrangé 2020-07-15 15:53:11 +01:00
parent fdab2f1a31
commit 7d488a7c45
2 changed files with 1 additions and 8 deletions

View File

@ -5640,11 +5640,6 @@ virQEMUCapsCacheLookup(virFileCachePtr cache,
priv->microcodeVersion = virHostCPUGetMicrocodeVersion();
ret = virFileCacheLookup(cache, binary);
if (!ret) {
virReportError(VIR_ERR_INTERNAL_ERROR,
_("no capabilities available for %s"), binary);
return NULL;
}
VIR_DEBUG("Returning caps %p for %s", ret, binary);
return ret;

View File

@ -5306,10 +5306,8 @@ qemuDomainPostParseDataAlloc(const virDomainDef *def,
virQEMUDriverPtr driver = opaque;
if (!(*parseOpaque = virQEMUCapsCacheLookup(driver->qemuCapsCache,
def->emulator))) {
virResetLastError();
def->emulator)))
return 1;
}
return 0;
}