From: Julio Faracco
Some people from IBM does not use 'ibm.com' domain emails.
They use personal or other domains.
Signed-off-by: Julio Faracco
---
docs/gitdm/companies/ibm | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/gitdm/companies/ibm b/docs/gitdm/companies/ibm
index
From: Julio Faracco
There is an issue with when of 'x' or 'y' settings are 0.
Function virDomainVideoResolutionDefParseXML() will validate this XML,
but both 'x' and 'y' will be removed. One example, if someone defines
this settings:
After applying this settings, funcion
On 10/19/19 12:55 PM, Ján Tomko wrote:
On Sat, Oct 19, 2019 at 07:21:15AM -0300, Daniel Henrique Barboza wrote:
On 10/18/19 7:37 PM, Ján Tomko wrote:
Ján Tomko (10):
tools: cmdDomblkinfoGet: reindent parameters
virsh: use g_strdup in cmdDomblkinfoGet
virsh: use g_strdup in
On Sat, Oct 19, 2019 at 07:21:15AM -0300, Daniel Henrique Barboza wrote:
On 10/18/19 7:37 PM, Ján Tomko wrote:
Ján Tomko (10):
tools: cmdDomblkinfoGet: reindent parameters
virsh: use g_strdup in cmdDomblkinfoGet
virsh: use g_strdup in virshDomainGetEditMetadata
virsh: getSignalNumber:
On 10/18/19 7:37 PM, Ján Tomko wrote:
Ján Tomko (10):
tools: cmdDomblkinfoGet: reindent parameters
virsh: use g_strdup in cmdDomblkinfoGet
virsh: use g_strdup in virshDomainGetEditMetadata
virsh: getSignalNumber: rename variables
virsh: getSignalNumber: use g_autofree
virsh:
On 10/18/19 3:22 PM, Daniel P. Berrangé wrote:
The CPU driver only supports CPU models for PPC64 architecture, not
plain PPC.
Failed to probe capabilities for /usr/bin/qemu-system-ppc:
this function is not supported by the connection driver:
'ppc' architecture is not supported by CPU
Commit 01ca4010d86 (libvirt v5.1.0) moved address reservation for
hotplugged interface devices up to an earlier point in
qemuDomainAttachNetDevice() because some function called when
hotplugging on aarch64 needed to know the address type, and failed
when it was "none".
This unfortunately caused a
