From: Felix Oxley <felix@oxley.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU suitable for mission critical applications?
Date: Wed, 8 Jun 2011 11:08:05 +0100 [thread overview]
Message-ID: <BANLkTim1Kxu1ZeHy+GKJXo_yUkuQE-8a_Q@mail.gmail.com> (raw)
Hello,
I have a an (almost) EOL factory planning system running on Solaris
Sparc which I would like to move to intel (and preferably virtualise)
in order to avoid having to maintain the Sun system and backup system.
The text based cobol application runs on this system: SunOS gplan 5.9
Generic_118558-35 sun4u sparc SUNW,Sun-Blade-1500. It is not feasible
to recompile the application to x86.
Therefore I am looking for alternative solutions. I heard of
Transitive QuickTransit, however since being purchased by IBM I do not
believe this is being marketed.
Would QEMU be suitable for this task? Would I be able to get commercial support?
Thanks for your advice.
next reply other threads:[~2011-06-08 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 10:08 Felix Oxley [this message]
2011-06-08 11:19 ` [Qemu-devel] QEMU suitable for mission critical applications? Stefan Hajnoczi
2011-06-12 21:51 ` Blue Swirl
2011-06-13 9:00 ` Felix Oxley
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=BANLkTim1Kxu1ZeHy+GKJXo_yUkuQE-8a_Q@mail.gmail.com \
--to=felix@oxley.org \
--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).