From: "Alex Bennée" <alex.bennee@linaro.org>
To: Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Subject: Could we document exact steps for loongson3-virt in the manual?
Date: Tue, 06 Apr 2021 14:06:57 +0100 [thread overview]
Message-ID: <87mtubwnsq.fsf@linaro.org> (raw)
Hi,
I was trying to bootstrap a Loongson3 Debian image but ran into some
roadblocks. Philippe pointed me at:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg768848.html
which gives a bit of detail but elides over details such as how to
handle block devices. AFAICT it should support virtio-blk although maybe
Debian bullseye doesn't support the target, it's hard to say:
./qemu-system-mips64el -M loongson3-virt -m 4096 -nographic -blockdev driver=raw,node-name=hd0,discard=unmap,file.driver=host_device,file.filename=/dev/zvol/hackpool-0/debian-bullseye-mips64le -device virtio-blk,drive=hd0 -kernel ./vmlinuz-5.9.0-4-loongson-3 -initrd initrd.gz -append "root=/dev/sda1 console=tty0 nokaslr"
Gets as far as:
[ 0.008641] printk: console [tty0] enabled
[ 0.009507] printk: bootconsole [early0] disabled
and then just goes silent. It would be nice if we could add enough
detail to the appropriate target-mips.rst to:
- give guidance on the best model to use for general purpose distros
- describe a common command line for such
- detail bootstraping a modern kernel
In the ARM section there is a nice "Choosing a board model" which
discusses what you want (probably "virt") and then we have varying
levels of detail for the various myriad zoo of ARM machines that are
emulated. I recently added sections to the versatile and vexpress
sections after going through similar pain trying to get those up and
running.
--
Alex Bennée
next reply other threads:[~2021-04-06 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 13:06 Alex Bennée [this message]
2021-04-07 3:47 ` Could we document exact steps for loongson3-virt in the manual? Jiaxun Yang
2021-04-07 7:47 ` Peter Maydell
2021-04-07 8:37 ` Alex Bennée
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=87mtubwnsq.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=chenhuacai@kernel.org \
--cc=f4bug@amsat.org \
--cc=jiaxun.yang@flygoat.com \
--cc=qemu-devel@nongnu.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 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).