From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, phil@supstitches.com
Subject: Re: [Qemu-devel] Problem with high load average when using -nographic with qemu in background
Date: Sun, 7 Jan 2007 11:42:31 +0000 [thread overview]
Message-ID: <200701071142.33309.paul@codesourcery.com> (raw)
In-Reply-To: <1168146212.15464.6.camel@quark>
On Sunday 07 January 2007 05:03, Phil Rasch wrote:
> Now that I know that I didn't completely miss the point, and may even
> have tried a reasonable thing, I have a question and a workaround.
>
> 1) Question: How do other people do this sort of thing? That is, start a
> virtual machine when the hostmachine is booted automatically? Or dont
> they worry about the load/performance issues?
I fixed qemu so it wasn't broken.
Paul
prev parent reply other threads:[~2007-01-07 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 17:08 [Qemu-devel] Problem with high load average when using -nographic with qemu in background Phil Rasch
2007-01-06 17:52 ` Mulyadi Santosa
2007-01-06 22:03 ` Paul Brook
2007-01-07 5:03 ` Phil Rasch
2007-01-07 11:42 ` Paul Brook [this message]
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=200701071142.33309.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=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 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).