From: "Bochnig, Martin" <mb1x@gmx.com>
To: qemu-devel@nongnu.org
Cc: Sittichai Palanisong <sitchai@Thailand.sun.com>
Subject: Re: [Qemu-devel] 0.60 Solaris 9 problems.
Date: Mon, 13 Sep 2004 14:05:59 +0200 [thread overview]
Message-ID: <41458D27.2040707@gmx.com> (raw)
In-Reply-To: <200409131034.i8DAY4WO018686@tiger2.tools.intra>
Juergen Keil wrote:
>
>
> The java virtual machine included in Solaris x86 does not work
> for me. When I start "java", I get:
>
> % java
> Error occurred during initialization of VM
> java.lang.InternalError
>
> Tracing system calls (actually tracing signals) using "truss -t!all java"
> shows that the JVM gets a SIGSEGV signal when trying to access memory at
> address 0x0000001F, and crashes with the internal error after that. I'm
> not sure if that's a bug in the java VM or a QEMU x86 CPU emulator bug.
>
>
> Sometimes a working java VM is needed at Solaris x86 installation time.
> For example with Solaris 10 x86, when you have a system with lots of memory,
> then a gui installer written in java is used, but it crashes with the above
> "InternalError" message.
>
> The solaris admin console (smc) also needs a working java VM.
Works for me.
Using
http://www.thinksolaris.com/MB1Xqemu0_6_0_slirp_i386_sunos5.9_local.pkg.gz
See
http://www.thinksolaris.com/java_smc_snapshot0.jpeg and
http://www.thinksolaris.com/java_smc_snapshot1.jpeg .
But currently Gnome2 causes QEMU to segfault.
Maybe the guest graphics driver or so. Using my old pkg and some other
guest config it worked, too. That's why I started the guest into
failsafe mode for the java / smc demo.
next prev parent reply other threads:[~2004-09-13 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 10:34 [Qemu-devel] 0.60 Solaris 9 problems Juergen Keil
2004-09-13 11:01 ` Karel Gardas
2004-09-13 12:05 ` Bochnig, Martin [this message]
2004-09-13 21:04 ` Simon H
-- strict thread matches above, loose matches on Subject: below --
2004-09-14 10:42 Juergen Keil
2004-09-14 11:59 ` Bochnig, Martin
2004-11-09 7:33 ` Paul Jakma
2004-09-12 12:29 Simon H
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=41458D27.2040707@gmx.com \
--to=mb1x@gmx.com \
--cc=bochnig@pool.math.tu-berlin.de \
--cc=qemu-devel@nongnu.org \
--cc=sitchai@Thailand.sun.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 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).