All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Rasch <phil@supstitches.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Problem with high load average when using -nographic with qemu in background
Date: Sat, 6 Jan 2007 10:08:09 -0700	[thread overview]
Message-ID: <200701061008.09809.phil@supstitches.com> (raw)

Sorry to bother you with this. I did try the qemu forums first.

I am having trouble running a trixbox/centos guest under an ubuntu host. Both 
completely uptodate installs of the OS's. I am using Qemu 0.8.2 with 
kqemu-1.3.0pre9.

If I start the qemu without -nographic interactively the VM runs well, and the 
hostOS maintains a load average of about 0.1

Trouble comes when I add -nographic to the command line, and redirect stdout 
and stderrout to a logfile. (I do this so I can start qemu from during the 
boot up process and run the VM in background all the time.

If I start qemu like this (from an interactive shell (tcsh))
qemu -m 256 -localtime -net nic -net tap -nographic trixbox.img \ 
>&! /tmp/qemulog &

It will stop on
 + Suspended[tty output]

If I also redirect stdin (eg adding "< /dev/null") it then starts and runs 
fine, but the hostOS load climbs to 1.0 and higher (depending on what the 
guest is doing, and the performance of the VM is seriously impaired.

I can ssh into the machine under both scenarios and see that the guest thinks 
it is fine, but it is really burdening the hostOS.

Looking through /var/log/messages on the guest shows that I have (I think) 
successfully set io to go through /dev/ttyS0, eg.

Jan  6 09:46:49 asterisk1 kernel: Kernel command line: ro console=ttyS0,9600n8 
vga=normal root=LABEL=/

Can anyone offer advice?

Phil

             reply	other threads:[~2007-01-06 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06 17:08 Phil Rasch [this message]
2007-01-06 17:52 ` [Qemu-devel] Problem with high load average when using -nographic with qemu in background Mulyadi Santosa
2007-01-06 22:03 ` Paul Brook
2007-01-07  5:03   ` Phil Rasch
2007-01-07 11:42     ` Paul Brook

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=200701061008.09809.phil@supstitches.com \
    --to=phil@supstitches.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.