From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: William barath <w_barath@hotmail.com>
Subject: Re: [Qemu-devel] RE: Qemu-devel Digest, Vol 25, Issue 38
Date: Thu, 21 Apr 2005 13:48:34 +0100 [thread overview]
Message-ID: <200504211348.34717.paul@codesourcery.com> (raw)
In-Reply-To: <BAY103-F5AEA2C4A6CA099EE7FBB7EB2C0@phx.gbl>
On Thursday 21 April 2005 07:20, William barath wrote:
> I've tried recently to build both qvm86 and kqemu kernel modules with
> identical results...
>
> Instead of building the module, it builds ALL other kernel modules.
> Luckily this only takes a few minutes on the second and third attempt!
>
> I'm using SuSE 9.1 FTP edition with the stock kernel "2.6.4-52-default",
> and today's CVS of both qemu and qvm86, as well as the kqemu plugin tarball
> from Fabrice's site.
<snip>
> Do I have to install a new kernel to get around this?
Probably. 2.6.4 is fairly old. I'm not particularly interested in making qvm86
support such old kernels.
Paul
next prev parent reply other threads:[~2005-04-21 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MC8-F38fRVvd5X00lfe000256c0@MC8-F38.hotmail.com>
2005-04-21 6:20 ` [Qemu-devel] RE: Qemu-devel Digest, Vol 25, Issue 38 William barath
2005-04-21 12:48 ` Paul Brook [this message]
2005-04-21 6:48 Ben Taylor
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=200504211348.34717.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=w_barath@hotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.