Re: [libvirt] [PATCH v2 1/3] qemu: use a bigger unplug timeout for PPC64 guests

2019-10-14 Thread Cole Robinson
On 10/11/19 3:54 PM, Daniel Henrique Barboza wrote: On 10/9/19 5:15 PM, Cole Robinson wrote: On 9/11/19 5:05 PM, Daniel Henrique Barboza wrote: For some architectures and setups, device removal can take longer than the default 5 seconds. This results in commands such as 'virsh setvcpus' to fi

Re: [libvirt] [PATCH v2 1/3] qemu: use a bigger unplug timeout for PPC64 guests

2019-10-11 Thread Daniel Henrique Barboza
On 10/9/19 5:15 PM, Cole Robinson wrote: On 9/11/19 5:05 PM, Daniel Henrique Barboza wrote: For some architectures and setups, device removal can take longer than the default 5 seconds. This results in commands such as 'virsh setvcpus' to fire timeout messages even if the operation were succe

Re: [libvirt] [PATCH v2 1/3] qemu: use a bigger unplug timeout for PPC64 guests

2019-10-09 Thread Cole Robinson
On 9/11/19 5:05 PM, Daniel Henrique Barboza wrote: For some architectures and setups, device removal can take longer than the default 5 seconds. This results in commands such as 'virsh setvcpus' to fire timeout messages even if the operation were successful in the guest, confusing the user. This

[libvirt] [PATCH v2 1/3] qemu: use a bigger unplug timeout for PPC64 guests

2019-09-11 Thread Daniel Henrique Barboza
For some architectures and setups, device removal can take longer than the default 5 seconds. This results in commands such as 'virsh setvcpus' to fire timeout messages even if the operation were successful in the guest, confusing the user. This patch sets a new 10 seconds unplug timeout for PPC64