From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michal Suchánek" <msuchanek@suse.de>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: hanji unit <hanjiunit@gmail.com>,
qemu-discuss <qemu-discuss@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU without X11 support
Date: Sun, 15 Oct 2017 17:39:59 +0200 [thread overview]
Message-ID: <b389eb6f-7a3a-6d63-95f2-f0b526de3afa@redhat.com> (raw)
In-Reply-To: <20171015160141.75690306@naga>
On 15/10/2017 16:01, Michal Suchánek wrote:
>>> ./configure --disable-gtk --disable-sdl --disable-opengl
>> You can also use the runtime -display options (assuming
>> your development environment has the libraries
>> and your runtime environment has them installed, there's
>> no harm in having a QEMU that was built with gtk support
>> and not using the gtk UI.)
>>
>> There are a couple of parts to this:
>> (1) does your guest OS require a graphics device?
>> (eg typically Windows does, ARM Linux will happily use
>> a serial port)
>> (2) if you do need a graphics device, where does the
>> output go?
>> (eg you can tell QEMU to just not show graphics at
>> all with -display none, use -display vnc to for a VNC
>> server, etc. Some of the -display options will use
>> X11, and some won't.)
> iirc you also need to specify -nographic so qemu does not try to use the
> X11 GUI to display your serial output.
Right. -nographic's effects can be described in terms of other
command-line options, but it is pretty hairy. The effects fall in two
categories:
1) -nographic is a shortcut for "-display none -machine graphics=off"
2) it changes the default character device backend from "vc:80Cx24C"
(80x24 graphical console) to either "mon:stdio" or "stdio", except for
the parallel port whose default becomes simply "null".
Paolo
next prev parent reply other threads:[~2017-10-15 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:25 [Qemu-devel] QEMU without X11 support hanji unit
2017-10-13 7:00 ` Gerd Hoffmann
2017-10-13 16:08 ` Peter Maydell
2017-10-15 14:01 ` Michal Suchánek
2017-10-15 15:39 ` Paolo Bonzini [this message]
2017-10-14 16:38 ` Philippe Mathieu-Daudé
2017-10-14 17:18 ` Peter Maydell
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=b389eb6f-7a3a-6d63-95f2-f0b526de3afa@redhat.com \
--to=pbonzini@redhat.com \
--cc=hanjiunit@gmail.com \
--cc=kraxel@redhat.com \
--cc=msuchanek@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).