From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Huacai Chen" <chenhuacai@kernel.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: Could we document exact steps for loongson3-virt in the manual?
Date: Wed, 07 Apr 2021 09:37:36 +0100 [thread overview]
Message-ID: <8735w2wkra.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA8V94ac+UNcP6nKfNJQAxSzeY_dbpZx1tKa0xnXHhekEA@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Tue, 6 Apr 2021 at 14:23, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> 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.
>
> Oddly enough somebody on stackoverflow had the same problem for
> a different board (malta) the other day:
> https://stackoverflow.com/questions/66904366/qemu-system-mips-stuck-after-console-tty0-enabled/66910192
>
> As Jiaxun says, the problem is that your kernel command line says "send the
> console output to the virtual console on the graphics device (tty0)" but your
> QEMU command line is using a serial console and not trying to use graphics.
> So as soon as the kernel gets to the point where it can honour your request
> it disables the early-boot console and enables tty0 and then you don't
> see anything any more :-)
Doh - should have spotted that. I guess the -nographic doesn't prompt
the kernel enough to warn about switching to a non-existent graphics
device. I can get to the installer now although it fails later failing
to find kernel modules. I suspect this is a Debian problem with a
mismatch between installer and archives.
>
> thanks
> -- PMM
--
Alex Bennée
prev parent reply other threads:[~2021-04-07 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 13:06 Could we document exact steps for loongson3-virt in the manual? Alex Bennée
2021-04-07 3:47 ` Jiaxun Yang
2021-04-07 7:47 ` Peter Maydell
2021-04-07 8:37 ` Alex Bennée [this message]
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=8735w2wkra.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=chenhuacai@kernel.org \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--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).