From: Peter Maydell <peter.maydell@linaro.org>
To: Sebastian Ott <sebott@redhat.com>
Cc: qemu-devel@nongnu.org, "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: hanging process with commit 69562648f9 ("vl: revert behaviour for -display none")
Date: Mon, 27 Nov 2023 14:37:47 +0000 [thread overview]
Message-ID: <CAFEAcA9c6Guo-juq37Lkfav9TR9zec_ymQkPdq4wSAmHRSb2-g@mail.gmail.com> (raw)
In-Reply-To: <531d4099-747f-5ab5-8c9c-30c50e6115c8@redhat.com>
On Mon, 27 Nov 2023 at 13:08, Sebastian Ott <sebott@redhat.com> wrote:
>
> On Mon, 27 Nov 2023, Peter Maydell wrote:
> > On Mon, 27 Nov 2023 at 12:29, Sebastian Ott <sebott@redhat.com> wrote:
> >> qemu fails to start a guest using the following command (the process just
> >> hangs): qemu-system-aarch64 -machine virt -cpu host -smp 4 -m 8192
> >> -kernel /boot/vmlinuz-6.7.0-rc1 -initrd ~/basic.img -append "root=/dev/ram
> >> console=ttyAMA0" -enable-kvm -device virtio-gpu,hostmem=2G -display none
> >>
> >> ..which I've used to debug a potential virtio-gpu issue. Bisect points to
> >> 69562648f9 ("vl: revert behaviour for -display none")
> >
> > Is it actually hanging, or is the guest starting up fine but
> > outputting to a serial port which you haven't directed anywhere?
>
> Ough, that's indeed the case. I only had a quick glance at the bt in gdb
> and obviously misinterpreted what I got there.
>
> > The commandline is a bit odd because it doesn't set up any of:
> > * a serial terminal
> > * a graphical window/display
> > * network forwarding that would allow ssh into the guest
> >
> > If you add '-serial stdio' do you see the guest output?
>
> I do. I was using the serial terminal which got setup implicitly I guess.
Yep. The issue fixed by 69562648f9 is that we briefly incorrectly
made "-display none" do more than just "disable the display window".
The revert brings us back to the normal behaviour that if you
want a serial port you need to ask for it. (Or use the -nographic
option, which is a legacy 'do what I mean' option that does
multiple things at once including turning off the GUI window,
and adding a serial terminal and a monitor multiplexed onto stdio.
But personally I find it clearer to explicitly ask for all
this stuff via '-display none -serial ...' etc.)
-- PMM
prev parent reply other threads:[~2023-11-27 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 12:29 hanging process with commit 69562648f9 ("vl: revert behaviour for -display none") Sebastian Ott
2023-11-27 12:36 ` Peter Maydell
2023-11-27 13:08 ` Sebastian Ott
2023-11-27 14:37 ` Peter Maydell [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=CAFEAcA9c6Guo-juq37Lkfav9TR9zec_ymQkPdq4wSAmHRSb2-g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sebott@redhat.com \
/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).