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

            Bug ID: 75981
           Summary: [Nested kvm on kvm]L2 guest reboot continuously when
                    create a rhel6u5(64bit) as L2 guest.
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.15.0-rc1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_...@kernel-bugs.osdl.org
          Reporter: chao.z...@intel.com
        Regression: No

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:198c74f43f0f5473f99967aead30ddc622804bc1
qemu.git Commit:411f491e0af173cf8f39347574941bd26fbae381
Host Kernel Version:3.15.0-rc1
Hardware:Romley_EP


Bug detailed description:
--------------------------
when create L1 guest with "-cpu host" , then create a 64bit rhel6u5 guest as L2
guest, the L2 guest reboot continuously.

note:
1. create a 64bit RHEL6u4 as L2 guest, the guest reboot continuously.
2. when creat a 32bit rhel6u5 guest as L2 guest, the L2 guest works fine
3. this should be a kernel bug:
kvm      +  qemu     = result
198c74f4 + 411f491e  = bad
0f689a33 + 411f491e  = good


Reproduce steps:
----------------
1. create L1 guest:
qemu-system-x86_64 -enable-kvm -m 8G -smp 4 -net nic,macaddr=00:12:41:51:14:16
-net tap,script=/etc/kvm/qemu-ifup ia32e_nested-kvm.img -cpu host,level=9
2. create L2 guest
qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none ia32e_rhel6u4.img


Current result:
----------------
64bit rhel6u5 as L2 guest reboot continuously

Expected result:
----------------
64bit rhel6u5 as L2 guest works fine

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

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to