From: David Barrett <dbarrett@quinthar.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to get target system display with qemu -nographic option?
Date: Thu, 17 Jul 2008 17:10:02 -0700 [thread overview]
Message-ID: <487FDF5A.1010200@quinthar.com> (raw)
In-Reply-To: <c3578ab90807171650n6f47580bm7c7a5f790da2a14@mail.gmail.com>
Atoosah wrote:
> When -nographic is specified, no graphical window is created. The only
> way to see the graphics window is using the VNC option.
>
> If I run the program with graphics enabled (i.e. no -nographic option) I
> get the login prompt and then the password. From then on, the display is
> in shell prompt mode. So, does -nographic mean that I won't be able to
> access this display? If so, it seems very limiting without being able to
> run experiments on our guest machine.
Ah, "graphics" means "display" -- it doesn't matter whether your guest
VM is running X or using a simple terminal, it all looks like one big
graphic to qemu.
Said another way, "-nographic" disables the display entirely, whether
that display is used for graphics or text.
> Furthermore, when -nographic is specified, I think "-monitor" defaults
> to "serial", meaning the actual serial output is overridden by the qemu
> monitor. To change this, look at "-monitor" and direct it somewhere
> else (such as to a TCP stream).
>
> I'd appreciate if you'd explain a bit more what you mean by "serial
> output is overridden by the qemu
> monitor"..
The "monitor" is the command-line interface to control qemu (start and
stop the VM, snapshots, etc). Normally, you can get to it with the
Control-Alt key combination: the display window switches to a terminal
showing the qemu monitor.
However, when "-nographic" is specified, there is no display window.
So, it pretends you specified "-monitor serial", which enables access to
the qemu monitor via the virtual serial cable. Unfortunately, that
means that you can no longer access the *real* virtual serial cable.
So, when you specify -nographic, I think if you just also specify
"-monitor none" then it'll disable the qemu monitor entirely and leave
the virtual serial port alone, letting you log on to your VM through the
virtual serial cable as you expect.
I *think* this is accurate, but I honestly haven't logged on to a qemu
vm via the serial port before (I just set up SSH), so there's some
guesswork involved. Take a look at the documentation for "-serial" and
"-monitor" and that should shed some light.
> Does this help?
>
>
> Thank you. I'm still looking at the vnc option. Just to make sure the
> /etc/inittab that is modified (with 7:2345:respawn:/sbin/mgetty ttyS0
> 9600 vt100-nav) should be the guests or the hosts? I'm a newbie in this
> area, so any help would be appreciated.
I don't know what you're trying to do with /etc/inittab. That doesn't
mean it's wrong, it just means I've never found it necessary to go that
route. I'm guessing you should probably undo all your changes there and
just stick with whatever was the default, and then use the "-nographic
-monitor none" option I mention above.
-david
next prev parent reply other threads:[~2008-07-18 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 23:50 [Qemu-devel] How to get target system display with qemu -nographic option? Atoosah
2008-07-18 0:10 ` David Barrett [this message]
2008-07-18 3:09 ` andrzej zaborowski
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 18:07 Atoosah
2008-07-17 21:33 ` David Barrett
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=487FDF5A.1010200@quinthar.com \
--to=dbarrett@quinthar.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).