View Issue Details

IDProjectCategoryView StatusLast Update
0015395CentOS-6kernelpublic2018-10-20 18:25
Reporterngstargate 
PrioritynormalSeveritycrashReproducibilityalways
Status newResolutionopen 
Product Version6.10 
Target VersionFixed in Version 
Summary0015395: Kernel error on KVM host, any guest VM's unstable
DescriptionI have Intel servers running CentOS 6.10 as KVM host and on it guests
running CentOS/Debian/Ubuntu/Windows.

Since the kernel update on CentOS 6.10 > kernel-2.6.32-754.el6.x86_64 I got kernel errors in log.
Guest VM's unstable, hangs or reboots.

Reverting CentOS 6.10 host to kernel-2.6.32-754.el6.x86_64 fixes the problem.
Fragment from log attached.
TagsNo tags attached.

Activities

ngstargate

ngstargate

2018-10-20 05:16

reporter  

kernel_errors.txt (3,752 bytes)
Oct 20 06:30:42 kvm66 kernel: vmwrite error: reg 6800 value a069b2d0 (err -1603685680)
Oct 20 06:30:42 kvm66 kernel: Pid: 28622, comm: qemu-kvm Not tainted 2.6.32-754.6.3.el6.x86_64 #1
Oct 20 06:30:42 kvm66 kernel: Call Trace:
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa0697eec>] ? vmwrite_error+0x2c/0x30 [kvm_intel]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa0697f10>] ? vmcs_writel+0x20/0x30 [kvm_intel]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa069b317>] ? vmx_fpu_activate+0x47/0xc0 [kvm_intel]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa0632247>] ? kvm_arch_vcpu_create+0x37/0x50 [kvm]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa062c2b1>] ? kvm_vm_ioctl+0x601/0x1050 [kvm]
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8106718c>] ? enqueue_task+0x6c/0x90
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8106335d>] ? check_preempt_curr+0x6d/0xa0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff810706f6>] ? try_to_wake_up+0x256/0x3f0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8124afd1>] ? avc_has_perm+0x71/0x90
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8124cdc4>] ? inode_has_perm+0x54/0xa0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8109b31f>] ? do_notify_parent+0x16f/0x230
Oct 20 06:30:42 kvm66 kernel: [<ffffffff811b7159>] ? vfs_ioctl+0x29/0xc0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff811b765a>] ? do_vfs_ioctl+0x3ca/0x590
Oct 20 06:30:42 kvm66 kernel: [<ffffffff811b78a1>] ? sys_ioctl+0x81/0xa0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff81564272>] ? system_call_after_swapgs+0xa2/0x152
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8156427e>] ? system_call_after_swapgs+0xae/0x152
Oct 20 06:30:42 kvm66 kernel: [<ffffffff81564272>] ? system_call_after_swapgs+0xa2/0x152
Oct 20 06:30:42 kvm66 kernel: [<ffffffff81564341>] ? system_call_fastpath+0x1f/0x3a
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8156427e>] ? system_call_after_swapgs+0xae/0x152
Oct 20 06:30:42 kvm66 kernel: vmwrite error: reg 4004 value 60042 (err 393282)
Oct 20 06:30:42 kvm66 kernel: Pid: 28622, comm: qemu-kvm Not tainted 2.6.32-754.6.3.el6.x86_64 #1
Oct 20 06:30:42 kvm66 kernel: Call Trace:
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa0697eec>] ? vmwrite_error+0x2c/0x30 [kvm_intel]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa0697f10>] ? vmcs_writel+0x20/0x30 [kvm_intel]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa06981d1>] ? update_exception_bitmap+0x61/0x70 [kvm_intel]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa069b347>] ? vmx_fpu_activate+0x77/0xc0 [kvm_intel]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa0632247>] ? kvm_arch_vcpu_create+0x37/0x50 [kvm]
Oct 20 06:30:42 kvm66 kernel: [<ffffffffa062c2b1>] ? kvm_vm_ioctl+0x601/0x1050 [kvm]
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8106718c>] ? enqueue_task+0x6c/0x90
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8106335d>] ? check_preempt_curr+0x6d/0xa0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff810706f6>] ? try_to_wake_up+0x256/0x3f0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8124afd1>] ? avc_has_perm+0x71/0x90
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8124cdc4>] ? inode_has_perm+0x54/0xa0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8109b31f>] ? do_notify_parent+0x16f/0x230
Oct 20 06:30:42 kvm66 kernel: [<ffffffff811b7159>] ? vfs_ioctl+0x29/0xc0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff811b765a>] ? do_vfs_ioctl+0x3ca/0x590
Oct 20 06:30:42 kvm66 kernel: [<ffffffff811b78a1>] ? sys_ioctl+0x81/0xa0
Oct 20 06:30:42 kvm66 kernel: [<ffffffff81564272>] ? system_call_after_swapgs+0xa2/0x152
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8156427e>] ? system_call_after_swapgs+0xae/0x152
Oct 20 06:30:42 kvm66 kernel: [<ffffffff81564272>] ? system_call_after_swapgs+0xa2/0x152
Oct 20 06:30:42 kvm66 kernel: [<ffffffff81564341>] ? system_call_fastpath+0x1f/0x3a
Oct 20 06:30:42 kvm66 kernel: [<ffffffff8156427e>] ? system_call_after_swapgs+0xae/0x152
kernel_errors.txt (3,752 bytes)
toracat

toracat

2018-10-20 17:49

manager   ~0032953

So, the last "good" kernel is 2.6.32-754.el6 and the first "bad" one is 2.6.32-754.2.1.el6 ?
ngstargate

ngstargate

2018-10-20 18:25

reporter   ~0032954

Yes, that's right

Issue History

Date Modified Username Field Change
2018-10-20 05:16 ngstargate New Issue
2018-10-20 05:16 ngstargate File Added: kernel_errors.txt
2018-10-20 17:49 toracat Note Added: 0032953
2018-10-20 18:25 ngstargate Note Added: 0032954