[Avocado-devel] add possibility to not freeze VM when test execution is stopped (ctrl-z)

2019-05-13 Thread Radek Duda
Hi,
some time ago I was used to stop test execution (ctrl-z) and then manually
interact with GUI of VM. That is impossible now since not only test
execution is stopped, but VM is stopped too - it is frozen and does not
interact to keyboard/mouse input through remote-viewer any more.
I consulted this with Lukáš, who described this as a proper behavior and
possibility to interact with VM's GUI as a bug, which has been fixed in the
past. I would like to have option to stop test execution (ctrl-z), but not
to freeze VM. Do you guys think it is possible?

regards,

Radek Duda
SPICE-QE


Re: [Avocado-devel] add possibility to not freeze VM when test execution is stopped (ctrl-z)

2019-05-13 Thread Cleber Rosa



- Original Message -
> From: "Radek Duda" 
> To: "avocado-devel" 
> Sent: Monday, May 13, 2019 5:33:50 AM
> Subject: [Avocado-devel] add possibility to not freeze VM when test   
> execution is stopped (ctrl-z)
> 
> Hi,
> some time ago I was used to stop test execution (ctrl-z) and then manually
> interact with GUI of VM. That is impossible now since not only test
> execution is stopped, but VM is stopped too - it is frozen and does not
> interact to keyboard/mouse input through remote-viewer any more.
> I consulted this with Lukáš, who described this as a proper behavior and
> possibility to interact with VM's GUI as a bug, which has been fixed in the
> past. I would like to have option to stop test execution (ctrl-z), but not
> to freeze VM. Do you guys think it is possible?
> 

Hi Radek,

I think the tricky part is determining what is "the VM" to Avocado, and not 
passing SIGSTOP
to that process.  Have you tried, instead, to send a SIGCONT to that process 
only?  Depending
on how your test system looks like (and it's running) I'd think something like:

 $ avocado run ...
 

 $ killal -CONT qemu

Should do the trick.  Let me know how if this works and if you find it 
acceptable.

Cheers,
- Cleber.

> regards,
> 
> Radek Duda
> SPICE-QE
> 



Re: [Avocado-devel] add possibility to not freeze VM when test execution is stopped (ctrl-z)

2019-05-14 Thread Lukáš Doktor
Dne 14. 05. 19 v 4:01 Cleber Rosa napsal(a):
> 
> 
> - Original Message -
>> From: "Radek Duda" 
>> To: "avocado-devel" 
>> Sent: Monday, May 13, 2019 5:33:50 AM
>> Subject: [Avocado-devel] add possibility to not freeze VM when test  
>> execution is stopped (ctrl-z)
>>
>> Hi,
>> some time ago I was used to stop test execution (ctrl-z) and then manually
>> interact with GUI of VM. That is impossible now since not only test
>> execution is stopped, but VM is stopped too - it is frozen and does not
>> interact to keyboard/mouse input through remote-viewer any more.
>> I consulted this with Lukáš, who described this as a proper behavior and
>> possibility to interact with VM's GUI as a bug, which has been fixed in the
>> past. I would like to have option to stop test execution (ctrl-z), but not
>> to freeze VM. Do you guys think it is possible?
>>
> 
> Hi Radek,
> 
> I think the tricky part is determining what is "the VM" to Avocado, and not 
> passing SIGSTOP
> to that process.  Have you tried, instead, to send a SIGCONT to that process 
> only?  Depending
> on how your test system looks like (and it's running) I'd think something 
> like:
> 
>  $ avocado run ...
>  
> 
>  $ killal -CONT qemu
> 
> Should do the trick.  Let me know how if this works and if you find it 
> acceptable.
> 

Hello guys,

we talked about this with Radek, he is aware of the SIGCONT, but it is not 
convenient (as you need to resume aexpects, netcats and such as well, otherwise 
it will hang after some writes). Basically the current behavior suits some, 
others might prefer to stop only the main test. We decided to SIGSTOP 
everything because it sounded as a useful feature, I even had plans to add 
interactive options (to resume bg threads, to attach debugger, to list results 
dir, ...) but it was never a priority.

The reason I wanted Radek to write to avocado-devel was to find out whether 
anyone actually benefits from the SIGSTOP, because I think we could simply 
switch the behavior. But if there are some users, we might consider adding cfg 
option to adjust the behavior.

As for me I used to use it as well, even had it on my todo-list to fix it as it 
was suppose to be frozen. Now when it works I dislike it as well... Since it 
didn't work for a long time I'd be slightly inclined towards changing the 
behavior back with or without the cfg option.

Regards,
Lukáš

> Cheers,
> - Cleber.
> 
>> regards,
>>
>> Radek Duda
>> SPICE-QE
>>
> 




signature.asc
Description: OpenPGP digital signature