On Mon, Mar 07, 2016 at 08:00:49PM +0100, Christian Borntraeger wrote:
> On 03/07/2016 06:01 PM, Stefan Hajnoczi wrote:
> > On Mon, Mar 07, 2016 at 01:29:08PM +0100, Christian Borntraeger wrote:
> >> Folks,
> >>
> >> I had a crash of a qemu guest in tracked_request_begin.
> >> The testcase was a gu
On 03/07/2016 06:01 PM, Stefan Hajnoczi wrote:
> On Mon, Mar 07, 2016 at 01:29:08PM +0100, Christian Borntraeger wrote:
>> Folks,
>>
>> I had a crash of a qemu guest in tracked_request_begin.
>> The testcase was a guest with ramdisk/kernel that reboots in a
>> loop. (about 10 times per second) wit
On Mon, Mar 07, 2016 at 01:29:08PM +0100, Christian Borntraeger wrote:
> Folks,
>
> I had a crash of a qemu guest in tracked_request_begin.
> The testcase was a guest with ramdisk/kernel that reboots in a
> loop. (about 10 times per second) with a single null-co disk
> attached. No idea how to r
On 03/07/2016 02:35 PM, Paolo Bonzini wrote:
>
>
> On 07/03/2016 13:29, Christian Borntraeger wrote:
>> Folks,
>>
>> I had a crash of a qemu guest in tracked_request_begin.
>> The testcase was a guest with ramdisk/kernel that reboots in a
>> loop. (about 10 times per second) with a single null-c
Folks,
I had a crash of a qemu guest in tracked_request_begin.
The testcase was a guest with ramdisk/kernel that reboots in a
loop. (about 10 times per second) with a single null-co disk
attached. No idea how to reproduce this, seems to be a lucky hit.
(gdb) bt
#0 0x101db5ba in tracked
On 07/03/2016 13:29, Christian Borntraeger wrote:
> Folks,
>
> I had a crash of a qemu guest in tracked_request_begin.
> The testcase was a guest with ramdisk/kernel that reboots in a
> loop. (about 10 times per second) with a single null-co disk
> attached.
Does it use a separate iothread?
