From: "Michal Suchánek" <msuchanek@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
hanji unit <hanjiunit@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-discuss <qemu-discuss@nongnu.org>
Subject: Re: [Qemu-devel] QEMU without X11 support
Date: Sun, 15 Oct 2017 16:01:41 +0200 [thread overview]
Message-ID: <20171015160141.75690306@naga> (raw)
In-Reply-To: <CAFEAcA9Vmrz3NTfJcSteyxvRvtb3VuCXZd=aOTL-GrWL3cm8bg@mail.gmail.com>
On Fri, 13 Oct 2017 17:08:49 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 13 October 2017 at 08:00, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > On Thu, 2017-10-12 at 16:25 -0400, hanji unit wrote:
> >> Hello, is it possible to run (or rebuild modifying build flags)
> >> QEMU without support for X11 window system integration?
> >
> > ./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.
HTH
Michal
next prev parent reply other threads:[~2017-10-15 14:01 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 [this message]
2017-10-15 15:39 ` Paolo Bonzini
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=20171015160141.75690306@naga \
--to=msuchanek@suse.de \
--cc=hanjiunit@gmail.com \
--cc=kraxel@redhat.com \
--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).