From: Lonnie Cumberland <lonnie@outstep.com>
To: Qemu-devel@nongnu.org
Subject: Porting QEMU to new hardware challenge?
Date: Fri, 2 Jul 2021 09:32:12 -0400 [thread overview]
Message-ID: <CAPmsJLCSnfkoB9Hk_gT2qJspeadxN3AM=TDbxZ4vpHL_M9X9Cw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
Hello All,
I hope that everyone is doing well today.
Currently, I am working on a project that needs a good and stable VMM to
run a single VM at a time within a new hypervisor being designed that
will run on x86_64 hardware. (at least initially)
For this effort, I have been looking at various possible VMMs like QEMU,
TinyEMU, Bhyve, and even VirtualBox but think that either QEMU or TinyEMU
might be the best solution and I am wondering how hard it might be to port
QEMU over to the new system?
I would like to get your opinion, and suggestions on the best way to
proceed and also what difficulties you may have had in the past, if you
ported QEMU.
Any help or information would be truly appreciated.
Best Regards and have a great weekend,
Lonnie
[-- Attachment #2: Type: text/html, Size: 965 bytes --]
reply other threads:[~2021-07-02 13:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAPmsJLCSnfkoB9Hk_gT2qJspeadxN3AM=TDbxZ4vpHL_M9X9Cw@mail.gmail.com' \
--to=lonnie@outstep.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).