[virt-tools-list] [virt-manager PATCH] virtManager: keep polling the connection while waiting for a new VM

[Cole Robinson]

On 02/13/2014 08:47 AM, Giuseppe Scrivano wrote:
> it fixes:
> 
> Traceback (most recent call last):
>   File "virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper
>     callback(asyncjob, *args, **kwargs)
>   File "virt-manager/virtManager/create.py", line 1793, in do_install
>     vm = self.conn.get_vm(guest.uuid)
>   File "virt-manager/virtManager/connection.py", line 676, in get_vm
>     return self.vms[uuid]
> KeyError: '933200a3-7124-4d1f-b0ad-847ea2b7cc23'
> 
> Signed-off-by: Giuseppe Scrivano <gscrivan at redhat.com>
> ---
>  virtManager/create.py | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/virtManager/create.py b/virtManager/create.py
> index d8e68c3..f8c72e4 100644
> --- a/virtManager/create.py
> +++ b/virtManager/create.py
> @@ -1789,6 +1789,7 @@ class vmmCreate(vmmGObjectUI):
>          while (guest.uuid not in self.conn.vms) and (count < 100):
>              count += 1
>              time.sleep(.1)
> +            self.conn.schedule_priority_tick(pollvm=True)
>  
>          vm = self.conn.get_vm(guest.uuid)
>          vm.tick()
> 

That will queue quite a lot of API calls, and particularly with the new domain
events turned on that shouldn't even make a difference that I can see. Is this
regularly reproducible? If so, how?

- Cole