Bug 1657738 - qemu core dump when start guest: qemu-kvm: error: failed to set MSR 0x10a to 0x0
Summary: qemu core dump when start guest: qemu-kvm: error: failed to set MSR 0x10a to 0x0
Keywords:
Status: CLOSED DUPLICATE of bug 1655826
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Amnon Ilan
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-10 10:59 UTC by Xueqiang Wei
Modified: 2019-02-22 22:10 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-12 05:35:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
core dump log (21.53 KB, text/plain)
2018-12-10 10:59 UTC, Xueqiang Wei
no flags Details

Description Xueqiang Wei 2018-12-10 10:59:14 UTC
Created attachment 1513022 [details]
core dump log

Description of problem:

# sh test.sh 
QEMU 3.0.92 monitor - type 'help' for more information
(qemu) qemu-kvm: error: failed to set MSR 0x10a to 0x0
qemu-kvm: /builddir/build/BUILD/qemu-3.1.0/target/i386/kvm.c:2211: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
src.sh: line 51: 14964 Aborted                 (core dumped)




Version-Release number of selected component (if applicable):

Kernel-4.18.0-37.el8.x86_64
qemu-kvm-3.1.0-0.module+el8+2266+616cf026.next.candidate




How reproducible:
5/5


Steps to Reproduce:

1. start guest with below cmd lines.

/usr/libexec/qemu-kvm \
    -S  \
    -name 'avocado-vt-vm1'  \
    -sandbox off  \
    -machine q35  \
    -nodefaults \
    -device VGA,bus=pcie.0,addr=0x1 \
    -device pcie-root-port,id=pcie_root_port_0,slot=2,chassis=2,addr=0x2,bus=pcie.0 \
    -device pcie-root-port,id=pcie_root_port_1,slot=3,chassis=3,addr=0x3,bus=pcie.0 \
    -device pcie-root-port,id=pcie_root_port_2,slot=4,chassis=4,addr=0x4,bus=pcie.0  \
    -chardev socket,id=qmp_id_qmpmonitor1,path=/var/tmp/avocado_w2u90exl/monitor-qmpmonitor1-20181127-024837-wdAVx2FL,server,nowait \
    -mon chardev=qmp_id_qmpmonitor1,mode=control  \
    -chardev socket,id=qmp_id_catch_monitor,path=/var/tmp/avocado_w2u90exl/monitor-catch_monitor-20181127-024837-wdAVx2FL,server,nowait \
    -mon chardev=qmp_id_catch_monitor,mode=control \
    -device pvpanic,ioport=0x505,id=idulvcka  \
    -chardev socket,id=serial_id_serial0,path=/var/tmp/avocado_w2u90exl/serial-serial0-20181127-024837-wdAVx2FL,server,nowait \
    -device isa-serial,chardev=serial_id_serial0  \
    -chardev socket,id=seabioslog_id_20181127-024837-wdAVx2FL,path=/var/tmp/avocado_w2u90exl/seabios-20181127-024837-wdAVx2FL,server,nowait \
    -device isa-debugcon,chardev=seabioslog_id_20181127-024837-wdAVx2FL,iobase=0x402 \
    -device pcie-root-port,id=pcie.0-root-port-5,slot=5,chassis=5,addr=0x5,bus=pcie.0 \
    -device qemu-xhci,id=usb1,bus=pcie.0-root-port-5,addr=0x0 \
    -device pcie-root-port,id=pcie.0-root-port-6,slot=6,chassis=6,addr=0x6,bus=pcie.0 \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie.0-root-port-6,addr=0x0 \
    -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/images/win2019-64-virtio-scsi.qcow2,node-name=my_file \
    -blockdev driver=qcow2,node-name=my,file=my_file \
    -device scsi-hd,drive=my,bus=virtio_scsi_pci0.0 \
    -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/images/data.qcow2,node-name=data_disk \
    -blockdev driver=qcow2,node-name=disk1,file=data_disk \
    -device scsi-hd,drive=disk1,bus=virtio_scsi_pci0.0 \
    -device pcie-root-port,id=pcie.0-root-port-7,slot=7,chassis=7,addr=0x7,bus=pcie.0 \
    -device virtio-net-pci,mac=9a:34:35:36:37:38,id=idyb3F88,vectors=4,netdev=idTAFS0s,bus=pcie.0-root-port-7,addr=0x0  \
    -netdev tap,id=idTAFS0s,vhost=on \
    -m 8G  \
    -smp 12,maxcpus=12,cores=6,threads=1,sockets=2  \
    -cpu 'Opteron_G5',+kvm_pv_unhalt \
    -device pcie-root-port,id=pcie.0-root-port-9,slot=9,chassis=9,addr=0x9,bus=pcie.0 \
    -device virtio-scsi-pci,id=virtio_scsi_pci1,bus=pcie.0-root-port-9,addr=0x0 \
    -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/windows/winutils.iso,node-name=cd_disk1,read-only=on \
    -blockdev driver=raw,node-name=cd1,file=cd_disk1,read-only=on \
    -device scsi-cd,drive=cd1,bus=virtio_scsi_pci1.0,id=cd_disk1 \
    -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-162.iso,node-name=cd_disk2,read-only=on \
    -blockdev driver=raw,node-name=cd2,file=cd_disk2,read-only=on \
    -device scsi-cd,drive=cd2,bus=virtio_scsi_pci1.0,id=cd_disk2 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -vnc :0  \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot order=cdn,once=c,menu=off,strict=off \
    -enable-kvm \
    -monitor stdio \
    -qmp tcp:0:4444,server,nowait \



Actual results:

after step 1: 
(qemu) qemu-kvm: error: failed to set MSR 0x10a to 0x0
qemu-kvm: /builddir/build/BUILD/qemu-3.1.0/target/i386/kvm.c:2211: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
src.sh: line 51: 14964 Aborted                 (core dumped)


Expected results:
boot up normally.


Additional info:

Tested on qemu-kvm-3.0.0-2.module+el8+2246+78080371, not hit this issue.

Comment 1 Pei Zhang 2018-12-10 11:31:51 UTC
Hit same issue too.

# /usr/libexec/qemu-kvm -cpu 'EPYC'
qemu-kvm: error: failed to set MSR 0x10a to 0x0
qemu-kvm: /builddir/build/BUILD/qemu-3.1.0/target/i386/kvm.c:2211: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
Aborted (core dumped)

Comment 2 Pei Zhang 2018-12-10 11:35:41 UTC
Additional info: 

When testing With "-cpu Haswell-noTSX", qemu works well.

My setup versions:
4.18.0-49.el8.x86_64
qemu-kvm-3.1.0-0.module+el8+2266+616cf026.next.candidate.x86_64

Comment 4 Xueqiang Wei 2018-12-11 10:25:33 UTC
Tested with the same environment(same cmd lines and same host) on QEMU 3.1.0 rc5, not hit this issue.

Comment 5 Xueqiang Wei 2018-12-11 10:27:22 UTC
Versions:
kernel-4.18.0-50.el8.x86_64
QEMU 3.1.0 rc5

Comment 6 Bandan Das 2018-12-11 18:40:58 UTC
On an AMD host ? Most likely a duplicate of bug 1655826.

Comment 7 Xueqiang Wei 2018-12-12 05:35:20 UTC
(In reply to Bandan Das from comment #6)
> On an AMD host ? Most likely a duplicate of bug 1655826.

Yes, I tested on Opteron_G5. It's a duplicate of bug 1655826. So close it.

*** This bug has been marked as a duplicate of bug 1655826 ***


Note You need to log in before you can comment on or make changes to this bug.