From: Jung-uk Kim <jkim@FreeBSD.org>
To: freebsd-amd64@FreeBSD.org
Cc: freebsd-emulation@FreeBSD.org,
Juergen Lock <nox@jelal.kn-bremen.de>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: oops! (was: FreeBSD qemu port update - some success with kqemu/amd64 :)
Date: Tue, 6 Sep 2005 16:10:22 -0400 [thread overview]
Message-ID: <200509061610.24704.jkim@FreeBSD.org> (raw)
In-Reply-To: <20050906195449.GA10388@saturn.kn-bremen.de>
On Tuesday 06 September 2005 03:54 pm, Juergen Lock wrote:
> Jung-uk Kim just made me aware of a device cloning change which
> requires a patch to the kqemu wrapper for __FreeBSD_version >=
> 600034. So here is a new port update:
--- >8 --- SNIP!!! --- >8 ---
It is working as advertised on FreeBSD/amd64 -CURRENT host now. :-)
BTW, I just confirmed FreeBSD 6.0-BETA4 guest works when PREEMPTION
option is removed from kernel configuration.
Thanks for the update,
Jung-uk Kim
next prev parent reply other threads:[~2005-09-06 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 19:07 [Qemu-devel] FreeBSD qemu port update - some success with kqemu/amd64 :) Juergen Lock
2005-09-06 19:54 ` [Qemu-devel] oops! (was: " Juergen Lock
2005-09-06 20:10 ` Jung-uk Kim [this message]
2005-09-10 17:06 ` [Qemu-devel] " Juergen Lock
2005-09-10 17:19 ` Juergen Lock
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=200509061610.24704.jkim@FreeBSD.org \
--to=jkim@freebsd.org \
--cc=freebsd-amd64@FreeBSD.org \
--cc=freebsd-emulation@FreeBSD.org \
--cc=nox@jelal.kn-bremen.de \
--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).