> On 1 Apr 2019, at 20:28, Vitaly Kuznetsov wrote:
>
> Liran Alon writes:
>
>>> On 1 Apr 2019, at 18:58, Vitaly Kuznetsov wrote:
>>>
>>> Liran Alon writes:
>>>
> On 1 Apr 2019, at 16:36, Vitaly Kuznetsov wrote:
>
> It was found that Hyper-V 2016 on KVM in some
Liran Alon writes:
>> On 1 Apr 2019, at 18:58, Vitaly Kuznetsov wrote:
>>
>> Liran Alon writes:
>>
On 1 Apr 2019, at 16:36, Vitaly Kuznetsov wrote:
It was found that Hyper-V 2016 on KVM in some configurations (q35 machine +
piix4-usb-uhci) hangs on boot. Trace analysis
> On 1 Apr 2019, at 18:58, Vitaly Kuznetsov wrote:
>
> Liran Alon writes:
>
>>> On 1 Apr 2019, at 16:36, Vitaly Kuznetsov wrote:
>>>
>>> It was found that Hyper-V 2016 on KVM in some configurations (q35 machine +
>>> piix4-usb-uhci) hangs on boot. Trace analysis led us to the conclusion
Liran Alon writes:
>> On 1 Apr 2019, at 16:36, Vitaly Kuznetsov wrote:
>>
>> It was found that Hyper-V 2016 on KVM in some configurations (q35 machine +
>> piix4-usb-uhci) hangs on boot. Trace analysis led us to the conclusion that
>> it is mishandling level-triggered interrupt performing EOI
On 01/04/19 17:13, Vitaly Kuznetsov wrote:
>>> +trace_ioapic_eoi_delayed_reassert(vector);
>>> +timer_mod(s->timer,
>>> + qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) +
>>> +
Paolo Bonzini writes:
> On 01/04/19 15:36, Vitaly Kuznetsov wrote:
...
>> static void ioapic_set_irq(void *opaque, int vector, int level)
>> {
>> IOAPICCommonState *s = opaque;
>> @@ -227,7 +236,28 @@ void ioapic_eoi_broadcast(int vector)
>>
> On 1 Apr 2019, at 16:36, Vitaly Kuznetsov wrote:
>
> It was found that Hyper-V 2016 on KVM in some configurations (q35 machine +
> piix4-usb-uhci) hangs on boot. Trace analysis led us to the conclusion that
> it is mishandling level-triggered interrupt performing EOI without fixing
> the
On 01/04/19 15:36, Vitaly Kuznetsov wrote:
> It was found that Hyper-V 2016 on KVM in some configurations (q35 machine +
> piix4-usb-uhci) hangs on boot. Trace analysis led us to the conclusion that
> it is mishandling level-triggered interrupt performing EOI without fixing
> the root cause. This
It was found that Hyper-V 2016 on KVM in some configurations (q35 machine +
piix4-usb-uhci) hangs on boot. Trace analysis led us to the conclusion that
it is mishandling level-triggered interrupt performing EOI without fixing
the root cause. This causes immediate re-assertion and L2 VM (which is
