Ok, I have found a solution. The process spawned was using SIGUSR1 to
signal something to the parent process (device internals). It seems that
QEMU uses SIGUSR1 internally because when I have switched to SIGUSR2 it
works as expected.
Maciek
On 07/23/2015 01:20 PM, Maciej Bielski wrote:
> I am usi
On 24 July 2015 at 16:54, Maciej Bielski wrote:
> Ok, I have found a solution. The process spawned was using SIGUSR1 to
> signal something to the parent process (device internals). It seems that
> QEMU uses SIGUSR1 internally because when I have switched to SIGUSR2 it
> works as expected.
Yes, we
The problem is still alive, and "kicking".
Whenever the ethernet cable is detached or the network (ADSL
modem/router) goes offline for a brief moment, the guest VMs remain
unable to reconnect, as shown in the previous post.
I have no idea how to move around this.
-- Davide
Hello,
I'm running a lot of VMs under qemu (using libvirt and KVM). Sometimes (one
time per 2000-3000 runs) I got following:
1. VM is paused by qemu. I can't resume that VM. I can just reset it and
resume.
2. In VM log file I see following: "KVM: unknown exit, hardware reason 31"
with a CPU dump
