[Bug 192521] New: KVM: entry failed, hardware error 0x0

[Bug 192521] New: KVM: entry failed, hardware error 0x0

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=192521

            Bug ID: 192521
           Summary: KVM: entry failed, hardware error 0x0
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.4.0-59-generic #80-Ubuntu
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: johnsomor@gmail.com
        Regression: No

libvirt is unable to start a VM with the following error:

2017-01-13 22:31:11.093+0000: starting up libvirt version: 1.3.1, package:
1ubuntu10.6 (Christian Ehrhardt <christian.ehrhardt@canonical.com> Tue, 22 Nov
2016 09:39:18 +0100), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.6),
hostname: ubuntu-xenial-ovh-bhs1-6664327
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name instance-00000001 -S
-machine pc-i440fx-xenial,accel=kvm,usb=off -m 64 -realtime mlock=off -smp
1,sockets=1,cores=1,threads=1 -uuid 8f8ef422-67e4-450c-9e1a-b23bda75da68
-smbios 'type=1,manufacturer=OpenStack Foundation,product=OpenStack
Nova,version=15.0.0,serial=55c26d1f-ee06-476e-a087-bc74cd6652c6,uuid=8f8ef422-67e4-450c-9e1a-b23bda75da68,family=Virtual
Machine' -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-instance-00000001/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew
-global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
-kernel
/opt/stack/data/nova/instances/8f8ef422-67e4-450c-9e1a-b23bda75da68/kernel
-initrd
/opt/stack/data/nova/instances/8f8ef422-67e4-450c-9e1a-b23bda75da68/ramdisk
-append 'root=/dev/vda console=tty0 console=ttyS0' -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/opt/stack/data/nova/instances/8f8ef422-67e4-450c-9e1a-b23bda75da68/disk,format=qcow2,if=none,id=drive-virtio-disk0,cache=none
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:17:59:cd,bus=pci.0,addr=0x3
-chardev
file,id=charserial0,path=/opt/stack/data/nova/instances/8f8ef422-67e4-450c-9e1a-b23bda75da68/console.log
-device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1
-device isa-serial,chardev=charserial1,id=serial1 -vnc 127.0.0.1:0 -k en-us
-device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
char device redirected to /dev/pts/0 (label charserial1)

KVM: entry failed, hardware error 0x0
EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000663
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0000 00000000 0000ffff 00009300
CS =f000 ffff0000 0000ffff 00009b00
SS =0000 00000000 0000ffff 00009300
DS =0000 00000000 0000ffff 00009300
FS =0000 00000000 0000ffff 00009300
GS =0000 00000000 0000ffff 00009300
LDT=0000 00000000 0000ffff 00008200
TR =0000 00000000 0000ffff 00008b00
GDT=     00000000 0000ffff
IDT=     00000000 0000ffff
CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 b0 20 e6 20 66 c3 <ea> 5b e0 00
f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 192521] KVM: entry failed, hardware error 0x0

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=192521

--- Comment #1 from Michael Johnson <johnsomor@gmail.com> ---
FYI, the CPU info from libvirtd:
2017-01-13 22:17:08.882+0000: 11494: debug : cpuBaselineXML:422 : ncpus=1,
nmodels=0
2017-01-13 22:17:08.882+0000: 11494: debug : cpuBaselineXML:425 :
xmlCPUs[0]=<cpu>
  <arch>x86_64</arch>
  <model>Haswell-noTSX</model>
  <vendor>Intel</vendor>
  <topology sockets="8" cores="1" threads="1"/>
  <feature name="abm"/>
  <feature name="f16c"/>
  <feature name="hypervisor"/>
  <feature name="osxsave"/>
  <feature name="pdpe1gb"/>
  <feature name="rdrand"/>
  <feature name="ss"/>
  <feature name="vme"/>
  <feature name="vmx"/>
</cpu>

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 192521] KVM: entry failed, hardware error 0x0

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=192521

Huaitong Han <oenhan@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |oenhan@gmail.com

--- Comment #2 from Huaitong Han <oenhan@gmail.com> ---
You should paste your host cpuinfo and host kernel version.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 192521] KVM: entry failed, hardware error 0x0

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=192521

--- Comment #3 from Michael Johnson <johnsomor@gmail.com> ---
Unfortunately this is at a hosting provider, OVH which I don't have access to
the underlying host.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.