qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Bug report for kvm-kmod-3.3!


From: Katrina Austin
Subject: Re: [Qemu-devel] Bug report for kvm-kmod-3.3!
Date: Fri, 23 Mar 2012 19:45:26 +0800

Hi Jan,
 
   The host version is: linux-2.6.33.3. I removed the kvm incorporated in the linux kernel and rebuilt the kvm-kmod-3.3.tar.bz2. I have tried from kvm-kmod-2.6.33.3 to kvm-kmod.3.3. Unfortunately, no one worked. The tested guest image is vxworks downloaded from http://people.freebsd.org/~wpaul/qemu/. You can download the vxworks.img and run the commandline: kvm -fda vxworks.img. The qemu will report: KVM internel error: suberror:1. However, it works well if 'no-kvm' is set, namely "kvm -fda vxworks.img -no-kvm".
   Could you please explain what the error means? It seems to be related with 32-bit protected mode.
   Thanks,
 
katrina
  

On Fri, Mar 23, 2012 at 6:28 PM, Jan Kiszka <address@hidden> wrote:
On 2012-03-23 09:19, Katrina Austin wrote:
> Hi all,
>
>    I've built a guest image. It works well on KVM with a AMD X240 processor
> but failed with a intel E5620 processor. I am using kvm-kmod-3.3 and
> qemu-kvm-0.14.0. Here comes the report:
>                 kvm_emulate_insn: 0: 11a6d0: ff (prot32) failed
>                 kvm_userspace_exit: reason KVM_EXIT_INTERNAL_ERROR (17)
>                 kvm_inj_exception:    #UD(0x0)
>                 kvm_entry: vcpu 0
>                 kvm_exit: reason EPT_MISCONFIG rip 0x11a6d0 info 0 0
>   It bothers me so much and I would be much appreciated if someone can
> provide help.

Could it be that your guest image uses instructions that are only
available on AMD processors? Or is this a regression from previous KVM
versions. If yes, which one worked?

Further questions in that case:
 - Could you retest with KVM over a 3.3 kernel, i.e. without kvm-kmod?
  Does that also faile?
 - What is your host kernel version?

Jan

--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


reply via email to

[Prev in Thread] Current Thread [Next in Thread]