qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] -kernel-kqemu with linux guest and vnc
Date: Sun, 26 Mar 2006 15:17:38 +0400	[thread overview]
Message-ID: <44267852.7050000@wasp.net.au> (raw)

G'day all,

The -kernel-kqemu with linux guest bug is still at large, however it appears if you compile your 
kernel with gcc-3.2.2 it will work. (yay!). Further investigation continues.
I've posted a monolithic 2.6.16 kernel compiled with gcc-3.2.2 at

http://fnarfbargle.dyndns.org:81/qemu/

Someone may get some use out of it.. just use it with the -kernel command line and don't forget to 
-append "root=/blah"

In addition, I grabbed a vnc patch from late last year and bent it a little to get it to fit the 
latest cvs. While I was there I horridly kludged it so that it compiles with --disable-sdl to save 
it linking with the sdl and X libs (which I don't want to install on my servers if I can avoid it).
It's all been lightly tested in various combinations of vnc and sdl and appears to do the job. Usual 
caveats about mouse sync in vnc apply (not that I use it in graphics mode anyway, but I did test it 
with knoppix).
You'll find the patch at the above location also, but be warned.. it works, but it's really ugly.

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

             reply	other threads:[~2006-03-26 11:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 11:17 Brad Campbell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-27  6:47 [Qemu-devel] -kernel-kqemu with linux guest and vnc Brad Campbell

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=44267852.7050000@wasp.net.au \
    --to=brad@wasp.net.au \
    --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).