All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Laszlo Ersek \(Red Hat\)" <1813165@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1813165] Re: KVM internal error. Suberror: 1 emulation failure
Date: Wed, 12 Aug 2020 12:51:43 -0000	[thread overview]
Message-ID: <159723670394.9711.18197255346528020388.malone@wampee.canonical.com> (raw)
In-Reply-To: 154833838504.19548.14915901097039330455.malonedeb@gac.canonical.com

According to comment #12, the bug underlying this LP ticket was fixed in
Linux kernel commit ad7dc69aeb23 ("x86/kvm/mmu: fix switch between root
and guest MMUs", 2019-02-22), released in v5.0.

** Project changed: qemu => linux

** Changed in: linux
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813165

Title:
  KVM internal error. Suberror: 1 emulation failure

Status in Linux:
  Fix Released

Bug description:
  Hello Devs.

  Having problems getting VM to run with qemu 3.1.0. I should mention
  it's a nested configuration.

  2019-01-24 13:46:08.648+0000: starting up libvirt version: 4.10.0, qemu version: 3.1.0, kernel: 4.14.94, hostname: one....
  LC_ALL=C PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin HOME=/root USER=root QEMU_AUDIO_DRV=none /usr/bin/kvm -name guest=one-266,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-one-266/master-key.aes -machine pc-i440fx-2.9,accel=kvm,usb=off,dump-guest-core=off -cpu Skylake-Client-IBRS,ss=on,hypervisor=on,tsc_adjust=on,clflushopt=on,ssbd=on,xsaves=on,pdpe1gb=on -m 1024 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid b219b45d-a2f0-4128-a948-8673a7abf968 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=21,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/0/266/disk.0,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,write-cache=on -drive file=/var/lib/one//datastores/0/266/disk.1,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=23,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=02:00:00:76:69:85,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:266 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
  char device redirected to /dev/pts/1 (label charserial0)
  KVM internal error. Suberror: 1
  emulation failure
  EAX=00000001 EBX=000f7c2c ECX=00000001 EDX=00000001
  ESI=00006a26 EDI=3ffbdc48 EBP=000069e6 ESP=000a8000
  EIP=000fd057 EFL=00010016 [----AP-] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =0010 00000000 ffffffff 00c09300
  CS =0000 00000000 00000fff 00809b00
  SS =0010 00000000 ffffffff 00c09300
  DS =0010 00000000 ffffffff 00c09300
  FS =0010 00000000 ffffffff 00c09300
  GS =0010 00000000 ffffffff 00c09300
  LDT=0000 00000000 0000ffff 00008200
  TR =0000 00000000 0000ffff 00008b00
  GDT=     10387cfe 0000fe6c
  IDT=     0010387c 00003810
  CR0=00000010 CR2=00000000 CR3=00000000 CR4=00000000
  DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
  DR6=00000000fffecffc DR7=000000000e1e0400
  EFER=0000000000000000
  Code=cb 66 ba 4d d0 0f 00 e9 c8 fe bc 00 80 0a 00 e8 31 3a ff ff <0f> aa fa fc 66 ba 66 d0 0f 00 e9 b1 fe f3 90 f0 0f ba 2d ac 3b 0f 00 00 72 f3 8b 25 a8 3b
  2019-01-24T13:47:39.383366Z kvm: terminating on signal 15 from pid 2708 (/usr/sbin/libvirtd)

  Someone has an idea whats going wrong here?

  thanks and cheers
  t.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1813165/+subscriptions


      parent reply	other threads:[~2020-08-12 13:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 13:59 [Qemu-devel] [Bug 1813165] [NEW] KVM internal error. Suberror: 1 emulation failure Thomas
2019-01-24 14:09 ` [Qemu-devel] [Bug 1813165] " Thomas
2019-02-05 14:32 ` Albert Damen
2019-02-06 14:28 ` Thomas
2019-02-11 17:38 ` Dr. David Alan Gilbert
2019-02-11 17:41 ` Dr. David Alan Gilbert
2019-02-11 18:50 ` Laszlo Ersek (Red Hat)
2019-02-11 19:37 ` Albert Damen
2019-02-11 20:08 ` Dr. David Alan Gilbert
2019-02-18  9:57 ` Vitaly Kuznetsov
2019-02-20 18:31 ` Vitaly Kuznetsov
2019-02-20 18:47 ` Dr. David Alan Gilbert
2019-02-20 19:18 ` Vitaly Kuznetsov
2019-02-22 16:50 ` Vitaly Kuznetsov
2019-02-22 19:35   ` Bruce Rogers
2019-02-22 20:10 ` Albert Damen
2020-03-05 17:17 ` tstrike
2020-03-05 17:21 ` tstrike
2020-03-05 17:22 ` tstrike
2020-03-06  8:33 ` Vitaly Kuznetsov
2020-03-06 13:17 ` tstrike
2020-03-06 16:36 ` tstrike
2020-03-09 11:25 ` Vitaly Kuznetsov
2020-03-10  0:18 ` tstrike
2020-03-10  8:44 ` Vitaly Kuznetsov
2020-03-10 11:10 ` tstrike
2020-03-10 11:51 ` Vitaly Kuznetsov
2020-03-10 12:21 ` tstrike
2020-03-10 12:38 ` Vitaly Kuznetsov
2020-03-15 21:02 ` Jon Hood
2020-08-12 12:51 ` Laszlo Ersek (Red Hat) [this message]

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=159723670394.9711.18197255346528020388.malone@wampee.canonical.com \
    --to=1813165@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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.