[Bug 1742286] Re: [regression] Xenial host with 4.4.0-108.131 fails to power some KVM guests

2018-01-10 Thread Ian McMichael
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934

** This bug has been marked a duplicate of bug 1741934
   Kernel trace with xenial 4.4  (4.4.0-108.131, Candidate kernels for PTI fix)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742286

Title:
  [regression] Xenial host with 4.4.0-108.131 fails to power some KVM
  guests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742286] Re: [regression] Xenial host with 4.4.0-108.131 fails to power some KVM guests

2018-01-10 Thread Emilio
I cannot boot system on a desktop computer, not virtual. I need press reset 
buton to resart freeze system.
I've a i5-4460 processor. I've returned to 4.4.0-104 generic kernel to restart 
my computer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742286

Title:
  [regression] Xenial host with 4.4.0-108.131 fails to power some KVM
  guests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742286] Re: [regression] Xenial host with 4.4.0-108.131 fails to power some KVM guests

2018-01-09 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742286

Title:
  [regression] Xenial host with 4.4.0-108.131 fails to power some KVM
  guests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742286] Re: [regression] Xenial host with 4.4.0-108.131 fails to power some KVM guests

2018-01-09 Thread Joseph Salisbury
Can you see if this bug happens with the following kernel:

http://kernel.ubuntu.com/~jsalisbury/lp1741934/

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Xenial)
   Status: New => Confirmed

** Tags added: kernel-key

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742286

Title:
  [regression] Xenial host with 4.4.0-108.131 fails to power some KVM
  guests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742286] Re: [regression] Xenial host with 4.4.0-108.131 fails to power some KVM guests

2018-01-09 Thread Simon Déziel
For what it's worth, a similar setup but using an AMD CPU (C-60) has no
problem with nmi_watchdog=0.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742286

Title:
  [regression] Xenial host with 4.4.0-108.131 fails to power some KVM
  guests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742286] Re: [regression] Xenial host with 4.4.0-108.131 fails to power some KVM guests

2018-01-09 Thread Simon Déziel
After multiple reboots, it turns out that the problematic host's boot
arg is "nmi_watchdog=0".

If I set the host with only those:

sdeziel@xeon:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic 
root=UUID=40a302c9-82d9-4574-ac2f-efcf5c9d126f ro hugepages=3008 kaslr 
possible_cpus=2 transparent_hugepage=never vsyscall=none

All 17 guests boot fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742286

Title:
  [regression] Xenial host with 4.4.0-108.131 fails to power some KVM
  guests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742286] Re: [regression] Xenial host with 4.4.0-108.131 fails to power some KVM guests

2018-01-09 Thread Simon Déziel
xeon is the host/hypervisor and it has the following boot args:

sdeziel@xeon:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic 
root=UUID=40a302c9-82d9-4574-ac2f-efcf5c9d126f ro hugepages=3008 kaslr 
nmi_watchdog=0 possible_cpus=2 transparent_hugepage=never vsyscall=none

The Trusty VM hangs during boot:

sdeziel@xeon:~$ virsh start --console smtp # Trusty VM
Domain smtp started
Connected to domain smtp
Escape character is ^]
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.13.0-137-generic (buildd@lgw01-amd64-058) (gcc 
version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #186-Ubuntu SMP Mon Dec 4 
19:09:19 UTC 2017 (Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39)
[0.00] Command line: root=UUID=4c6c4ccd-99e2-43fa-af96-91bdeb1258aa ro 
console=ttyS0  
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x17fd] usable
[0.00] BIOS-e820: [mem 0x17fe-0x17ff] reserved
[0.00] BIOS-e820: [mem 0xfeffc000-0xfeff] reserved
[0.00] BIOS-e820: [mem 0xfffc-0x] reserved
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.8 present.
[0.00] Hypervisor detected: KVM
[0.00] No AGP bridge found
[0.00] e820: last_pfn = 0x17fe0 max_arch_pfn = 0x4
[0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[0.00] found SMP MP-table at [mem 0x000f6630-0x000f663f] mapped at 
[880f6630]
[0.00] Scanning 1 areas for low memory corruption
[0.00] init_memory_mapping: [mem 0x-0x000f]
[0.00] init_memory_mapping: [mem 0x1780-0x179f]
[0.00] init_memory_mapping: [mem 0x1400-0x177f]
[0.00] init_memory_mapping: [mem 0x0010-0x13ff]
[0.00] init_memory_mapping: [mem 0x17a0-0x17fd]
[0.00] RAMDISK: [mem 0x17a62000-0x17fc]
[0.00] ACPI: RSDP 000f6450 14 (v00 BOCHS )
[0.00] ACPI: RSDT 17fe16fa 34 (v01 BOCHS  BXPCRSDT 0001 
BXPC 0001)
[0.00] ACPI: FACP 17fe0c14 74 (v01 BOCHS  BXPCFACP 0001 
BXPC 0001)
[0.00] ACPI: DSDT 17fe0040 000BD4 (v01 BOCHS  BXPCDSDT 0001 
BXPC 0001)
[0.00] ACPI: FACS 17fe 40
[0.00] ACPI: SSDT 17fe0c88 0009C2 (v01 BOCHS  BXPCSSDT 0001 
BXPC 0001)
[0.00] ACPI: APIC 17fe164a 78 (v01 BOCHS  BXPCAPIC 0001 
BXPC 0001)
[0.00] ACPI: HPET 17fe16c2 38 (v01 BOCHS  BXPCHPET 0001 
BXPC 0001)
[0.00] No NUMA configuration found
[0.00] Faking a node at [mem 0x-0x17fd]
[0.00] Initmem setup node 0 [mem 0x-0x17fd]
[0.00]   NODE_DATA [mem 0x17fdb000-0x17fd]
[0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00
[0.00] kvm-clock: cpu 0, msr 0:17fd7001, boot clock
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x1000-0x00ff]
[0.00]   DMA32[mem 0x0100-0x]
[0.00]   Normal   empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x1000-0x0009efff]
[0.00]   node   0: [mem 0x0010-0x17fd]
[0.00] ACPI: PM-Timer IO Port: 0x608
[0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[0.00] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[0.00] ACPI: IOAPIC (id[0x00] address[0xfec0] gsi_base[0])
[0.00] IOAPIC[0]: apic_id 0, version 17, address 0xfec0, GSI 0-23
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[0.00] Using ACPI (MADT) for SMP configuration information
[0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0
[0.00] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[0.00] PM: Registered nosave memory: [mem 0x0009f000-0x0009]
[0.00] PM: Registered nosave memory: [mem 0x000a-0x000e]
[0.00] PM: Registered nosave memory: [mem