qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Atoosah <atoosaah@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: How to get target system display with qemu -nographic option?
Date: Mon, 21 Jul 2008 13:40:07 -0700	[thread overview]
Message-ID: <c3578ab90807211340m4dc19de7x7bc6f0c4c6da468a@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2274 bytes --]

Thank you guys for the explanation. I don't want to ssh as that will modify
the behavior of my kernel. The option -monitor requires a device, and so
"none" would be viewed as a device (which does not exist).

My goal is to run qemu and have my guests display available via the serial
line (for example /dev/ttyS0). In order to do this, it seems to me that the
guests grub.conf file console parameter needs to be modified (similar to
below); on the host,  qemu needs to be started with "console" option (as
shown below); finally, another terminal should be opened with serial port
capabilities (such as minicom).  Is this correct? If so, how do I get
minicom to connect?

- I've modified my guest kernel /boot/grub/grub.conf file as follows:
title Fedora ...
console=ttyS0,38400n8

- To start qemu the options I use are:
qemu -hda mydisk.img -m 512 -append "root=/dev/hda console=ttyS0" -nographic
-serial pty

- My minicom settings are similar to my grub.conf file, i.e. "Comm
Parameters" are 38400 8N1
If I start qemu in one terminal and minicom in the other, should my guests
display automatically show up in the minicom screen? If not, how do I get
minicom to connect to /dev/ttyS0? So far, my minicom shows as offline. (I've
also tried GtkTerm, with no success).

Thanks again.


> 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.
>
> 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
>
> On the guest. When you use -nographic, you get a (vritual) pc without
> a monitor, but with a serial port. If your Fedora is not set up to
> have a login on the serial port, you will see nothing when you connect
> a serial cable to the port. You can have login prompts both on serial
> and on screen.
>
> You could also ssh into the guest instead.
>
>
>

[-- Attachment #2: Type: text/html, Size: 2719 bytes --]

             reply	other threads:[~2008-07-21 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 20:40 Atoosah [this message]
2008-07-21 21:52 ` [Qemu-devel] Re: How to get target system display with qemu -nographic option? David Barrett
  -- strict thread matches above, loose matches on Subject: below --
2008-07-21 23:16 Vikram Hegde
2008-07-25 19:21 Atoosah
2008-07-26  1:03 Vikram Hegde
2008-07-26  3:13 Vikram Hegde

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=c3578ab90807211340m4dc19de7x7bc6f0c4c6da468a@mail.gmail.com \
    --to=atoosaah@gmail.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).