Bug 1134700

Summary: Host call trace when booting L2 guest on wildcatpass Haswell machine
Product: Red Hat Enterprise Linux 7 Reporter: FuXiangChun <xfu>
Component: qemu-kvm-rhevAssignee: Bandan Das <bdas>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: choma, hhuang, juzhang, michen, pezhang, virt-maint, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-13 04:16:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description FuXiangChun 2014-08-28 07:05:11 UTC
Description of problem:
For wildcatpass host, host call trace when booting L2 guest. and guest show black screen.  

Version-Release number of selected component (if applicable):
host and guest kernel version:
3.10.0-145.el7.x86_64

qemu-kvm-rhev version:
qemu-kvm-rhev-2.1.0-2.el7.x86_64
qemu-kvm-1.5.3-69.el7.x86_64

How reproducible:
100%


Steps to Reproduce:
1. Enable nested virt on wildcatpass host
# cat /sys/module/kvm_intel/parameters/nested
Y
# cat /sys/module/kvm_intel/parameters/enable_shadow_vmcs
Y
# cat /sys/module/kvm_intel/parameters/ept
Y
# cat /sys/module/kvm_intel/parameters/enable_apicv
Y

2.Boot RHEL7.0 L1 guest on host with '-cpu host'

/usr/libexec/qemu-kvm -M pc-i440fx-rhel7.0.0 -cpu host -name RHEL-Server-7.0-64 -m 8G -smp 8,cores=2,threads=2,maxcpus=160 -nodefconfig -spice port=5903,disable-ticketing -drive file=/home/rhel7.qcow2,if=none,id=drive-virtio-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,media=disk,snapshot=off,bus=1,unit=1 -device virtio-blk-pci,scsi=on,drive=drive-virtio-disk,id=virtio-disk,bus=pci.0,addr=0x7,bootindex=1,physical_block_size=512,logical_block_size=512 -monitor stdio -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup,downscript=no,ifname=chenlin -device virtio-net-pci,mq=on,netdev=hostnet0,id=virtio-net-pci0,mac=00:01:02:03:04:07,bus=pci.0,addr=0x9,multifunction=on,status=on,gso=on,ioeventfd=on,vectors=8,indirect_desc=off,event_idx=off,guest_tso4=off,guest_tso6=on,guest_ecn=off,guest_ufo=on,host_tso4=off,host_tso6=on,host_ecn=on,mrg_rxbuf=off,ctrl_vq=on,host_ufo=on,mrg_rxbuf=on,ctrl_rx=on,ctrl_vlan=on,ctrl_rx_extra=on,ctrl_mac_addr=on -balloon virtio,id=bl1 -vga qxl -qmp tcp:0:4445,server,nowait

3.Boot L2 RHEL7.0 guest on L1 with Haswell

/usr/libexec/qemu-kvm -M pc-i440fx-rhel7.0.0 -name RHEL-Server-7.0-64 -m 4G -smp 1,cores=1,threads=1,maxcpus=160 -nodefconfig -spice port=5903,disable-ticketing -drive file=/home/rhel7.qcow2-guest,if=none,id=drive-virtio-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,media=disk,snapshot=off,bus=1,unit=1 -device virtio-blk-pci,scsi=on,drive=drive-virtio-disk,id=virtio-disk,bus=pci.0,addr=0x7,bootindex=1,physical_block_size=512,logical_block_size=512 -monitor stdio  -balloon virtio,id=bl1 -vga qxl -qmp tcp:0:4445,server,nowait

Actual results:
Host call trace

