qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Josef Moffett <moffett@secureit-mu.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Re: Nothing happens
Date: Sun, 12 Jun 2005 12:14:49 +0400	[thread overview]
Message-ID: <42ABEEF9.1020604@secureit-mu.com> (raw)

I have just joined the mail list after coming up with a problem similar 
to one I googled here and perhaps to which I can add a bit more 
information. Unfortunatly, I can only add a little more prescision to 
the problem rather than any answers, but perhaps Rudi Lippert can verify 
if this is happening to him too.

I have a problem after compiling qemu with SDL-devel and KQemu support.

The problem seems similar to  what has been posted and replied to in the 
following messages
http://www.mail-archive.com/qemu-devel@nongnu.org/msg00540.html

but I did find the following with the -monitor stdio; that when I did a 
screen dump qemu was running and dumping valid (linux, win 98 and winxp) 
screen images. I only had no access to these - in other words the 
emulator was working fine, both with and without kqemu, but there was no 
console or visual output with which to manipulate the emulated virtual 
machine. (ie no visual and no keyboard/mouse access to the (hidden) 
console.)
here is my configure output

using: qemu-0.7.0-i386.tar.gz
and : kqemu-0.6.2-1.tar.gz

downloaded on Sat 11/06/2005 around 22:oo

----------------
joe@anvard:~/qemu-0.7.0> ./configure
Install prefix    /usr/local
BIOS directory    /usr/local/share/qemu
binary directory  /usr/local/bin
Manual directory  /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path       /home/joe/qemu-0.7.0
C compiler        gcc
make              make
host CPU          i386
host big endian   no
target list       i386-user arm-user armeb-user sparc-user ppc-user 
i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu
gprof enabled     no
static build      no
SDL support       yes
SDL static link   no
mingw32 support   no
Adlib support     no
FMOD support      no
kqemu support     yes

KQEMU Linux module configuration:
kernel sources    /lib/modules/2.6.8-24.16-default/build
kbuild type       2.6
-----------------

I am running under Suse 9.2 and the precompiled binaries work right "out 
of the box" (even the network stuff which some people seem to be having 
trouble with) but are just a tad too slow for what I wanted to use qemu 
for so I wanted to try with kqemu built in.

I first just tried without the SDL-devel libs, but that was the same, 
and the above mentioned thread suggested that SDL may be a cause 
(although I suspect we may be talking of different problems). The thing 
is, once the virtual machine achieves a state of "completion" (ie 
windows gets to the login promt, or linux gets to the bash prompt - same 
problem there by the way) the cpu cycles disappear as the virtual 
machine is not doing any work at all. So perhaps the problem is the same?

Any help would be appreciated...

             reply	other threads:[~2005-06-12  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-12  8:14 Josef Moffett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-18 21:32 [Qemu-devel] Re: Nothing happens Rudi Lippert
2005-05-18 21:57 ` Struan Bartlett
2005-05-19  9:23   ` [Qemu-devel] " Rudi Lippert
2005-05-19 23:30     ` Struan Bartlett
2005-05-20  8:12     ` Oliver Gerlich

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=42ABEEF9.1020604@secureit-mu.com \
    --to=moffett@secureit-mu.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).