>> I *think* it happens because I'm changing guest page tables from outside
>> (i.e. host application), and the new intel pgtable optimization bits
>> don't expect that (yes, it is a vt box).
>
> Well, the older implementation doesn't expect that either. You can
> disable the optimization with by
Gerd Hoffmann wrote:
> Avi Kivity wrote:
>
>> You can call kvm_disable_irqchip_creation() to kill in-kernel pic and
>> friends.
>>
>> (the logic is inverted -- the function should be
>> kvm_enable_irqchip_creation() so that this problem would not occur)
>>
>
> Ok, will try, next question fi
Avi Kivity wrote:
> You can call kvm_disable_irqchip_creation() to kill in-kernel pic and
> friends.
>
> (the logic is inverted -- the function should be
> kvm_enable_irqchip_creation() so that this problem would not occur)
Ok, will try, next question first though as I'm running in trouble much
e
Gerd Hoffmann wrote:
> Avi Kivity wrote:
>
>> Only one fix, but an important one. It fixes booting of newer Linux
>> versions, which experienced disk and keyboard problems without
>> -no-kvm-irqchip.
>>
>> As usual, if you have an issue please try with -no-kvm-irqchip and report.
>>
>
> Up
Avi Kivity wrote:
> Only one fix, but an important one. It fixes booting of newer Linux
> versions, which experienced disk and keyboard problems without
> -no-kvm-irqchip.
>
> As usual, if you have an issue please try with -no-kvm-irqchip and report.
Updated from -41. Now my libkvm-using-tool's
Only one fix, but an important one. It fixes booting of newer Linux
versions, which experienced disk and keyboard problems without
-no-kvm-irqchip.
As usual, if you have an issue please try with -no-kvm-irqchip and report.
Changes since kvm-42:
- fix ioapic edge-triggered interrupt handling
Not
