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

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

Yay! I've almost got it. I'd appreciate a bit more help for the last few
steps.

Thank you David for pointing out the command options wouldn't be recognized.
Now, I see how it wouldn't make sense to pass in commands to a bootable
image. I had previously added the same console parameters to grub, but the
kernel was not recognizing it.

Vikram, thank you telling me about the -B option. That was the key :-) My
kernel is not that old, 2.6.11, and so needed that option. Now I get the
boot up messaged on my terminal!

-- But, after bootup messages are done, I do not see the login screen. After
the last bootup messages are done, shouldn't the login screen magically
appear on the terminal? I don't see anyting after the last bootup message
of  "Starting HAL daemon: [  OK ]". Why would that be?

-- Also, I'm easily able to switch to Qemu's Command window with Ctrl-a c,
but cannot switch back to console. Shouldn't I be able to?

Below I've listed the changes (on a 2.6.11 Fedora Core guest) I've made in
case someone needs to refer to it:

A) modified grub.conf as follows:
default=0
timout=10
serial --unit=0 --speed=9600
terminal serial console
title something
         root (hd0,0)
         kernel some_stuff -B console=ttyS0
         initrd something

B) In /etc/inittab mgetty was giving me respawning error so I removed the
below line. It seems that mgetty was not being recognized.
#T0:2345:respawn:/sbin/mgetty dev=ttyS0 b 9600 ...

Vikram, have you tried mingetty? I don't have getty available.

C) Running qemu as follows:
$ qemu  -hda myboot.img -m 512 -nographic

-----------------------------------------------------------------------
Note: my last last boot message are:
Checking filesystems
Checking all file systems.
...
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
Enabling swap space:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Checking for new hardware [  OK  ]
Starting pcmcia:  [  OK  ]
Starting system logger: [  OK  ]
...
Starting system message bus: [  OK  ]
Starting HAL daemon: [  OK  ]

-----------------------------------------------------------------------

Thank you.



> Hi,
>
> There are two components to making output appear on the serial port.
>
> 1. Getting GRUB to output (the menu etc.) to the serial port. You can do
> this via the following global directive
>          serial --unit=0 --speed=9600
>          terminal serial
> Add this as a "global" entry to grub.conf  i.e. at the same level as your
> "default" and "timeout" directives (i.e. outside the title block)
>
> 2. Getting the Linux kernel to output console to the serial port (once it
> takes over from GRUB). I don't
>    have experience doing console redirection on Linux but on Opensolaris we
> do it via a property specified via
>    a -B option specified  on the "kernel" line.
>
> Atoosah wrote:
> > title Fedora ....
> > console=ttyS0   ....
>
> This is unlikely to work - the "console" token is interpreted by GRUB as a
> command and there is no "console" command in legacy GRUB.
>
> Vikram
>
> ----- Original Message ----
>
> Ah, you're going well outside my area of familiarity -- I've never set
> up a console terminal over a serial line physically nor virtually.
>
> However, I notice you're using the "-append" line -- I made that mistake
> as well, but learned that you can only use "-append" if you're also
> using "-kernel" and "-initrd".  Basically, you can wholly specify the
> kernel in the qemu command line, or you need to go with the kernel
> defined by GRUB, but you can't selectively override grub using the
> command line.
>
> Other than that, I'm not sure how to help.  Good luck!
>
> -david
>
>

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

             reply	other threads:[~2008-07-25 19:21 UTC|newest]

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