From: "Shane Brennan" <shanerb@soe.ucsc.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Problem Running QEMU, and passing new commands
Date: Sat, 3 Mar 2007 18:52:15 -0800 [thread overview]
Message-ID: <4f2c8b9a0703031852u62309c60s552804f1c9e131d9@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
Hi,
I have successfully integrated the statistical simulation package
SimPoint with QEMU. Now I wish to add some commands to QEMU so a user can
start or stop simulation. The goal is that at the QEMU command prompt, the
user could enter a command like start_simpoint or stop_simpoint. For
example:
(qemu) start_simpoint
SimPoint started!
(qemu)
.... /*Time passes.. */
(qemu) stop_simpoint
SimPoint stopped!
I am curious where I would edit QEMU to look for such commands, some point
in the code where I can see what command is passed to QEMU, and do something
such as
"if strcmp(command, "start_simpoint") == 0"
Also, there is another problem, I am able to run QEMU if I tell it to load
and boot a linux image. But I am not able to simply boot up to the (qemu)
prompt and enter commands from there. I try running QEMU using the following
commands:
qemu-img create -f qcow c.img 3G
./i386-softmmu/qemu -hda c.img -L ./pc-bios/ -nographic
and it loads up to the (qemu) prompt. However, at that point everything
freezes. I am running QEMU on a linux host with a dual 64-bit AMD
processors, and doing this over an SSH connection.
If anyone has any advice on how I can get QEMU to boot to the point where I
can enter commands, and how I can monitor these commands within the source
code, I would very much appreciate the assistance.
~Shane Brennan
UC Santa Cruz
[-- Attachment #2: Type: text/html, Size: 1477 bytes --]
next reply other threads:[~2007-03-04 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 2:52 Shane Brennan [this message]
2007-03-04 10:05 ` [Qemu-devel] Problem Running QEMU, and passing new commands maestro
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=4f2c8b9a0703031852u62309c60s552804f1c9e131d9@mail.gmail.com \
--to=shanerb@soe.ucsc.edu \
--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).