From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 197813] New: KVM: entry failed, hardware error 0x5
Date: Wed, 08 Nov 2017 09:28:32 +0000 [thread overview]
Message-ID: <bug-197813-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=197813
Bug ID: 197813
Summary: KVM: entry failed, hardware error 0x5
Product: Virtualization
Version: unspecified
Kernel Version: 3.13.6
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: biaoxiangye@163.com
Regression: No
Created attachment 260561
--> https://bugzilla.kernel.org/attachment.cgi?id=260561&action=edit
qemu log info
[host CPU]:
Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
[qemu cmdline]:
/usr/bin/qemu-system-x86_64 -name CZJ-TEST_clone2 -S -machine
pc-i440fx-2.1,accel=kvm,usb=off,system=linux -m 4096,slots=10,maxmem=33554432M
-smp 16,maxcpus=160,sockets=10,cores=16,threads=1 -numa
node,nodeid=0,cpus=0-15,mem=4096 -uuid 8ef69d74-8e6a-4c5a-9570-a2d7f6f8bf66
-no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/run/lib/libvirt/qemu/CZJ-TEST_clone2.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
usb-ehci,id=ehci,bus=pci.0,addr=0x4 -device
nec-usb-xhci,id=xhci,bus=pci.0,addr=0x5 -device
virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x6 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive
file=/vms/images/CZJ-TEST_clone2,if=none,id=drive-virtio-disk0,format=qcow2,cache=directsync,aio=native
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive
file=/vms/isos/iso9600-a11e6280-96ca-4725-ac07-23597e2083e8.iso,if=none,id=drive-ide0-0-0,readonly=on,format=raw,cache=directsync,aio=native
-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2
-netdev tap,fd=49,id=hostnet0,vhost=on,vhostfd=50 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=0c:da:41:1d:b9:10,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/CZJ-TEST_clone2.agent,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0
-device usb-tablet,id=input0,bus=usb.0 -vnc 0.0.0.0:4 -device
cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9
[qemu version]
qemu 2.1.2
[qemu error log]
KVM: entry failed, hardware error 0x5
EAX=ffffffed EBX=37fe0000 ECX=00000000 EDX=00000000
ESI=00000000 EDI=00000046 EBP=37fe3e98 ESP=00000080
EIP=81058e96 EFL=001db68a [D-S----] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0080 003eb338 00000000 00008000 DPL=0 <hiword>
CS =44c1 001de741 00000000 00009e00 DPL=0 CS16 [CR-]
SS =097a 00400000 fffff680 00008000 DPL=0 <hiword>
DS =0080 0020bf62 00000000 00008000 DPL=0 <hiword>
FS =0080 001dc5a4 00000000 00008000 DPL=0 <hiword>
GS =cdc3 001dca83 00000000 00009d00 DPL=0 CS16 [C-A]
LDT=de42 001cedc2 00000000 00009c00 DPL=0 CS16 [C--]
TR =0f42 00400000 fffff680 00008000 DPL=0 <hiword>
GDT= 0000000000400000 0000f680
IDT= 00000000001df68c 00000000
CR0=8005003b CR2=00007f43f702b2c8 CR3=00000000001dd2cb CR4=0000046a
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
DR3=0000000000000000
DR6=00000000fffe0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? <??> ?? ?? ??
?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
It occurs several times and don't know how to reporduced.
I have searched the error number 5 in talbe of VM-Instruction Error Numbers, it
means VMRESUME with non-launched VMCS.
VMRESUME should be used for any subsequent VM entry using a VMCS(until the
next execution of VMCLEAR for the VMCS)
Dos it's a kvm bug or cpu issues?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2017-11-08 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 9:28 bugzilla-daemon [this message]
2018-02-13 17:26 ` [Bug 197813] KVM: entry failed, hardware error 0x5 bugzilla-daemon
2018-02-13 17:32 ` bugzilla-daemon
2018-02-13 18:13 ` bugzilla-daemon
2018-02-14 15:15 ` bugzilla-daemon
2018-02-15 18:12 ` Bandan Das
2018-02-15 18:12 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-197813-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox