[Bug 1165206] Xen 4.12 DomU hang / freeze / stall / NMI watchdog bug soft lockup CPU #0 stuck under high load / upstream with workaround
http://bugzilla.suse.com/show_bug.cgi?id=1165206 http://bugzilla.suse.com/show_bug.cgi?id=1165206#c18 Glen Barney <glenbarney@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(glenbarney@gmail. | |com) | --- Comment #18 from Glen Barney <glenbarney@gmail.com> --- Okay, packages downloaded and installed successfully! Here are some portions of xl dmesg: (XEN) Xen version 4.12.2_03-lp151.1 (abuild@suse.de) (gcc (SUSE Linux) 7.5.0) debug=n Thu Mar 19 20:51:14 UTC 2020 (XEN) Latest ChangeSet: (XEN) Bootloader: GRUB2 2.02 (XEN) Command line: dom0_mem=4G dom0_max_vcpus=4 dom0_vcpus_pin gnttab_max_frames=256 vga=gfx-1024x768x16 (XEN) ACPI: 32/64X FACS address mismatch in FADT - 7b8f3000/0000000000000000, using 32 (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47 (XEN) IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71 (XEN) Enabling APIC mode: Phys. Using 3 I/O APICs (XEN) Not enabling x2APIC (upon firmware request) (XEN) xstate: size: 0x340 and states: 0x7 (XEN) CMCI: threshold 0x2 too large for CPU0 bank 17, using 0x1 (XEN) CMCI: threshold 0x2 too large for CPU0 bank 18, using 0x1 (XEN) CMCI: threshold 0x2 too large for CPU0 bank 19, using 0x1 (XEN) Speculative mitigation facilities: (XEN) Hardware features: IBRS/IBPB STIBP L1D_FLUSH SSBD MD_CLEAR (XEN) Compiled-in support: INDIRECT_THUNK SHADOW_PAGING (XEN) Xen settings: BTI-Thunk RETPOLINE, SPEC_CTRL: IBRS- SSBD-, Other: IBPB L1D_FLUSH VERW (XEN) L1TF: believed vulnerable, maxphysaddr L1D 46, CPUID 46, Safe address 300000000000 (XEN) Support for HVM VMs: MSR_SPEC_CTRL RSB EAGER_FPU MD_CLEAR (XEN) Support for PV VMs: MSR_SPEC_CTRL RSB EAGER_FPU MD_CLEAR (XEN) XPTI (64-bit PV only): Dom0 enabled, DomU enabled (with PCID) (XEN) PV L1TF shadowing: Dom0 disabled, DomU enabled (XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2) (XEN) Initializing Credit2 scheduler (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2597.008 MHz processor. (XEN) Initing memory sharing. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) Allocated console ring of 64 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) - APIC Register Virtualization (XEN) - Virtual Interrupt Delivery (XEN) - Posted Interrupt Processing (XEN) - VMCS shadowing (XEN) - VM Functions (XEN) HVM: ASIDs enabled. (XEN) VMX: Disabling executable EPT superpages due to CVE-2018-12207 (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) CMCI: threshold 0x2 too large for CPU16 bank 17, using 0x1 (XEN) CMCI: threshold 0x2 too large for CPU16 bank 18, using 0x1 (XEN) CMCI: threshold 0x2 too large for CPU16 bank 19, using 0x1 (XEN) *************************************************** (XEN) Booted on L1TF-vulnerable hardware with SMT/Hyperthreading (XEN) enabled. Please assess your configuration and choose an (XEN) explicit 'smt=<bool>' setting. See XSA-273. (XEN) *************************************************** (XEN) Booted on MLPDS/MFBDS-vulnerable hardware with SMT/Hyperthreading (XEN) enabled. Mitigations will not be fully effective. Please (XEN) choose an explicit smt=<bool> setting. See XSA-297. (XEN) *************************************************** Interestingly, my guests in /etc/xen/auto didn't start, even though xendomains was still showing enabled. I had to systemctl start xendomains by hand to make them go. Not a big deal, just a note. Anyway, I'm up and running, and will report back! THANK YOU! Glen -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com