Hi,
As of last March, the bug was found to be in SeaBIOS:
http://www.seabios.org/pipermail/seabios/2010-March/000419.html
Since Bochs BIOS didn't have the problem in this thread, it is
reasonable to assume that any QEMU issues that existed in 0.9.1 are
fixed by now.
This has also been fixe
Hi,
Sorry, can't follow this ATM. But maybe you mean this: there is indeed a
problem with removing the clearance of event_inj.invalid as it may be
later on transferred into exit_int_info. And if we succeed with
injecting the event, that field must not remaind valid.
Correct.
OK, here is v2:
only clear SVM_EVTINJ_VALID after successful interrupt
delivery. This apparently does not match real hardware which clears the
whole event_inj field on every vmexit, including unsuccessful interrupt
delivery.
Reported-by: Erik van der Kouwe
Signed-off-by: Jan Kiszka
---
(before it gets lost)
Erik, p
Hi,
Would be nice to have nested VMX support though, given that Intel CPUs
are so much more common than AMDs. I've been searching on the Dell
website (in the Netherlands) for a laptop recently and I couldn't find a
single AMD model.
That doesn't mean they are uncommon ;-) There are many vend
Hi,
And the svm-emulation is only available on AMD hardware.
I assume you mean nested SVM emulation in a KVM guest is only
available on real AMD hardware?
Is this due to something inherent, or just a limitation of the KVM
code not handling all the necessary traps in kvm-intel?
I don't think
Hi,
Thankss for your answer.
SVM always clears the vmcb.eventinj on vmrun because every exception is
injected right after vmrun finished and cpu is in guest mode. It can
happen (for example if taking the exception causes a page fault) that
the vmcb.eventinj field is copied to vmcb.exit_int_info
Hi,
Use Linux+KVM as host OS, it can also run VMMs as guests (aka nested
SVM). And you could even debug those guests just like when you would run
QEMU in emulation mode. In contrast to SVM emulation, nesting is fairly
stable AFAIK. And it is faster.
In my experience, if I provide the -enable-k
Hi,
Be warned: Though my experience is already more than a year old, the SVM
emulation in QEMU is most probably not yet rock-stable. Always check
suspicious behavior against real hardware and/or the spec. [ As real
hardware is everywhere, nesting works with KVM+SVM and is much faster,
motivation
ored in EXITINTINFO.
Thanks in advance for any information,
Erik van der Kouwe
translation block i would love to hear it.
With kind regards,
Erik van der Kouwe
swers, suggestions or other advice you may have.
With kind regards,
Erik van der Kouwe
11 matches
Mail list logo