From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: mips system emulation failure with virtio
Date: Tue, 05 Sep 2023 14:59:57 +0100 [thread overview]
Message-ID: <87pm2whfyn.fsf@linaro.org> (raw)
In-Reply-To: <4f2a4b734b20b80857d56af986335f78a92a0fff.camel@linuxfoundation.org>
Richard Purdie <richard.purdie@linuxfoundation.org> writes:
> With qemu 8.1.0 we see boot hangs fox x86-64 targets.
>
> These are fixed by 0d58c660689f6da1e3feff8a997014003d928b3b (softmmu:
> Use async_run_on_cpu in tcg_commit) but if I add that commit, mips and
> mips64 break, hanging at boot unable to find a rootfs.
(Widen CC list)
>
> We use virtio for network and disk and both of those change in the
> bootlog from messages like:
>
> [ 1.726118] virtio-pci 0000:00:13.0: enabling device (0000 -> 0003)
> [ 1.728864] virtio-pci 0000:00:14.0: enabling device (0000 -> 0003)
> [ 1.729948] virtio-pci 0000:00:15.0: enabling device (0000 -> 0003)
> ...
> [ 2.162148] virtio_blk virtio2: 1/0/0 default/read/poll queues
> [ 2.168311] virtio_blk virtio2: [vda] 1184242 512-byte logical
>
> to:
>
> [ 1.777051] virtio-pci 0000:00:13.0: enabling device (0000 -> 0003)
> [ 1.779822] virtio-pci 0000:00:14.0: enabling device (0000 -> 0003)
> [ 1.780926] virtio-pci 0000:00:15.0: enabling device (0000 -> 0003)
> ...
> [ 1.894852] virtio_rng: probe of virtio1 failed with error -28
> ...
> [ 2.063553] virtio_blk virtio2: 1/0/0 default/read/poll queues
> [ 2.064260] virtio_blk: probe of virtio2 failed with error -28
> [ 2.069080] virtio_net: probe of virtio0 failed with error -28
>
>
> i.e. the virtio drivers no longer work.
Interesting, as you say this seems to be VirtIO specific as the baseline
tests (using IDE) work fine:
➜ ./tests/venv/bin/avocado run ./tests/avocado/tuxrun_baselines.py:test_mips64
JOB ID : 71f3e3b7080164b78ef1c8c1bb6bc880932d8c9b
JOB LOG : /home/alex/avocado/job-results/job-2023-09-05T15.01-71f3e3b/job.log
(1/2) ./tests/avocado/tuxrun_baselines.py:TuxRunBaselineTest.test_mips64: PASS (12.19 s)
(2/2) ./tests/avocado/tuxrun_baselines.py:TuxRunBaselineTest.test_mips64el: PASS (11.78 s)
RESULTS : PASS 2 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB TIME : 24.79 s
> I tested with current qemu master
> (17780edd81d27fcfdb7a802efc870a99788bd2fc) and mips is still broken
> there.
>
> Is this issue known about?
Could you raise a bug at:
https://gitlab.com/qemu-project/qemu/-/issues
I'm curious why MIPS VirtIO is affected but nothing else is...
>
> Cheers,
>
> Richard
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-09-05 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 13:19 mips system emulation failure with virtio Richard Purdie
2023-09-05 13:59 ` Alex Bennée [this message]
2023-09-05 14:50 ` Richard Purdie
2023-09-05 15:12 ` Philippe Mathieu-Daudé
2023-09-05 15:53 ` Richard Purdie
2023-09-05 16:46 ` Philippe Mathieu-Daudé
2023-09-05 16:50 ` Richard Purdie
2023-09-06 15:50 ` Philippe Mathieu-Daudé
2023-09-06 16:06 ` Philippe Mathieu-Daudé
2023-09-06 16:46 ` Richard Purdie
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=87pm2whfyn.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=jiaxun.yang@flygoat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=richard.purdie@linuxfoundation.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.