From: Andreas Schwab <schwab@suse.de>
To: kvm-riscv@lists.infradead.org
Subject: [6.6 regression] qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error -1
Date: Thu, 09 Nov 2023 10:19:20 +0100 [thread overview]
Message-ID: <mvmv8ab473b.fsf@suse.de> (raw)
v6.6 broke KVM with qemu 8.1.2.
$ qemu-system-riscv64 -cpu rv64 -machine virt,accel=kvm
qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error -1
openat(AT_FDCWD, "/dev/kvm", O_RDWR|O_CLOEXEC) = 9
ioctl(9, _IOC(_IOC_NONE, 0xae, 0x1, 0), 0) = 10
ioctl(10, _IOC(_IOC_NONE, 0xae, 0x41, 0), 0) = 11
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = 0
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = 0
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = 0
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = 0
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = 0
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = 0
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = 0
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = 0
ioctl(11, _IOC(_IOC_WRITE, 0xae, 0xab, 0x10), 0x7fffd101e3f8) = -1 ENOENT (No such file or directory)
write(2, "qemu-system-riscv64:", 20qemu-system-riscv64:) = 20
write(2, " ", 1 ) = 1
write(2, "Unable to read ISA_EXT KVM regis"..., 51Unable to read ISA_EXT KVM register ssaia, error -1) = 51
write(2, "\n", 1
) = 1
close(11) = 0
close(10) = 0
close(9) = 0
exit_group(1) = ?
+++ exited with 1 +++
--
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next reply other threads:[~2023-11-09 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 9:19 Andreas Schwab [this message]
2023-11-09 15:45 ` [6.6 regression] qemu-system-riscv64: Unable to read ISA_EXT KVM register ssaia, error -1 Palmer Dabbelt
2023-11-13 8:45 ` Andreas Schwab
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=mvmv8ab473b.fsf@suse.de \
--to=schwab@suse.de \
--cc=kvm-riscv@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.