From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH] [RFC] Solaris user emulation
Date: Tue, 14 Apr 2009 19:25:55 +0300 [thread overview]
Message-ID: <f43fc5580904140925m1aa496f1i38f1575c3fa1933e@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
Hi,
I started to add support for (Open)Solaris user emulation. It compiles
but doesn't work yet, this is just a preview. The patch is largely
copy & paste from BSD user and there are no docs yet.
The current blocking problem is that I don't know how to make the
qemu-i386 executable a shared ELF object which Solaris wouldn't refuse
to execute (with native ld). Without that, qemu-i386 and the target
executable occupy same memory region, leading to a crash. Any hints
are welcome.
One problem is that Solaris headers are CDDL licensed and IIRC that
was not compatible with GPL.
[-- Attachment #2: solaris_user.diff.bz2 --]
[-- Type: application/x-bzip2, Size: 30011 bytes --]
next reply other threads:[~2009-04-14 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 16:25 Blue Swirl [this message]
2009-04-14 16:45 ` [Qemu-devel] [PATCH] [RFC] Solaris user emulation M. Warner Losh
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=f43fc5580904140925m1aa496f1i38f1575c3fa1933e@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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).