From: sebastiano lomuscio <slomuscio@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu high cpu load when -monitor stdio and fifo is used
Date: Sat, 22 Oct 2005 17:43:18 +0200 [thread overview]
Message-ID: <8aa9b2c50510220843h485bd247p@mail.gmail.com> (raw)
Please help me.!
I'm trying to send command to the qemu monitor via a FIFO device in
order to stop,start and save the vm state in a file from another
process .
The script I'm using is the following:
#!/bin/bash
mkfifo /tmp/serin
qemu -boot c -cdrom win2000.iso -hda win2000s.img -m 256
-localtime -snapshot -nographic -serial null -monitor stdio -n
./qemu-ifup < /tmp/serin &
exit
When this script is started the emulator doesn't start.
I have to send the following command via /tmp/serin
echo "start " > /tmp/serin
After that, the emulator runs fine but the cpu load is very high (near
99%) also if i send the "stop" command : echo "stop" > /tmp/serin
the emulation get stopped but the cpu load remain high.
The emulated system is windows 2000 server
Any help is really appreciated
Sebastiano
reply other threads:[~2005-10-22 15:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8aa9b2c50510220843h485bd247p@mail.gmail.com \
--to=slomuscio@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).