From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KL2B1-0006g2-CD for qemu-devel@nongnu.org; Mon, 21 Jul 2008 16:40:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KL2B0-0006ef-7a for qemu-devel@nongnu.org; Mon, 21 Jul 2008 16:40:10 -0400 Received: from [199.232.76.173] (port=58960 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KL2Az-0006eN-IJ for qemu-devel@nongnu.org; Mon, 21 Jul 2008 16:40:09 -0400 Received: from fg-out-1718.google.com ([72.14.220.157]:34879) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KL2Az-0000Hq-9p for qemu-devel@nongnu.org; Mon, 21 Jul 2008 16:40:09 -0400 Received: by fg-out-1718.google.com with SMTP id l26so811941fgb.8 for ; Mon, 21 Jul 2008 13:40:07 -0700 (PDT) Message-ID: Date: Mon, 21 Jul 2008 13:40:07 -0700 From: Atoosah MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2965_6456052.1216672807557" Subject: [Qemu-devel] Re: How to get target system display with qemu -nographic option? Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_2965_6456052.1216672807557 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. > > > ------=_Part_2965_6456052.1216672807557 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
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.



------=_Part_2965_6456052.1216672807557--