From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [BUG] No irqchip created after commit 11bc4a13d1f4 ("kvm: convert "-machine kernel_irqchip" to an accelerator property")
Date: Fri, 20 Dec 2019 16:39:11 +0100 [thread overview]
Message-ID: <CABgObfbKM_QNXJaAk7m2JYOoZgAAa+98d2x3==eYUkTi_CGw6Q@mail.gmail.com> (raw)
In-Reply-To: <87eewz84ts.fsf@vitty.brq.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
No, absolutely not. I was sure I had tested it, but I will take a look.
Paolo
Il ven 20 dic 2019, 15:11 Vitaly Kuznetsov <vkuznets@redhat.com> ha scritto:
> I apologize if this was already reported,
>
> I just noticed that with the latest updates QEMU doesn't start with the
> following configuration:
>
> qemu-system-x86_64 -name guest=win10 -machine pc,accel=kvm -cpu
> host,hv_vpindex,hv_synic ...
>
> qemu-system-x86_64: failed to turn on HyperV SynIC in KVM: Invalid argument
> qemu-system-x86_64: kvm_init_vcpu failed: Invalid argument
>
> If I add 'kernel-irqchip=split' or ',kernel-irqchip=on' it starts as
> usual. I bisected this to the following commit:
>
> commit 11bc4a13d1f4b07dafbd1dda4d4bf0fdd7ad65f2 (HEAD, refs/bisect/bad)
> Author: Paolo Bonzini <pbonzini@redhat.com>
> Date: Wed Nov 13 10:56:53 2019 +0100
>
> kvm: convert "-machine kernel_irqchip" to an accelerator property
>
> so aparently we now default to 'kernel_irqchip=off'. Is this the desired
> behavior?
>
> --
> Vitaly
>
>
[-- Attachment #2: Type: text/html, Size: 1590 bytes --]
next prev parent reply other threads:[~2019-12-20 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 14:11 [BUG] No irqchip created after commit 11bc4a13d1f4 ("kvm: convert "-machine kernel_irqchip" to an accelerator property") Vitaly Kuznetsov
2019-12-20 15:39 ` Paolo Bonzini [this message]
2019-12-28 9:32 ` [PATCH] accel/kvm: Make "kernel_irqchip" default on Xiaoyao Li
2019-12-28 10:02 ` Paolo Bonzini
2019-12-28 10:16 ` Xiaoyao Li
2019-12-28 10:57 ` Paolo Bonzini
2019-12-28 11:14 ` Xiaoyao Li
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='CABgObfbKM_QNXJaAk7m2JYOoZgAAa+98d2x3==eYUkTi_CGw6Q@mail.gmail.com' \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vkuznets@redhat.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;
as well as URLs for NNTP newsgroup(s).