* [Qemu-devel] Bug report for kvm-kmod-3.3!
@ 2012-03-23 8:19 Katrina Austin
2012-03-23 10:28 ` Jan Kiszka
0 siblings, 1 reply; 8+ messages in thread
From: Katrina Austin @ 2012-03-23 8:19 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
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.
Thanks,
katrina
[-- Attachment #2: Type: text/html, Size: 734 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [Qemu-devel] Bug report for kvm-kmod-3.3! 2012-03-23 8:19 [Qemu-devel] Bug report for kvm-kmod-3.3! Katrina Austin @ 2012-03-23 10:28 ` Jan Kiszka 2012-03-23 11:45 ` Katrina Austin 0 siblings, 1 reply; 8+ messages in thread From: Jan Kiszka @ 2012-03-23 10:28 UTC (permalink / raw) To: Katrina Austin; +Cc: qemu-devel 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] Bug report for kvm-kmod-3.3! 2012-03-23 10:28 ` Jan Kiszka @ 2012-03-23 11:45 ` Katrina Austin 2012-03-23 12:13 ` Jan Kiszka 0 siblings, 1 reply; 8+ messages in thread From: Katrina Austin @ 2012-03-23 11:45 UTC (permalink / raw) To: Jan Kiszka; +Cc: qemu-devel [-- Attachment #1: Type: text/plain, Size: 1853 bytes --] 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 <jan.kiszka@siemens.com> 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 > [-- Attachment #2: Type: text/html, Size: 2457 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] Bug report for kvm-kmod-3.3! 2012-03-23 11:45 ` Katrina Austin @ 2012-03-23 12:13 ` Jan Kiszka 2012-03-23 12:21 ` Katrina Austin 2012-03-28 12:44 ` Katrina Austin 0 siblings, 2 replies; 8+ messages in thread From: Jan Kiszka @ 2012-03-23 12:13 UTC (permalink / raw) To: Katrina Austin; +Cc: qemu-devel@nongnu.org On 2012-03-23 12:45, Katrina Austin wrote: > 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". QEMU uses an AMD-derived CPU type by default. Does the image work when you specify, e.g., -cpu Nehalem? Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] Bug report for kvm-kmod-3.3! 2012-03-23 12:13 ` Jan Kiszka @ 2012-03-23 12:21 ` Katrina Austin 2012-03-24 2:21 ` Katrina Austin 2012-03-28 12:44 ` Katrina Austin 1 sibling, 1 reply; 8+ messages in thread From: Katrina Austin @ 2012-03-23 12:21 UTC (permalink / raw) To: Jan Kiszka; +Cc: qemu-devel@nongnu.org [-- Attachment #1: Type: text/plain, Size: 1079 bytes --] The microa-architecture of Intel Xeon E5620 is westmere-EP. So, how to specify, e.g., -cpu westmere? p.s. I cannot test it until tomorrow as I am out of office now. Thanks, katrina On Fri, Mar 23, 2012 at 8:13 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote: > On 2012-03-23 12:45, Katrina Austin wrote: > > 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". > > QEMU uses an AMD-derived CPU type by default. Does the image work when > you specify, e.g., -cpu Nehalem? > > Jan > > -- > Siemens AG, Corporate Technology, CT T DE IT 1 > Corporate Competence Center Embedded Linux > [-- Attachment #2: Type: text/html, Size: 1570 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] Bug report for kvm-kmod-3.3! 2012-03-23 12:21 ` Katrina Austin @ 2012-03-24 2:21 ` Katrina Austin 0 siblings, 0 replies; 8+ messages in thread From: Katrina Austin @ 2012-03-24 2:21 UTC (permalink / raw) To: Jan Kiszka; +Cc: qemu-devel@nongnu.org [-- Attachment #1: Type: text/plain, Size: 1491 bytes --] Hi Jan, I have tried to specify the CPU type but got no luck. More specifically, the bootrom of vxworks failed. I think the problem lies in the Intel VMX. However, I don't know how to make further debugging. Hope you can provide more suggestions from the bug report. Best, Katrina On Fri, Mar 23, 2012 at 8:21 PM, Katrina Austin <kaustin272@gmail.com>wrote: > The microa-architecture of Intel Xeon E5620 is westmere-EP. So, how to > specify, e.g., -cpu westmere? > p.s. I cannot test it until tomorrow as I am out of office now. > > Thanks, > > katrina > > On Fri, Mar 23, 2012 at 8:13 PM, Jan Kiszka <jan.kiszka@siemens.com>wrote: > >> On 2012-03-23 12:45, Katrina Austin wrote: >> > 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". >> >> QEMU uses an AMD-derived CPU type by default. Does the image work when >> you specify, e.g., -cpu Nehalem? >> >> Jan >> >> -- >> Siemens AG, Corporate Technology, CT T DE IT 1 >> Corporate Competence Center Embedded Linux >> > > [-- Attachment #2: Type: text/html, Size: 2352 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] Bug report for kvm-kmod-3.3! 2012-03-23 12:13 ` Jan Kiszka 2012-03-23 12:21 ` Katrina Austin @ 2012-03-28 12:44 ` Katrina Austin 2012-03-28 12:52 ` Jan Kiszka 1 sibling, 1 reply; 8+ messages in thread From: Katrina Austin @ 2012-03-28 12:44 UTC (permalink / raw) To: Jan Kiszka; +Cc: qemu-devel@nongnu.org [-- Attachment #1: Type: text/plain, Size: 1136 bytes --] Hi Jan, Now I wanna to locate the instruction in the guest OS that causes this problem. However, I dont know how to make it as the guest OS has not yet started up. I would be much appreicated if you can provide some suggestions. Katrina On Fri, Mar 23, 2012 at 8:13 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote: > On 2012-03-23 12:45, Katrina Austin wrote: > > 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". > > QEMU uses an AMD-derived CPU type by default. Does the image work when > you specify, e.g., -cpu Nehalem? > > Jan > > -- > Siemens AG, Corporate Technology, CT T DE IT 1 > Corporate Competence Center Embedded Linux > [-- Attachment #2: Type: text/html, Size: 1579 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] Bug report for kvm-kmod-3.3! 2012-03-28 12:44 ` Katrina Austin @ 2012-03-28 12:52 ` Jan Kiszka 0 siblings, 0 replies; 8+ messages in thread From: Jan Kiszka @ 2012-03-28 12:52 UTC (permalink / raw) To: Katrina Austin; +Cc: qemu-devel@nongnu.org On 2012-03-28 14:44, Katrina Austin wrote: > Hi Jan, > Now I wanna to locate the instruction in the guest OS that causes this problem. However, I dont know how to make it as the guest OS has not yet started up. I would be much appreicated if you can provide some suggestions. Not sure if we discussed this already, but getting kvm-kmod from the list of suspects would be good, ie. testing original kvm over a recent kernel (3.3 or kvm.git). There is always the risk that some wrapping is broken and causes such an error. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-03-28 12:52 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-03-23 8:19 [Qemu-devel] Bug report for kvm-kmod-3.3! Katrina Austin 2012-03-23 10:28 ` Jan Kiszka 2012-03-23 11:45 ` Katrina Austin 2012-03-23 12:13 ` Jan Kiszka 2012-03-23 12:21 ` Katrina Austin 2012-03-24 2:21 ` Katrina Austin 2012-03-28 12:44 ` Katrina Austin 2012-03-28 12:52 ` Jan Kiszka
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).