Re: KVM broken after suspend in most recent kernels.
On Tue, 2020-05-26 at 22:13 -0700, Sean Christopherson wrote: > On Mon, May 25, 2020 at 09:15:57PM +0800, Brad Campbell wrote: > > > When you mean that KVM is broken after suspend, you mean that you > > > can't > > > start new VMs after suspend, or do VMs that were running before > > > suspend > > > break? I see the later on my machine. I have AMD system though, > > > so most > > > likely this is another bug. > > > > > > Looking at the commit, I suspect that we indeed should set the > > > IA32_FEAT_CTL > > > after resume from ram, since suspend to ram might count as a > > > complete CPU > > > reset. > > > > > > > One of those "I should have clarified that" moments immediately > > after I > > pressed send. I've not tried suspending with a VM running. It's > > "can't start > > new VMs after suspend". > > Don't bother testing suspending with a VM, the only thing that will > be > different is that your system will hang on resume instead when > running a > VM. If there are active VMs, KVM automatically re-enables VMX via > VMXON > after resume, and VMXON is what's faulting. > > Odds are good the firmware simply isn't initializing IA32_FEAT_CTL, > ever. > The kernel handles the boot-time case, but I (obviously) didn't > consider > the suspend case. I'll work on a patch. This is exactly what I was thinking about this as well. Best regards, Maxim Levitsky >
Re: KVM broken after suspend in most recent kernels.
On Mon, May 25, 2020 at 09:15:57PM +0800, Brad Campbell wrote: > >When you mean that KVM is broken after suspend, you mean that you can't > >start new VMs after suspend, or do VMs that were running before suspend > >break? I see the later on my machine. I have AMD system though, so most > >likely this is another bug. > > > >Looking at the commit, I suspect that we indeed should set the IA32_FEAT_CTL > >after resume from ram, since suspend to ram might count as a complete CPU > >reset. > > > > One of those "I should have clarified that" moments immediately after I > pressed send. I've not tried suspending with a VM running. It's "can't start > new VMs after suspend". Don't bother testing suspending with a VM, the only thing that will be different is that your system will hang on resume instead when running a VM. If there are active VMs, KVM automatically re-enables VMX via VMXON after resume, and VMXON is what's faulting. Odds are good the firmware simply isn't initializing IA32_FEAT_CTL, ever. The kernel handles the boot-time case, but I (obviously) didn't consider the suspend case. I'll work on a patch.
Re: KVM broken after suspend in most recent kernels.
On 25/5/20 7:46 pm, Maxim Levitsky wrote: On Sun, 2020-05-24 at 18:43 +0800, Brad Campbell wrote: On 24/5/20 12:50 pm, Brad Campbell wrote: G'day all. Machine is a Macbook Pro Retina ~ 2014. Kernels are always vanilla kernel and compiled on the machine. No additional patches. vendor_id: GenuineIntel cpu family: 6 model: 69 model name: Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz stepping: 1 microcode: 0x25 cpu MHz: 2795.034 cache size: 3072 KB physical id: 0 siblings: 4 core id: 1 cpu cores: 2 apicid: 3 initial apicid: 3 fpu: yes fpu_exception: yes cpuid level: 13 wp: yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d vmx flags: vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips: 5199.87 clflush size: 64 cache_alignment: 64 address sizes: 39 bits physical, 48 bits virtual KVM worked fine in kernels somewhere prior to 5.4-5.5. KVM works fine in later kernels up to and including 5.7.0-rc6 after a clean boot. It does not work after a suspend. I can't actually bisect this because there is a bug in earlier kernels that breaks the suspend method used which requires manual patching to work around. This is using qemu version 5.0.0, but also happens with 4.2.0. In kernels earlier than 5.7 it results in either an immediate hard lock, or a GPF that results in progressive system freeze until a hard reboot is required (won't flush to disk so no logs get recorded and I have no serial or netconsole ability). In 5.7-rc6 it results in the following trace and thankfully no further issues (so I can get the logs and report it). I can and will perform any required testing and debugging, but this machine suspends with pm-utils s2both, and that is broken between about 5.4 & 5.6 due to swapfile locking issues, which makes actual bisection very, very difficult as it *requires* a suspend/resume to trigger the bug. [ 227.715173] [ cut here ] [ 227.715176] VMXON faulted, MSR_IA32_FEAT_CTL (0x3a) = 0x4 [ 227.715194] WARNING: CPU: 0 PID: 5502 at arch/x86/kvm/vmx/vmx.c:2239 hardware_enable+0x167/0x180 [kvm_intel] [ 227.715195] Modules linked in: brcmfmac xhci_pci xhci_hcd cmac bnep iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv4 ip_tables x_tables nfsd bridge stp llc appletouch brcmutil snd_hda_codec_hdmi sha256_ssse3 snd_hda_codec_cirrus snd_hda_codec_generic sha256_generic libsha256 x86_pkg_temp_thermal coretemp btusb kvm_intel btrtl kvm btbcm btintel irqbypass bluetooth cfg80211 snd_hda_intel ecdh_generic ecc snd_intel_dspcfg bcm5974 rfkill snd_hda_codec snd_hwdep snd_hda_core snd_pcm_oss snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915 snd_seq snd_seq_device snd_timer i2c_algo_bit iosf_mbi drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops snd drm intel_gtt agpgart evdev apple_bl video soundcore hid_apple usb_storage hid_generic usbhid hid dm_crypt dm_mod i2c_i801 i2c_core sg usbcore usb_common [last unloaded: xhci_hcd] [ 227.715221] CPU: 0 PID: 5502 Comm: qemu Not tainted 5.7.0-rc6+ #15 [ 227.715222] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS 159.0.0.0.0 02/05/2020 [ 227.715225] RIP: 0010:hardware_enable+0x167/0x180 [kvm_intel] [ 227.715227] Code: 01 00 01 b9 3a 00 00 00 0f 32 31 c9 48 c1 e2 20 be ef be ad de 48 c7 c7 68 fd bb c0 48 09 c2 85 c9 48 0f 44 f2 e8 43 78 4f dc <0f> 0b eb 8a 48 8b 15 ce 89 06 dd e9 c7 fe ff ff 66 0f 1f 84 00 00 [ 227.715228] RSP: 0018:97091d873df8 EFLAGS: 00010092 [ 227.715229] RAX: 002d RBX: 0046 RCX: 0007 [ 227.715230] RDX: 0007 RSI: 0082 RDI: 97091f2187a0 [ 227.715231] RBP: 97091d873e10 R08: 0008 R09: 0495 [ 227.715232] R10: 0010 R11: 97091d873c6d R12: [ 227.715233] R13: 0286 R14: b5d08015e010 R15: [ 227.715234] FS: 7f1468fd33c0() GS:97091f20() knlGS: [ 227.715235] CS: 0010 DS: ES: CR0: 80050033 [ 227.715236] CR2: 563b54c7201d CR3: 00043f43f001 CR4: 001626f0 [ 227.7
Re: KVM broken after suspend in most recent kernels.
On Sun, 2020-05-24 at 18:43 +0800, Brad Campbell wrote: > > On 24/5/20 12:50 pm, Brad Campbell wrote: > > G'day all. > > > > Machine is a Macbook Pro Retina ~ 2014. Kernels are always vanilla kernel > > and compiled on the machine. No additional patches. > > > > vendor_id: GenuineIntel > > cpu family: 6 > > model: 69 > > model name: Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz > > stepping: 1 > > microcode: 0x25 > > cpu MHz: 2795.034 > > cache size: 3072 KB > > physical id: 0 > > siblings: 4 > > core id: 1 > > cpu cores: 2 > > apicid: 3 > > initial apicid: 3 > > fpu: yes > > fpu_exception: yes > > cpuid level: 13 > > wp: yes > > flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > > pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl > > xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl > > vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe > > popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault > > epb invpcid_single ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept > > vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt > > dtherm ida arat pln pts md_clear flush_l1d > > vmx flags: vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb > > flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple > > bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds > > swapgs itlb_multihit > > bogomips: 5199.87 > > clflush size: 64 > > cache_alignment: 64 > > address sizes: 39 bits physical, 48 bits virtual > > > > > > KVM worked fine in kernels somewhere prior to 5.4-5.5. > > > > KVM works fine in later kernels up to and including 5.7.0-rc6 after a clean > > boot. It does not work after a suspend. > > > > I can't actually bisect this because there is a bug in earlier kernels that > > breaks the suspend method used which requires manual patching to work > > around. > > > > This is using qemu version 5.0.0, but also happens with 4.2.0. > > > > In kernels earlier than 5.7 it results in either an immediate hard lock, or > > a GPF that results in progressive system freeze until a hard reboot is > > required (won't flush to disk so no logs get recorded and I have no serial > > or netconsole ability). In 5.7-rc6 it results in the following trace and > > thankfully no further issues (so I can get the logs and report it). > > > > I can and will perform any required testing and debugging, but this machine > > suspends with pm-utils s2both, and that is broken between about 5.4 & 5.6 > > due to swapfile locking issues, which makes actual bisection very, very > > difficult as it *requires* a suspend/resume to trigger the bug. > > > > [ 227.715173] [ cut here ] > > [ 227.715176] VMXON faulted, MSR_IA32_FEAT_CTL (0x3a) = 0x4 > > [ 227.715194] WARNING: CPU: 0 PID: 5502 at arch/x86/kvm/vmx/vmx.c:2239 > > hardware_enable+0x167/0x180 [kvm_intel] > > [ 227.715195] Modules linked in: brcmfmac xhci_pci xhci_hcd cmac bnep > > iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv4 ip_tables > > x_tables nfsd bridge stp llc appletouch brcmutil snd_hda_codec_hdmi > > sha256_ssse3 snd_hda_codec_cirrus snd_hda_codec_generic sha256_generic > > libsha256 x86_pkg_temp_thermal coretemp btusb kvm_intel btrtl kvm btbcm > > btintel irqbypass bluetooth cfg80211 snd_hda_intel ecdh_generic ecc > > snd_intel_dspcfg bcm5974 rfkill snd_hda_codec snd_hwdep snd_hda_core > > snd_pcm_oss snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915 > > snd_seq snd_seq_device snd_timer i2c_algo_bit iosf_mbi drm_kms_helper > > syscopyarea sysfillrect sysimgblt fb_sys_fops snd drm intel_gtt agpgart > > evdev apple_bl video soundcore hid_apple usb_storage hid_generic usbhid hid > > dm_crypt dm_mod i2c_i801 i2c_core sg usbcore usb_common [last unloaded: > > xhci_hcd] > > [ 227.715221] CPU: 0 PID: 5502 Comm: qemu Not tainted 5.7.0-rc6+ #15 > > [ 227.715222] Hardware name: Apple Inc. > > MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS 159.0.0.0.0 02/05/2020 > > [ 227.715225] RIP: 0010:hardware_enable+0x167/0x180 [kvm_intel] > > [ 227.715227] Code: 01 00 01 b9 3a 00 00 00 0f 32 31 c9 48 c1 e2 20 be ef > > be ad de 48 c7 c7 68 fd bb c0 48 09 c2 85 c9 48 0f 44 f2 e8 43 78 4f dc > > <0f> 0b eb 8a 48 8b 15 ce 89 06 dd e9 c7 fe ff ff 66 0f 1f 84 00 00 > > [ 227.715228] RSP: 0018:97091d873df8 EFLAGS: 00010092 > > [ 227.715229] RAX: 002d RBX: 0046 RCX: > > 0007 > > [ 227.715230] RDX: 0007 RSI: 0082 RDI: > > 97091f2187a0 > > [ 227.715231] RBP: 97091d873e10 R08: 0008 R09: > > 0495 > > [ 227.715232] R10: 0010 R11: 97091d873c6d R12:
Re: KVM broken after suspend in most recent kernels.
On 24/5/20 12:50 pm, Brad Campbell wrote: G'day all. Machine is a Macbook Pro Retina ~ 2014. Kernels are always vanilla kernel and compiled on the machine. No additional patches. vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz stepping : 1 microcode : 0x25 cpu MHz : 2795.034 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 5199.87 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual KVM worked fine in kernels somewhere prior to 5.4-5.5. KVM works fine in later kernels up to and including 5.7.0-rc6 after a clean boot. It does not work after a suspend. I can't actually bisect this because there is a bug in earlier kernels that breaks the suspend method used which requires manual patching to work around. This is using qemu version 5.0.0, but also happens with 4.2.0. In kernels earlier than 5.7 it results in either an immediate hard lock, or a GPF that results in progressive system freeze until a hard reboot is required (won't flush to disk so no logs get recorded and I have no serial or netconsole ability). In 5.7-rc6 it results in the following trace and thankfully no further issues (so I can get the logs and report it). I can and will perform any required testing and debugging, but this machine suspends with pm-utils s2both, and that is broken between about 5.4 & 5.6 due to swapfile locking issues, which makes actual bisection very, very difficult as it *requires* a suspend/resume to trigger the bug. [ 227.715173] [ cut here ] [ 227.715176] VMXON faulted, MSR_IA32_FEAT_CTL (0x3a) = 0x4 [ 227.715194] WARNING: CPU: 0 PID: 5502 at arch/x86/kvm/vmx/vmx.c:2239 hardware_enable+0x167/0x180 [kvm_intel] [ 227.715195] Modules linked in: brcmfmac xhci_pci xhci_hcd cmac bnep iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv4 ip_tables x_tables nfsd bridge stp llc appletouch brcmutil snd_hda_codec_hdmi sha256_ssse3 snd_hda_codec_cirrus snd_hda_codec_generic sha256_generic libsha256 x86_pkg_temp_thermal coretemp btusb kvm_intel btrtl kvm btbcm btintel irqbypass bluetooth cfg80211 snd_hda_intel ecdh_generic ecc snd_intel_dspcfg bcm5974 rfkill snd_hda_codec snd_hwdep snd_hda_core snd_pcm_oss snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915 snd_seq snd_seq_device snd_timer i2c_algo_bit iosf_mbi drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops snd drm intel_gtt agpgart evdev apple_bl video soundcore hid_apple usb_storage hid_generic usbhid hid dm_crypt dm_mod i2c_i801 i2c_core sg usbcore usb_common [last unloaded: xhci_hcd] [ 227.715221] CPU: 0 PID: 5502 Comm: qemu Not tainted 5.7.0-rc6+ #15 [ 227.715222] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS 159.0.0.0.0 02/05/2020 [ 227.715225] RIP: 0010:hardware_enable+0x167/0x180 [kvm_intel] [ 227.715227] Code: 01 00 01 b9 3a 00 00 00 0f 32 31 c9 48 c1 e2 20 be ef be ad de 48 c7 c7 68 fd bb c0 48 09 c2 85 c9 48 0f 44 f2 e8 43 78 4f dc <0f> 0b eb 8a 48 8b 15 ce 89 06 dd e9 c7 fe ff ff 66 0f 1f 84 00 00 [ 227.715228] RSP: 0018:97091d873df8 EFLAGS: 00010092 [ 227.715229] RAX: 002d RBX: 0046 RCX: 0007 [ 227.715230] RDX: 0007 RSI: 0082 RDI: 97091f2187a0 [ 227.715231] RBP: 97091d873e10 R08: 0008 R09: 0495 [ 227.715232] R10: 0010 R11: 97091d873c6d R12: [ 227.715233] R13: 0286 R14: b5d08015e010 R15: [ 227.715234] FS: 7f1468fd33c0() GS:97091f20() knlGS: [ 227.715235] CS: 0010 DS: ES: CR0: 80050033 [ 227.715236] CR2: 563b54c7201d CR3: 00043f43f001 CR4: 001626f0 [ 227.715237] DR0: DR1: DR2: [ 227.715238] DR3:
KVM broken after suspend in most recent kernels.
G'day all. Machine is a Macbook Pro Retina ~ 2014. Kernels are always vanilla kernel and compiled on the machine. No additional patches. vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz stepping: 1 microcode : 0x25 cpu MHz : 2795.034 cache size : 3072 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips: 5199.87 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual KVM worked fine in kernels somewhere prior to 5.4-5.5. KVM works fine in later kernels up to and including 5.7.0-rc6 after a clean boot. It does not work after a suspend. I can't actually bisect this because there is a bug in earlier kernels that breaks the suspend method used which requires manual patching to work around. This is using qemu version 5.0.0, but also happens with 4.2.0. In kernels earlier than 5.7 it results in either an immediate hard lock, or a GPF that results in progressive system freeze until a hard reboot is required (won't flush to disk so no logs get recorded and I have no serial or netconsole ability). In 5.7-rc6 it results in the following trace and thankfully no further issues (so I can get the logs and report it). I can and will perform any required testing and debugging, but this machine suspends with pm-utils s2both, and that is broken between about 5.4 & 5.6 due to swapfile locking issues, which makes actual bisection very, very difficult as it *requires* a suspend/resume to trigger the bug. [ 227.715173] [ cut here ] [ 227.715176] VMXON faulted, MSR_IA32_FEAT_CTL (0x3a) = 0x4 [ 227.715194] WARNING: CPU: 0 PID: 5502 at arch/x86/kvm/vmx/vmx.c:2239 hardware_enable+0x167/0x180 [kvm_intel] [ 227.715195] Modules linked in: brcmfmac xhci_pci xhci_hcd cmac bnep iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv4 ip_tables x_tables nfsd bridge stp llc appletouch brcmutil snd_hda_codec_hdmi sha256_ssse3 snd_hda_codec_cirrus snd_hda_codec_generic sha256_generic libsha256 x86_pkg_temp_thermal coretemp btusb kvm_intel btrtl kvm btbcm btintel irqbypass bluetooth cfg80211 snd_hda_intel ecdh_generic ecc snd_intel_dspcfg bcm5974 rfkill snd_hda_codec snd_hwdep snd_hda_core snd_pcm_oss snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915 snd_seq snd_seq_device snd_timer i2c_algo_bit iosf_mbi drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops snd drm intel_gtt agpgart evdev apple_bl video soundcore hid_apple usb_storage hid_generic usbhid hid dm_crypt dm_mod i2c_i801 i2c_core sg usbcore usb_common [last unloaded: xhci_hcd] [ 227.715221] CPU: 0 PID: 5502 Comm: qemu Not tainted 5.7.0-rc6+ #15 [ 227.715222] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS 159.0.0.0.0 02/05/2020 [ 227.715225] RIP: 0010:hardware_enable+0x167/0x180 [kvm_intel] [ 227.715227] Code: 01 00 01 b9 3a 00 00 00 0f 32 31 c9 48 c1 e2 20 be ef be ad de 48 c7 c7 68 fd bb c0 48 09 c2 85 c9 48 0f 44 f2 e8 43 78 4f dc <0f> 0b eb 8a 48 8b 15 ce 89 06 dd e9 c7 fe ff ff 66 0f 1f 84 00 00 [ 227.715228] RSP: 0018:97091d873df8 EFLAGS: 00010092 [ 227.715229] RAX: 002d RBX: 0046 RCX: 0007 [ 227.715230] RDX: 0007 RSI: 0082 RDI: 97091f2187a0 [ 227.715231] RBP: 97091d873e10 R08: 0008 R09: 0495 [ 227.715232] R10: 0010 R11: 97091d873c6d R12: [ 227.715233] R13: 0286 R14: b5d08015e010 R15: [ 227.715234] FS: 7f1468fd33c0() GS:97091f20() knlGS: [ 227.715235] CS: 0010 DS: ES: CR0: 80050033 [ 227.715236] CR2: 563b54c7201d CR3: 00043f43f001 CR4: 001626f0 [ 227.715237] DR0: DR1: DR2: [ 227.715238] DR3:
