reported qemu error msg "KVM is too old to support ic-mode=dual,kernel-irqchip=on" indicates the
guest os is legacy, but that's not the case here, whereas kernel levels are near upstream which has support for xive.
My understanding of the env I used as below
Level | XIVE KVM support | XIVE support(in kernel or emulation)
--------------------------------------------------
L0 | Yes | Yes
L1 | No | Yes(booted with irqchip: in-kernel)
L2 | No | Yes
So, ideally when a L2 guest is started with ic-mode=dual,kernel-irqchip=on, we should have seen below error
(2) QEMU fails with ``kernel_irqchip requested but unavailable:
IRQ_XIVE capability must be present for KVM``
but we actually saw the reported one, which is misleading.
As per this the table https:/ /www.qemu. org/docs/ master/ specs/ppc- spapr-xive. html#kvm- negotiation
reported qemu error msg "KVM is too old to support ic-mode= dual,kernel- irqchip= on" indicates the
guest os is legacy, but that's not the case here, whereas kernel levels are near upstream which has support for xive.
My understanding of the env I used as below
Level | XIVE KVM support | XIVE support(in kernel or emulation) ------- ------- ------- ------- ------- ------- -
-------
L0 | Yes | Yes
L1 | No | Yes(booted with irqchip: in-kernel)
L2 | No | Yes
So, ideally when a L2 guest is started with ic-mode= dual,kernel- irqchip= on, we should have seen below error
(2) QEMU fails with ``kernel_irqchip requested but unavailable:
IRQ_XIVE capability must be present for KVM``
but we actually saw the reported one, which is misleading.