runqemu qemux86-64 image kvm cpuid error

Arjun Padmanabhan arjun.padmanabhan at microsemi.com
Mon Sep 26 19:51:32 AEST 2016


Hi,

While executing runqemu on qemux86-64 image with kvm option, I am getting CPUID kvm_asyncpf error.  Have anyone faced this issue? Is there any fix for this issue?

I am attaching my cpuinfo along with this mail.

Following is the console output.
[root at openbmc qemux86-64]# runqemu qemux86-64 kvm

Continuing with the following parameters:
KERNEL:
[/root/Desktop/openbmc/openbmc/qemu_build/tmp/deploy/images/qemux86-64/bzImage-qemux86-64.bin]
ROOTFS:
[/root/Desktop/openbmc/openbmc/qemu_build/tmp/deploy/images/qemux86-64/obmc-phosphor-image-qemux86-64-20160923061208.rootfs.ext4]
FSTYPE: [ext4]
Setting up tap interface under sudo
Acquiring lockfile for tap0...
Running qemu-system-x86_64...
/root/Desktop/openbmc/openbmc/qemu_build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-x86_64
-kernel
/root/Desktop/openbmc/openbmc/qemu_build/tmp/deploy/images/qemux86-64/bzImage-qemux86-64.bin
-net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no -cpu
kvm64 -drive
file=/root/Desktop/openbmc/openbmc/qemu_build/tmp/deploy/images/qemux86-64/obmc-phosphor-image-qemux86-64-20160923061208.rootfs.ext4,if=virtio,format=raw
-show-cursor -usb -usbdevice tablet -vga vmware -no-reboot -enable-kvm -m 256
-serial mon:vc -serial null -append "vga=0 uvesafb.mode_option=640x480-32
root=/dev/vda rw mem=256M ip=192.168.7.2::192.168.7.1:255.255.255.0
oprofile.timer=1 rootfstype=ext4 "
warning: host doesn't support requested feature:
CPUID.40000001H:EAX.kvm_asyncpf [bit 4]
VNC server running on '::1:5901'

Regards
Arjun Padmanabhan
Microsemi Storage Solutions India Pvt. Ltd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160926/c95201fe/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cpu_info.txt
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160926/c95201fe/attachment.txt>


More information about the openbmc mailing list