From: Sean Christopherson <seanjc@google.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH] x86/run: Use separate "-accel" option to configure the accelerator
Date: Tue, 2 Jun 2026 13:22:09 -0700 [thread overview]
Message-ID: <ah87cbm6mxt0aWWk@google.com> (raw)
In-Reply-To: <ah7mxim83BLuF-Ia@google.com>
On Tue, Jun 02, 2026, Sean Christopherson wrote:
> On Tue, Jun 02, 2026, Xiaoyao Li wrote:
> > On 5/29/2026 8:09 AM, Xiaoyao Li wrote:
> > > On 5/28/2026 9:00 PM, Sean Christopherson wrote:
> > > > On Thu, May 28, 2026, Xiaoyao Li wrote:
> > > > > When configuring accelerator via machine's "accel" property, it cannot
> > > > > pass additional ACCEL_PROPS. For example, it hits following error when
> > > > > configuring KVM with "notify-vmexit":
> > > > >
> > > > > # ACCEL="kvm,notify-vmexit=internal-error" ./x86-run x86/apic.c
> > > > > # qemu-system-x86_64: Property
> > > > > 'pc-i440fx-11.1-machine.notify- vmexit' not found
> > > > >
> > > > > Switch to use separate "-accel" option to configure the accelerator.
> > > > >
> > > > > Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
> > > > > ---
> > > > > x86/run | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/x86/run b/x86/run
> > > > > index dd38f14c871f..a68d469dd1b8 100755
> > > > > --- a/x86/run
> > > > > +++ b/x86/run
> > > > > @@ -43,7 +43,7 @@ fi
> > > > > pit="-global kvm-pit.lost_tick_policy=discard"
> > > > > command="${qemu} --no-reboot -nodefaults $pit $pc_testdev
> > > > > -display none -serial stdio $pci_testdev"
> > > > > -command+=" -machine accel=$ACCEL$ACCEL_PROPS"
> > > > > +command+=" -accel $ACCEL$ACCEL_PROPS"
> > > >
> > > > This breaks my setup for specifying kernel_irqchip=split.
> > > >
> > > > qemu: -accel kvm,kernel_irqchip=split: Property 'kvm-
> > > > accel.kernel_irqchip' not found
> > >
> > > If you switch "kernel_irqchip" to "kernel-irqchip", it should work again.
> > >
> > > This needs to be fixed on QEMU side. I'll look at it.
> >
> > Well, I feel hard to justify a QEMU "fix" for it.
> >
> > "kernel_irqchip" was a property of "machine" in old QEMU, and QEMU switched
> > it to "kernel-irqchip" automatically.
> >
> > Then QEMU moved it to be a property of "accel", while keeping the
> > compatibility when users configure it via "machine" that QEMU internally
> > setting it to accel's property in this case.
> >
> > However, "kernel_irqchip" is only valid on "machine", but not on "accel".
> >
> > For this KVM unit test issue, do we need to add workaround to keep your
> > (work-by-accident) usage working? or just kill it?
>
> Nah, just switch to "accel" and call it good. I'm likely the one and only user
> of kernel_irqchip.
There's another problem: the CET and LAM tests force -enable-kvm:
[cet]
file = cet.flat
arch = x86_64
smp = 2
qemu_params = -enable-kvm -m 2048 -cpu host
[lam]
file = lam.flat
arch = x86_64
qemu_params = -enable-kvm -cpu max
Which apparently is wired up to "-machine accel=" under the hood, because they
get skipped with:
SKIP cet (qemu: The -accel and "-machine accel=" options are incompatible)
SKIP lam (qemu: The -accel and "-machine accel=" options are incompatible)
prev parent reply other threads:[~2026-06-02 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 7:17 [kvm-unit-tests PATCH] x86/run: Use separate "-accel" option to configure the accelerator Xiaoyao Li
2026-05-28 13:00 ` Sean Christopherson
2026-05-29 0:09 ` Xiaoyao Li
2026-05-29 16:03 ` Sean Christopherson
2026-06-02 10:00 ` Xiaoyao Li
2026-06-02 14:20 ` Sean Christopherson
2026-06-02 20:22 ` Sean Christopherson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ah87cbm6mxt0aWWk@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=xiaoyao.li@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox