From: "poletaev" <Dmitry.Poletaev@ispras.ru>
To: qemu-devel@nongnu.org
Cc: Pavel.Dovgaluk@ispras.ru
Subject: [Qemu-devel] vmx support for qemu
Date: Wed, 26 Oct 2016 15:16:25 +0300 [thread overview]
Message-ID: <000501d22f82$c57f3d70$507db850$@Poletaev@ispras.ru> (raw)
Hello. I am trying to make realization of vmx for qemu.
For now it can:
- decode vmx instructions, vmx determination and vmx MSRs reading is
supported
- handle interrupts, exceptions, vm exits due to cr 0/4 exits, cr shadowing
is supported
- run bios POST and some amount of guest code in VirtualBox (tested on 5+
version). Current problem here is a strange wish of hypervisor to change
processor mode in vmx non-root to vm86 and find ill_op there. I have no
ideas, why VirtualBox wants it (may be someone knows?).
- configure guest in kvm, but guest can't run due to #PF which kvm can't
handle right on my realization. Details: when kvm configures guest and
enters in it, #PF with 0xfe05b address happens. Kvm goes to handle #PF.
kvm_mmu_page_fault goes to nonpaging_page_fault, which don't find page in
cache and calls nonpaging_map. nonpaging_map exits after critical section
before out_unlock label. For me reaction looks normal, but I didn't dig
deeper. After #PF handling kvm enters to guest again and falls to kvm again
with #PF on 0xfe05b. This situation repeats infinitely.
If somebody have an interest in subject, he can find sources here
https://github.com/ispras/qemu.git , branch vmx.
Best regards,
Dmitry Poletaev.
next reply other threads:[~2016-10-26 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 12:16 poletaev [this message]
[not found] <5810a75b.6c27c80a.a1cb1.f340SMTPIN_ADDED_BROKEN@mx.google.com>
2016-11-04 12:46 ` [Qemu-devel] vmx support for qemu Stefan Hajnoczi
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='000501d22f82$c57f3d70$507db850$@Poletaev@ispras.ru' \
--to=dmitry.poletaev@ispras.ru \
--cc=Pavel.Dovgaluk@ispras.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.