From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 197813] KVM: entry failed, hardware error 0x5
Date: Tue, 13 Feb 2018 17:26:29 +0000 [thread overview]
Message-ID: <bug-197813-28872-M4C757yURy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197813-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197813
Carlos Lopez (clopezbelenguer@es.amnesty.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clopezbelenguer@es.amnesty.
| |org
--- Comment #1 from Carlos Lopez (clopezbelenguer@es.amnesty.org) ---
We are experiencing the same problem with an equivalent proccessor of the same
generation.
[host CPU]:
Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
[kvmqemulog]
/usr/bin/kvm -id 139 -chardev
socket,id=qmp,path=/var/run/qemu-server/139.qmp,server,nowait -mon
chardev=qmp,mode=control -pidfile /var/run/qemu-server/139.pid -smbios
type=1,uuid=04fc63bd-caef-424d-a047-c99d0ffd5be0 -name
DEVsai-store01.es.amnesty.org -smp 10,sockets=1,cores=10,maxcpus=10 -nodefaults
-boot
menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg
-vga std -vnc unix:/var/run/qemu-server/139.vnc,x509,password -cpu
Broadwell-noTSX,+kvm_pv_unhalt,+kvm_pv_eoi,enforce,vendor=GenuineIntel -m 12288
-k es -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device
pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device
piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device
usb-tablet,id=tablet,bus=uhci.0,port=1 -chardev
socket,id=serial0,path=/var/run/qemu-server/139.serial0,server,nowait -device
isa-serial,chardev=serial0 -iscsi
initiator-name=iqn.1993-08.org.debian:01:481b3cd8ee13 -drive
if=none,id=drive-ide2,media=cdrom,aio=threads -device
ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -device
virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive
file=/dev/zvol/zdata1/vm-139-disk-4,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on
-device
scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0
-drive
file=/dev/zvol/zdata1/vm-139-disk-5,if=none,id=drive-scsi1,format=raw,cache=none,aio=native,detect-zeroes=on
-device
scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1
-drive
file=/dev/zvol/zdata1/vm-139-disk-6,if=none,id=drive-scsi3,format=raw,cache=none,aio=native,detect-zeroes=on
-device
scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=3,drive=drive-scsi3,id=scsi3
-drive
file=/dev/zvol/zdata1/vm-139-disk-7,if=none,id=drive-scsi4,format=raw,cache=none,aio=native,detect-zeroes=on
-device
scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=4,drive=drive-scsi4,id=scsi4
-device ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7 -drive
file=/dev/zvol/zdata1/vm-139-disk-1,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on
-device ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=104 -drive
file=/dev/zvol/zdata1/vm-139-disk-2,if=none,id=drive-sata3,format=raw,cache=none,aio=native,detect-zeroes=on
-device ide-drive,bus=ahci0.3,drive=drive-sata3,id=sata3 -drive
file=/dev/zvol/zdata1/vm-139-disk-3,if=none,id=drive-sata5,format=raw,cache=none,aio=native,detect-zeroes=on
-device ide-drive,bus=ahci0.5,drive=drive-sata5,id=sata5 -netdev
type=tap,id=net0,ifname=tap139i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown
-device
e1000,mac=62:20:40:70:2E:55,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
KVM: entry failed, hardware error 0x5
RAX=0000000000000000 RBX=ffffffff81f3c9c0 RCX=0000000000000000
RDX=0000000000000000
RSI=0000000000000000 RDI=0000000000000000 RBP=ffff8803313dbe90
RSP=ffff8803313dbe90
R8 =ffff880333490580 R9 =0000000000000000 R10=00000000ffff5b28
R11=000000000001e400
R12=0000000000000009 R13=0000000000000000 R14=0000000000000000
R15=ffff8803313d8000
RIP=ffffffff81064646 RFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0000 0000000000000000 ffffffff 00000000
CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
DS =0000 0000000000000000 ffffffff 00000000
FS =0000 0000000000000000 ffffffff 00000000
GS =0000 ffff880333480000 ffffffff 00000000
LDT=0000 0000000000000000 ffffffff 00000000
TR =0040 ffff8803334848c0 00002087 00008b00 DPL=0 TSS64-busy
GDT= ffff88033348c000 0000007f
IDT= ffffffffff574000 00000fff
CR0=80050033 CR2=00007f567ecf4700 CR3=000000032ef4e000 CR4=00360670
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
DR3=0000000000000000
DR6=00000000fffe0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=89 e5 fb 5d c3 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 fb f4 <5d> c3 0f 1f
84 00 00 00 00 00 55 48 89 e5 f4 5d c3 66 0f 1f 84 00 00 00 00 00 55 49 89 c9
Since the error and the plaform is almost identical could it be Broadwell/Xeon
related?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-02-13 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 9:28 [Bug 197813] New: KVM: entry failed, hardware error 0x5 bugzilla-daemon
2018-02-13 17:26 ` bugzilla-daemon [this message]
2018-02-13 17:32 ` [Bug 197813] " 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-M4C757yURy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.