From: Marcelo Tosatti mtosa...@redhat.com
Michael reported a qemu-kvm SIGSEGV at shutdown:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x411d0940 (LWP 14446)]
0x0040afb4 in qemu_mod_timer (ts=0x19f0fd0,
expire_time=62275467335)
at
On 10/29/2009 12:38 AM, Marcelo Tosatti wrote:
This will miss an event at the very beginning of the loop (powerdown
requested before we had a chance to spin up?). I think it should be
fine since there will be a pending signal which will break us out of
kvm_cpu_exec() before it has a chance to
On 10/27/2009 05:33 PM, Marcelo Tosatti wrote:
Michael reported a qemu-kvm SIGSEGV at shutdown:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x411d0940 (LWP 14446)]
0x0040afb4 in qemu_mod_timer (ts=0x19f0fd0,
expire_time=62275467335)
at
On Wed, Oct 28, 2009 at 11:42:56AM +0200, Avi Kivity wrote:
On 10/27/2009 05:33 PM, Marcelo Tosatti wrote:
Michael reported a qemu-kvm SIGSEGV at shutdown:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x411d0940 (LWP 14446)]
0x0040afb4 in qemu_mod_timer
Michael reported a qemu-kvm SIGSEGV at shutdown:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x411d0940 (LWP 14446)]
0x0040afb4 in qemu_mod_timer (ts=0x19f0fd0,
expire_time=62275467335)
at /home/mst/scm/qemu-kvm/vl.c:1009
1009if
On Mon, Oct 26, 2009 at 04:46:02PM -0200, Marcelo Tosatti wrote:
Michael reported a qemu-kvm SIGSEGV at shutdown:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x411d0940 (LWP 14446)]
0x0040afb4 in qemu_mod_timer (ts=0x19f0fd0,
expire_time=62275467335)
On Mon, Oct 26, 2009 at 08:58:49PM +0200, Gleb Natapov wrote:
On Mon, Oct 26, 2009 at 04:46:02PM -0200, Marcelo Tosatti wrote:
Michael reported a qemu-kvm SIGSEGV at shutdown:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x411d0940 (LWP 14446)]