From: Serge Hallyn <1387881@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1387881] Re: qemu fails to recognize full virtualization
Date: Mon, 03 Nov 2014 16:12:10 -0000 [thread overview]
Message-ID: <20141103161210.GL10873@ubuntumail> (raw)
In-Reply-To: 20141031174359.6330.97979.malone@soybean.canonical.com
I don't think however that we can claim this is notabug. Based on the
Description, the kvm modules appears to be loaded and enabled, per kvm-ok
output. You shouldn't be getting the
KVM internal error. Suberror: 1
emulation failure
that you're getting, and it's not clear to me what part of installing
qemu-kvm is fixing it.
Can you only get this on one particular host (i.e. hardware type)? Is
there anything in syslog? Which packages (dpkg -l | grep qemu) are
actually installed? Does a reboot (without installing new packages)
fix the problem?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1387881
Title:
qemu fails to recognize full virtualization
Status in QEMU:
New
Status in “linux” package in Ubuntu:
Invalid
Status in “qemu” package in Ubuntu:
New
Bug description:
System:
14.04
qemu - 2.0.0+dfsg-2ubuntu1.6
virtinst 0.600.4-3ubuntu2
Command:
virt-install --name juju-bootstrap --ram=2048 --vcpus=1 --hvm \
--virt-type=kvm --pxe --boot network,hd --os-variant=ubuntutrusty \
--graphics vnc --noautoconsole --os-type=linux --accelerate \
--disk=/var/lib/libvirt/images/juju-bootstrap.qcow2,bus=virtio,format=qcow2,cache=none,sparse=true,size=20 \
--network=bridge=br0,model=virtio
Error:
ERROR Host does not support virtualization type 'hvm'
Diagnostics:
$ sudo kvm -vnc :1 -monitor stdio
[sudo] password for cscloud:
QEMU 2.0.0 monitor - type 'help' for more information
(qemu) KVM internal error. Suberror: 1
emulation failure
EAX=00000000 EBX=40010000 ECX=00000030 EDX=00000cfd
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00006fcc
EIP=0fedb30c EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00409300 DPL=0 DS [-WA]
CS =0008 00000000 ffffffff 00c09a00 DPL=0 CS32 [-R-]
SS =0010 00000000 ffffffff 00409200 DPL=0 DS [-W-]
DS =0010 00000000 ffffffff 00409300 DPL=0 DS [-WA]
FS =0010 00000000 ffffffff 00c09300 DPL=0 DS [-WA]
GS =0010 00000000 ffffffff 00c09300 DPL=0 DS [-WA]
LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
GDT= 000f6688 00000037
IDT= 000f66c6 00000000
CR0=60000011 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
info kvm
kvm support: enabled
(qemu)
> lsmod|grep kvm
kvm_intel 143109 0
kvm 451552 1 kvm_intel
$ dmesg|grep -i kvm
[ 5.722167] kvm: Nested Virtualization enabled
[ 5.722190] kvm: Nested Paging enabled
---
I haven't been able to get much out of libvirt as the kvm instance
never starts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1387881/+subscriptions
next prev parent reply other threads:[~2014-11-03 16:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 21:34 [Qemu-devel] [Bug 1387881] [NEW] qemu fails to recognize full virtualization Adam Stokes
2014-10-30 21:59 ` [Qemu-devel] [Bug 1387881] " Joseph Salisbury
2014-10-30 22:00 ` [Qemu-devel] [Bug 1387881] Missing required logs Brad Figg
2014-10-30 22:00 ` [Qemu-devel] [Bug 1387881] Re: qemu fails to recognize full virtualization Joseph Salisbury
2014-10-30 22:13 ` Serge Hallyn
2014-10-30 22:18 ` Adam Stokes
2014-10-30 22:19 ` Adam Stokes
2014-10-31 15:05 ` David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] AlsaDevices.txt David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] BootDmesg.txt David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] CRDA.txt David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] Card0.Codecs.codec.3.txt David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] CurrentDmesg.txt David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] Lspci.txt David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] Lsusb.txt David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] PciMultimedia.txt David Britton
2014-10-31 15:05 ` [Qemu-devel] [Bug 1387881] ProcCpuinfo.txt David Britton
2014-10-31 15:06 ` [Qemu-devel] [Bug 1387881] ProcInterrupts.txt David Britton
2014-10-31 15:06 ` [Qemu-devel] [Bug 1387881] ProcModules.txt David Britton
2014-10-31 15:06 ` [Qemu-devel] [Bug 1387881] UdevDb.txt David Britton
2014-10-31 15:06 ` [Qemu-devel] [Bug 1387881] UdevLog.txt David Britton
2014-10-31 15:06 ` [Qemu-devel] [Bug 1387881] WifiSyslog.txt David Britton
2014-10-31 15:07 ` [Qemu-devel] [Bug 1387881] Re: qemu fails to recognize full virtualization David Britton
2014-10-31 15:20 ` Chris J Arges
2014-10-31 15:27 ` David Britton
2014-10-31 15:42 ` Chris J Arges
2014-10-31 17:43 ` Adam Stokes
2014-11-03 16:12 ` Serge Hallyn [this message]
2014-11-05 16:25 ` Chris J Arges
2014-11-05 16:33 ` Chris J Arges
2014-11-06 22:46 ` Chris J Arges
2014-11-07 17:01 ` Iggy
2014-11-10 22:25 ` Chris J Arges
2014-11-10 22:30 ` David Britton
2015-01-16 21:58 ` Serge Hallyn
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=20141103161210.GL10873@ubuntumail \
--to=1387881@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).