On 1/17/20 7:24 PM, Daniel P. Berrangé wrote:
The virConnectGetDomainCapabilities API accepts either a binary path
to the emulator, or desired guest arch. If guest arch is not given,
then the host arch is assumed.
In the case where the binary is not given, the code tried to find the
emulator
On 1/17/20 7:24 PM, Daniel P. Berrangé wrote:
The virConnectGetDomainCapabilities API accepts either a binary path
to the emulator, or desired guest arch. If guest arch is not given,
then the host arch is assumed.
I forgot to mention that virConnectBaselineHypervisorCPU and
Looks ok and also fixes on my system the problem.
Tested-by: Boris Fiuczynski
On 1/17/20 7:24 PM, Daniel P. Berrangé wrote:
The virConnectGetDomainCapabilities API accepts either a binary path
to the emulator, or desired guest arch. If guest arch is not given,
then the host arch is assumed.
The virConnectGetDomainCapabilities API accepts either a binary path
to the emulator, or desired guest arch. If guest arch is not given,
then the host arch is assumed.
In the case where the binary is not given, the code tried to find the
emulator binary in the existing list of cached emulator
