[Qemu-devel] [Bug 994378] [NEW] Nested-virt)L 1 (kvm on kvm)guest panic with parameter “-c pu host” in qemu command line.

[Yongjie Ren]

Public bug reported:

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9
qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231
Host Kernel Version:3.4.0-rc3
Hardware:WSM-EP, Romley-EP


Bug detailed description:
--------------------------
(KVM on KVM) L1 guest panic when starting the L1 guest with “-cpu host” 
parameter in qemu command line.

Note:
1. when creating guest with “-cpu qemu64,+vmx”, L1 guest and L2 guest can boot
up. 
2. This should be a qemu-kvm bug. using '-cpu host' parameter, the following is 
the result.
Kvm        + qemu-kvm =result
19853301 + 69abebf2  = bad
19853301 + 44755ea3  = good
3. when booting up the guest with  the good commit of 19853301 + 44755ea3, you 
can see some
error info, but nested virt works fine. (L1 and L2 guest can boot up.)
“error: feature "i64" not available in set
error: bad option value [extfeature_edx = i64 xd syscall]” 

some logs 
address@hidden x86_64-softmmu]# ./qemu-system-x86_64 -m 2048 -net 
nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/nested-kvm.qcow 
-cpu host
error: feature "i64" not available in set
error: bad option value [extfeature_edx = i64 xd syscall]
error: feature "i64" not available in set
error: bad option value [extfeature_edx = i64 xd syscall]
error: feature "i64" not available in set
error: bad option value [extfeature_edx = i64 syscall xd]
error: feature "i64" not available in set
error: bad option value [extfeature_edx = i64 syscall xd]
VNC server running on `::1:5900'


Reproduce steps:
----------------
1.start up a host with kvm (commit: 19853301)
2.rmmod kvm_intel
3.modprobe kvm_intel nested=1
4.qemu-system-x86_64 -m 2048  -hda L1-kvm.img -cpu host


Current result:
----------------
L1 guest panic.

Expected result:
----------------
L1 guest and L2 guest boot up correctly.

Basic root-causing log:
----------------------

** Affects: qemu
     Importance: Undecided
         Status: New

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

Title:
  Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in
  qemu command line.

Status in QEMU:
  New

Bug description:
  Environment:
  ------------
  Host OS (ia32/ia32e/IA64):ia32e
  Guest OS (ia32/ia32e/IA64):ia32e
  Guest OS Type (Linux/Windows):Linux
  kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9
  qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231
  Host Kernel Version:3.4.0-rc3
  Hardware:WSM-EP, Romley-EP

  
  Bug detailed description:
  --------------------------
  (KVM on KVM) L1 guest panic when starting the L1 guest with “-cpu host” 
parameter in qemu command line.

  Note:
  1. when creating guest with “-cpu qemu64,+vmx”, L1 guest and L2 guest can boot
  up. 
  2. This should be a qemu-kvm bug. using '-cpu host' parameter, the following 
is the result.
  Kvm        + qemu-kvm =result
  19853301 + 69abebf2  = bad
  19853301 + 44755ea3  = good
  3. when booting up the guest with  the good commit of 19853301 + 44755ea3, 
you can see some
  error info, but nested virt works fine. (L1 and L2 guest can boot up.)
  “error: feature "i64" not available in set
  error: bad option value [extfeature_edx = i64 xd syscall]” 

  some logs 
  address@hidden x86_64-softmmu]# ./qemu-system-x86_64 -m 2048 -net 
nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/nested-kvm.qcow 
-cpu host
  error: feature "i64" not available in set
  error: bad option value [extfeature_edx = i64 xd syscall]
  error: feature "i64" not available in set
  error: bad option value [extfeature_edx = i64 xd syscall]
  error: feature "i64" not available in set
  error: bad option value [extfeature_edx = i64 syscall xd]
  error: feature "i64" not available in set
  error: bad option value [extfeature_edx = i64 syscall xd]
  VNC server running on `::1:5900'


  Reproduce steps:
  ----------------
  1.start up a host with kvm (commit: 19853301)
  2.rmmod kvm_intel
  3.modprobe kvm_intel nested=1
  4.qemu-system-x86_64 -m 2048  -hda L1-kvm.img -cpu host


  Current result:
  ----------------
  L1 guest panic.

  Expected result:
  ----------------
  L1 guest and L2 guest boot up correctly.

  Basic root-causing log:
  ----------------------

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