Andreas Tanz wrote:
Craig Metz wrote:
In message 49d396ab.6090...@redhat.com, you write:
Via engineers have contacted me and confirmed that this is a problem in
the processor.
Is there a known-fixed CPU revision?
Is there a way to identify working vs.
Craig Metz wrote:
In message 49d396ab.6090...@redhat.com, you write:
Via engineers have contacted me and confirmed that this is a problem in
the processor.
Is there a known-fixed CPU revision?
Is there a way to identify working vs. non-working chips, either from IC
Avi Kivity wrote:
Will talk to the specification and come up with further tests.
Please printk() vmcs_readl(GUEST_RFLAGS) (where you printk kvm_rip_read()).
vmx.c:
2637 static int handle_exception(struct kvm_vcpu *vcpu, struct kvm_run *kvm_run)
2638 {
...
2687 error_code = 0;
Andreas Tanz wrote:
[ 3732.020033] returning from kvm_handle_exit, cause 3, retval = 1, exit_reason
= 7
Here, vmx tells us that the guest is ready to accept interrupts (having
executed the sti instruction)
[ 3732.020044] vmx-vmx_vcpu_run() 00 : vmcs_read32(VM_ENTRY_INTR_INFO_FIELD)
Avi Kivity wrote:
Will talk to the specification and come up with further tests.
Please printk() vmcs_readl(GUEST_RFLAGS) (where you printk kvm_rip_read()).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this
Andreas Tanz wrote:
Hi!
The guest starts up showing the Bochs BIOS POST and stucks giving thousands of lines :
[15013.656923] returning from kvm_handle_exit, cause 3, retval = 1
What was the value of exit_reason?
kernel/x86/vmx.c:
3211 static int kvm_handle_exit(struct
-- dmesg :
[79116.175571] returning from kvm_handle_exit, cause 3, retval = 1,
exit_reason = 0
That's an exception or nmi. Next step is to instrument
handle_exception() and see what happens there. Please print out
vect_info, intr_info, and kvm_rip_read(vcpu) (all as hex).
The
Andreas Tanz wrote:
-- dmesg :
[79116.175571] returning from kvm_handle_exit, cause 3, retval = 1, exit_reason = 0
That's an exception or nmi. Next step is to instrument
handle_exception() and see what happens there. Please print out
vect_info, intr_info, and kvm_rip_read(vcpu) (all
i modded handle_exception as you said :
vmx.c:
...
2637 static int handle_exception(struct kvm_vcpu *vcpu, struct kvm_run *kvm_run)
2638 {
2639 struct vcpu_vmx *vmx = to_vmx(vcpu);
2640 u32 intr_info, ex_no, error_code;
2641 unsigned long cr2, rip, dr6;
2642 u32
Andreas Tanz wrote:
i modded handle_exception as you said :
2711 printk(KERN_ERR vmx-handle_exception 0f : vcpu-arch.rmode.active:
0x%x\n,vcpu-arch.rmode.active);
2712 int debug_handle_rmode_exception = handle_rmode_exception(vcpu,
intr_info INTR_INFO_VECTOR_MASK,
Am 19.03.2009 schrieb Avi Kivity:
This bit is broken. The original code:
if (vcpu-arch.rmode.active
handle_rmode_exception(vcpu, intr_info INTR_INFO_VECTOR_MASK,
error_code)) {
Only executes handle_rmode_exception() if rmode.active is true.
Andreas Tanz wrote:
Am 19.03.2009 schrieb Avi Kivity:
This bit is broken. The original code:
if (vcpu-arch.rmode.active
handle_rmode_exception(vcpu, intr_info INTR_INFO_VECTOR_MASK,
error_code)) {
Only executes handle_rmode_exception() if
12 matches
Mail list logo
