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

[Katrina Austin]

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 <address@hidden> 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 <address@hidden> 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