From: Gary Jennejohn <gary.jennejohn@freenet.de>
To: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: freebsd-emulation@FreeBSD.org, freebsd-current@FreeBSD.org,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: testing qemu svn r6636 on FreeBSD; future of qemu on FreeBSD...
Date: Wed, 25 Feb 2009 20:15:50 +0100 [thread overview]
Message-ID: <20090225201550.3d3032b5@ernst.jennejohn.org> (raw)
On Mon, 23 Feb 2009 22:19:33 +0100
Juergen Lock <nox@jelal.kn-bremen.de> wrote:
> You could try a few things:
> a) the same with kqemu (userland), in case its a tcg bug (or indeed a
> timeout; remember to rebuild qemu in case you built it without the
> kqemu knob enabled or otherwise kqemu won't get used), and also
> b) another time with -kernel-kqemu in case its a tcg bug affecting
> guest kernel code (altho of course in both cases kqemu can cause its
> own kind of failures, even more so with amd64 guests...)
>
Neither of these work. The only way I can get past loading the kernel
is with -no-kqemu.
I still see the segmentation fault in Yast.call. Now I know that it's
in line 486, if that's of any interest.
Sorry, I'm not going to invest any more time in this.
---
Gary Jennejohn
next reply other threads:[~2009-02-25 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 19:15 Gary Jennejohn [this message]
2009-02-28 17:15 ` [Qemu-devel] Re: testing qemu svn r6636 on FreeBSD; future of qemu on FreeBSD Juergen Lock
2009-02-28 19:16 ` Gary Jennejohn
2009-02-28 21:36 ` Juergen Lock
2009-03-01 17:57 ` Gary Jennejohn
2009-03-01 23:13 ` Juergen Lock
2009-03-02 0:32 ` Gary Jennejohn
-- strict thread matches above, loose matches on Subject: below --
2009-02-22 1:37 [Qemu-devel] " Juergen Lock
[not found] ` <20090223154724.7d687b13@ernst.jennejohn.org>
[not found] ` <20090223211933.GA79361@saturn.kn-bremen.de>
2009-02-25 15:24 ` [Qemu-devel] " Gary Jennejohn
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=20090225201550.3d3032b5@ernst.jennejohn.org \
--to=gary.jennejohn@freenet.de \
--cc=freebsd-current@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).