[ 6945.191942] WARNING: at arch/x86/kvm/vmx.c:8686 nested_vmx_vmexit+0x282/0x290 [kvm_intel]()
[ 6945.191953] Modules linked in: vhost_net macvtap macvlan tun kvm_intel kvm sg bridge stp llc intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ixgbe ptp aesni_intel pps_core lrw iTCO_wdt mdio gf128mul glue_helper iTCO_vendor_support dca ablk_helper mei_me lpc_ich cryptd pcspkr i2c_i801 mfd_core mei shpchp wmi ipmi_si ipmi_msghandler acpi_pad acpi_power_meter mperf xfs libcrc32c sd_mod sr_mod cdrom crc_t10dif crct10dif_common mgag200 syscopyarea sysfillrect sysimgblt i2c_algo_bit drm_kms_helper ahci ttm libahci drm libata i2c_core dm_mirror dm_region_hash dm_log dm_mod [last unloaded: kvm]
[ 6945.191954] CPU: 14 PID: 4093 Comm: qemu-kvm Tainted: G        W   --------------   3.10.0-145.el7.x86_64 #1
[ 6945.191955] Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS GRNDSDP1.86B.0037.D10.1408060946 08/06/2014
[ 6945.191958]  0000000000000000 000000004c295ac9 ffff88038f5a9c60 ffffffff815eb72b
[ 6945.191960]  ffff88038f5a9c98 ffffffff8106a6c1 ffff88085eb90000 ffff8802e6b67000
[ 6945.191962]  0000000000000001 ffff880466ef0000 ffff88085eb90030 ffff88038f5a9ca8
[ 6945.191962] Call Trace:
[ 6945.191965]  [<ffffffff815eb72b>] dump_stack+0x19/0x1b
[ 6945.191967]  [<ffffffff8106a6c1>] warn_slowpath_common+0x61/0x80
[ 6945.191968]  [<ffffffff8106a7ea>] warn_slowpath_null+0x1a/0x20
[ 6945.191970]  [<ffffffffa046ddb2>] nested_vmx_vmexit+0x282/0x290 [kvm_intel]
[ 6945.191972]  [<ffffffffa0465e48>] ? vmx_sync_pir_to_irr+0x28/0x30 [kvm_intel]
[ 6945.191974]  [<ffffffffa046dec0>] vmx_check_nested_events+0x100/0x120 [kvm_intel]
[ 6945.191981]  [<ffffffffa04e8d2f>] vcpu_enter_guest+0x42f/0xd50 [kvm]
[ 6945.191983]  [<ffffffffa0469d6b>] ? vmx_deliver_posted_interrupt+0x3b/0x80 [kvm_intel]
[ 6945.191989]  [<ffffffffa0508722>] ? __apic_accept_irq+0x162/0x2b0 [kvm]
[ 6945.191994]  [<ffffffffa04ee848>] kvm_arch_vcpu_ioctl_run+0x208/0x480 [kvm]
[ 6945.191998]  [<ffffffffa04d8e3a>] kvm_vcpu_ioctl+0x2aa/0x580 [kvm]
[ 6945.192000]  [<ffffffff812015d1>] ? fsnotify+0x251/0x350
[ 6945.192002]  [<ffffffff811d2765>] do_vfs_ioctl+0x2e5/0x4c0
[ 6945.192004]  [<ffffffff812672de>] ? file_has_perm+0xae/0xc0
[ 6945.192006]  [<ffffffff811d29e1>] SyS_ioctl+0xa1/0xc0
[ 6945.192008] ---[ end trace a300483cabb64f90 ]---

2. L2 guest black screen(can not boot)


Expected results:
L2 guest boot successfully

Additional info:
QE didn't test other host. not sure if other host has the same issue.

Comment 4 FuXiangChun 2015-06-23 01:49:29 UTC
I have reserved a wildcatpass host in beaker.  will update test result to bz asap.

Comment 5 FuXiangChun 2015-06-30 07:34:48 UTC
I re-tested this bug with 3.10.0-229.7.2.el7.x86_64.  the bug still can be reproduced.  As I cann't connect to it after host can be updated to the latest kernel(in beaker). so I didn't update host and guest kernel to the latest kernel version.  If the kernel is not sure whether the recent kernel fixed it. please tell me.  I will reserve another host in beaker.

Comment 9 Bandan Das 2015-07-13 04:16:35 UTC
This is no longer reproducible with recent builds, closing this as CURRENTRELEASE. Please feel free to reopen if the issue persists.