* [Bug 1914748] [NEW] Confuse error message when KVM can not start requested CPU
@ 2021-02-05 10:21 Philippe Mathieu-Daudé
2021-02-05 10:29 ` [Bug 1914748] " Alex Bennée
2021-05-09 15:48 ` Philippe Mathieu-Daudé
0 siblings, 2 replies; 3+ messages in thread
From: Philippe Mathieu-Daudé @ 2021-02-05 10:21 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
As of commit 1ba089f2255, on Cavium CN8890 (ThunderX cores):
$ qemu-system-aarch64 -display none -accel kvm -M virt,gic-version=3 -accel kvm -cpu cortex-a57 --trace \*kvm_vcpu\*
kvm_vcpu_ioctl cpu_index 0, type 0x4020aeae, arg 0xffff9b7f9b18
qemu-system-aarch64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument
(same using "-cpu cortex-a53" or cortex-a72).
Explanation from Peter Maydell on IRC:
> using a specific cpu type will only work with KVM if the host CPU really is that
> exact CPU type, otherwise, use "-cpu host" or "-cpu max"
Having a better error description would help to understand the reason.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: arm ui
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914748
Title:
Confuse error message when KVM can not start requested CPU
Status in QEMU:
New
Bug description:
As of commit 1ba089f2255, on Cavium CN8890 (ThunderX cores):
$ qemu-system-aarch64 -display none -accel kvm -M virt,gic-version=3 -accel kvm -cpu cortex-a57 --trace \*kvm_vcpu\*
kvm_vcpu_ioctl cpu_index 0, type 0x4020aeae, arg 0xffff9b7f9b18
qemu-system-aarch64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument
(same using "-cpu cortex-a53" or cortex-a72).
Explanation from Peter Maydell on IRC:
> using a specific cpu type will only work with KVM if the host CPU really is that
> exact CPU type, otherwise, use "-cpu host" or "-cpu max"
Having a better error description would help to understand the reason.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1914748/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug 1914748] Re: Confuse error message when KVM can not start requested CPU
2021-02-05 10:21 [Bug 1914748] [NEW] Confuse error message when KVM can not start requested CPU Philippe Mathieu-Daudé
@ 2021-02-05 10:29 ` Alex Bennée
2021-05-09 15:48 ` Philippe Mathieu-Daudé
1 sibling, 0 replies; 3+ messages in thread
From: Alex Bennée @ 2021-02-05 10:29 UTC (permalink / raw)
To: qemu-devel
** Tags added: ui
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914748
Title:
Confuse error message when KVM can not start requested CPU
Status in QEMU:
New
Bug description:
As of commit 1ba089f2255, on Cavium CN8890 (ThunderX cores):
$ qemu-system-aarch64 -display none -accel kvm -M virt,gic-version=3 -accel kvm -cpu cortex-a57 --trace \*kvm_vcpu\*
kvm_vcpu_ioctl cpu_index 0, type 0x4020aeae, arg 0xffff9b7f9b18
qemu-system-aarch64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument
(same using "-cpu cortex-a53" or cortex-a72).
Explanation from Peter Maydell on IRC:
> using a specific cpu type will only work with KVM if the host CPU really is that
> exact CPU type, otherwise, use "-cpu host" or "-cpu max"
Having a better error description would help to understand the reason.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1914748/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 1914748] Re: Confuse error message when KVM can not start requested CPU
2021-02-05 10:21 [Bug 1914748] [NEW] Confuse error message when KVM can not start requested CPU Philippe Mathieu-Daudé
2021-02-05 10:29 ` [Bug 1914748] " Alex Bennée
@ 2021-05-09 15:48 ` Philippe Mathieu-Daudé
1 sibling, 0 replies; 3+ messages in thread
From: Philippe Mathieu-Daudé @ 2021-05-09 15:48 UTC (permalink / raw)
To: qemu-devel
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'invalid' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/239
** Changed in: qemu
Status: New => Invalid
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #239
https://gitlab.com/qemu-project/qemu/-/issues/239
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914748
Title:
Confuse error message when KVM can not start requested CPU
Status in QEMU:
Invalid
Bug description:
As of commit 1ba089f2255, on Cavium CN8890 (ThunderX cores):
$ qemu-system-aarch64 -display none -accel kvm -M virt,gic-version=3 -accel kvm -cpu cortex-a57 --trace \*kvm_vcpu\*
kvm_vcpu_ioctl cpu_index 0, type 0x4020aeae, arg 0xffff9b7f9b18
qemu-system-aarch64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument
(same using "-cpu cortex-a53" or cortex-a72).
Explanation from Peter Maydell on IRC:
> using a specific cpu type will only work with KVM if the host CPU really is that
> exact CPU type, otherwise, use "-cpu host" or "-cpu max"
Having a better error description would help to understand the reason.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1914748/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-05-09 15:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-05 10:21 [Bug 1914748] [NEW] Confuse error message when KVM can not start requested CPU Philippe Mathieu-Daudé
2021-02-05 10:29 ` [Bug 1914748] " Alex Bennée
2021-05-09 15:48 ` Philippe Mathieu-Daudé
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).