thr3ads.net - Pkg xen devel - [Pkg-xen-devel] Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot [Jul 2017]

If this information is useful, please help other people find it:
Share via:

Bill MacAllister

2017-Jul-02 22:37 UTC

[Pkg-xen-devel] Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

Package: xen-system-amd64
Version: 4.8.1-1+deb9u1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

     Initially an attempt was made to upgrade an existing Jessie
     Xen 4.4 system to Stretch Xen 4.8.  When that failed I decided
     to start with a fresh Stretch install.
     
   * What exactly did you do (or not do) that was effective (or
     ineffective)?

     - First, I just replaced 'jessie' with 'stretch' in
sources.list
       and ran 'apt-get dist-upgrade'.  The resulting system crashed
       on boot.
     - Second, I installed a new stretch system, updated my puppet
       manifest to support Xen 4.8, ran puppet, and rebooted.  The
       resulting system crashed on boot exactly the same as my first
       attempt.
     - Third, I installed a new stretch system and installed only the
       xen-system-amd64 package.  The resulting system crashed on boot
       exactly the same as my first attempt.
       
   * What was the outcome of this action?

     Here is the output captured from a serial console connection.

[    0.000000] Linux version 4.9.0-3-amd64 (debian-kernel at lists.debian.org)
(gc)
[    0.000000] Command line: placeholder root=UUID=54dcd810-baaf-4dfd-9442-4a728
[    0.000000] x86/fpu: Legacy x87 FPU detected.
[    0.000000] x86/fpu: Using 'eager' FPU context switches.
[    0.000000] Released 0 page(s)
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] Xen: [mem 0x0000000000000000-0x000000000009dfff] usable
[    0.000000] Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[    0.000000] Xen: [mem 0x0000000000100000-0x00000000cf378fff] usable
[    0.000000] Xen: [mem 0x00000000cf379000-0x00000000cf38efff] reserved
[    0.000000] Xen: [mem 0x00000000cf38f000-0x00000000cf3cdfff] ACPI data
[    0.000000] Xen: [mem 0x00000000cf3ce000-0x00000000cfffffff] reserved
[    0.000000] Xen: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[    0.000000] Xen: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
[    0.000000] Xen: [mem 0x0000000100000000-0x000000062fffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 2.6 present.
[    0.000000] Hypervisor detected: Xen
[    0.000000] e820: last_pfn = 0x630000 max_arch_pfn = 0x400000000
[    0.000000] MTRR: Disabled
[    0.000000] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[    0.000000] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WC  WP  UC  UC  
[    0.000000] e820: last_pfn = 0xcf379 max_arch_pfn = 0x400000000
[    0.000000] RAMDISK: [mem 0x02000000-0x0325ffff]
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] ACPI: RSDP 0x00000000000F1150 000024 (v02 DELL  )
[    0.000000] ACPI: XSDT 0x00000000000F1254 00009C (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: FACP 0x00000000CF3B3F9C 0000F4 (v03 DELL   PE_SC3   000000)
[    0.000000] ACPI: DSDT 0x00000000CF38F000 003DD0 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: FACS 0x00000000CF3B6000 000040
[    0.000000] ACPI: FACS 0x00000000CF3B6000 000040
[    0.000000] ACPI: APIC 0x00000000CF3B3478 00015E (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: SPCR 0x00000000CF3B35D8 000050 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: HPET 0x00000000CF3B362C 000038 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: RMAD 0x00000000CF3B3668 000198 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: MCFG 0x00000000CF3B38C4 00003C (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: WD__ 0x00000000CF3B3904 000134 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: SLIC 0x00000000CF3B3A3C 000176 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: ERST 0x00000000CF392F70 000270 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: HEST 0x00000000CF3931E0 0003A8 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: BERT 0x00000000CF392DD0 000030 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: EINJ 0x00000000CF392E00 000170 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: SRAT 0x00000000CF3B3BC0 000370 (v01 DELL   PE_SC3   000000)
[    0.000000] ACPI: TCPA 0x00000000CF3B3F34 000064 (v02 DELL   PE_SC3   000000)
[    0.000000] ACPI: SSDT 0x00000000CF3B7000 0043F4 (v01 INTEL  PPM RCM  800000)
[    0.000000] Setting APIC routing to Xen PV.
[    0.000000] NUMA turned off
[    0.000000] Faking a node at [mem 0x0000000000000000-0x000000062fffffff]
[    0.000000] NODE_DATA(0) allocated [mem 0x5e6228000-0x5e622cfff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.000000]   Normal   [mem 0x0000000100000000-0x000000062fffffff]
[    0.000000]   Device   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009dfff]
[    0.000000]   node   0: [mem 0x0000000000100000-0x00000000cf378fff]
[    0.000000]   node   0: [mem 0x0000000100000000-0x000000062fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000062fffffff]
[    0.000000] p2m virtual area at ffffc90000000000, size is 40000000
[    0.000000] Remapped 199913 page(s)
[    0.000000] ACPI: PM-Timer IO Port: 0x808
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
[    0.000000] IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000
[    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
[    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[    0.000000] PM: Registered nosave memory: [mem 0xcf379000-0xcf38efff]
[    0.000000] PM: Registered nosave memory: [mem 0xcf38f000-0xcf3cdfff]
[    0.000000] PM: Registered nosave memory: [mem 0xcf3ce000-0xcfffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xd0000000-0xdfffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xe0000000-0xefffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xf0000000-0xfdffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfe000000-0xffffffff]
[    0.000000] e820: [mem 0xd0000000-0xdfffffff] available for PCI devices
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 4.8.1 (preserve-AD)
[    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xfffs
[    0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:16 nr_n1
[    0.000000] percpu: Embedded 35 pages/cpu @ffff880616a00000 s103512 r8192 d34
[    0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pa5
[    0.000000] Policy zone: Normal
[    0.000000] Kernel command line: placeholder root=UUID=54dcd810-baaf-4dfd-948
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] software IO TLB [mem 0x612a00000-0x616a00000] (64MB) mapped at []
[    0.000000] Memory: 24146744K/25152600K available (6187K kernel code, 1137K )
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000]  RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=16.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=16
[    0.000000] Using NULL legacy PIC
[    0.000000] NR_IRQS:33024 nr_irqs:1096 0
[    0.000000] xen:events: Using FIFO-based ABI
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    0.000000] console [ttyS0] enabled
[    0.000000] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4s
[    0.000000] installing Xen timer for CPU 0
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 2393.841 MHz processor
[   14.535998] Calibrating delay loop (skipped), value calculated using timer f)
[   14.663009] pid_max: default: 32768 minimum: 301
[   14.718218] ACPI: Core revision 20160831
[   14.770224] ACPI: 2 ACPI AML tables successfully acquired and loaded
[   14.846542] Security Framework initialized
[   14.895489] Yama: disabled by default; enable with sysctl kernel.yama.*
[   14.974603] AppArmor: AppArmor disabled by boot time parameter
[   15.047887] Dentry cache hash table entries: 4194304 (order: 13, 33554432 by)
[   15.144904] Inode-cache hash table entries: 2097152 (order: 12, 16777216 byt)
[   15.235894] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
[   15.318212] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 byt)
[   15.406263] CPU: Physical Processor ID: 1
[   15.454170] CPU: Processor Core ID: 0
[   15.497911] mce: CPU supports 2 MCE banks
[   15.545833] Last level iTLB entries: 4KB 512, 2MB 7, 4MB 7
[   15.611415] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
[   15.686661] Freeing SMP alternatives memory: 24K (ffffffff81e7a000 - fffffff)
[   15.783278] ftrace: allocating 25178 entries in 99 pages
[   15.857576] cpu 0 spinlock event irq 57
[   15.903411] smpboot: Max logical packages: 1
[   15.954433] smpboot: CPU 0 Converting physical 1 to logical package 0
[   16.031463] VPMU disabled by hypervisor.
[   16.078349] Performance Events: Westmere events, PMU not available due to vi.
[   16.206235] NMI watchdog: disabled (cpu0): hardware events not enabled
[   16.284305] NMI watchdog: Shutting down hard lockup detector on all cpus
[   16.364621] installing Xen timer for CPU 1
[   16.414578] cpu 1 spinlock event irq 69
[   16.460644] installing Xen timer for CPU 2
[   16.510187] cpu 2 spinlock event irq 76
[   16.556171] installing Xen timer for CPU 3
[   16.605928] cpu 3 spinlock event irq 83
[   16.651997] installing Xen timer for CPU 4
[   16.701895] cpu 4 spinlock event irq 90
[   16.747956] installing Xen timer for CPU 5
[   16.797827] cpu 5 spinlock event irq 97
[   16.843852] installing Xen timer for CPU 6
[   16.893749] cpu 6 spinlock event irq 104
[   16.940860] installing Xen timer for CPU 7
[   16.990761] cpu 7 spinlock event irq 111
[   17.037855] installing Xen timer for CPU 8
[   17.086802] random: fast init done
[   17.128477] smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
[   17.204417] ------------[ cut here ]------------
[   17.259544] kernel BUG at /build/linux-9uDFZV/linux-4.9.30/arch/x86/kernel/c!
[   17.360431] invalid opcode: 0000 [#1] SMP
[   17.408284] Modules linked in:
[   17.444705] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 4.9.0-3-amd64 #1 Debia2
[   17.546637] Hardware name: Dell Inc. PowerEdge R610/0XDN97, BIOS 6.4.0 07/233
[   17.636089] task: ffff88060f35e280 task.stack: ffffc900431bc000
[   17.706821] RIP: e030:[<ffffffff81037bfd>]  [<ffffffff81037bfd>]
identify_se0
[   17.812922] RSP: e02b:ffffc900431bff30  EFLAGS: 00010086
[   17.876374] RAX: 00000000ffffffe4 RBX: ffff880616c0a100 RCX: ffffffff81c48888
[   17.961667] RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000005
[   18.046960] RBP: 0000000000000008 R08: 0000000000000008 R09: 0000000000000005
[   18.132254] R10: ffffc900431bfdf4 R11: ffffffff81eac4ad R12: 0000000000000000
[   18.217544] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[   18.302833] FS:  0000000000000000(0000) GS:ffff880616c00000(0000) knlGS:00000
[   18.399564] CS:  e033 DS: 002b ES: 002b CR0: 0000000080050033
[   18.468211] CR2: 0000000000000000 CR3: 0000000001c07000 CR4: 0000000000002660
[   18.553497] Stack:
[   18.577427]  0000000000000008 0000000000000000 ffffffff81022ae1 0000000000000
[   18.665868]  ffffffff81022b4c 0000000000000000 0000000000000000 0000000000000
[   18.754307]  0000000000000000 0000000000000000 0000000000000000 0000000000000
[   18.842742] Call Trace:
[   18.871877]  [<ffffffff81022ae1>] ? cpu_bringup+0x31/0x80
[   18.936366]  [<ffffffff81022b4c>] ? cpu_bringup_and_idle+0x1c/0x40
[   19.010213] Code: 12 26 fd 7e 89 ef ff 50 68 0f b7 93 d2 00 00 00 39 d0 75 1 
[   19.236405] RIP  [<ffffffff81037bfd>] identify_secondary_cpu+0x4d/0x70
[   19.314419]  RSP <ffffc900431bff30>
[   19.356040] ---[ end trace 52b2fae2ee0ce5e0 ]---
[   19.411172] Kernel panic - not syncing: Attempted to kill the idle task!

     
   * What outcome did you expect instead?

     A bootable system.



-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xen-system-amd64 depends on:
pn  xen-hypervisor-4.8-amd64  <none>
pn  xen-utils-4.8             <none>

xen-system-amd64 recommends no packages.

xen-system-amd64 suggests no packages.

Bastian Blank

2017-Jul-03 14:34 UTC

head link

[Pkg-xen-devel] Bug#866952: Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

Control: severity -1 important

On Sun, Jul 02, 2017 at 03:37:40PM -0700, Bill MacAllister
wrote:> Package: xen-system-amd64
> Version: 4.8.1-1+deb9u1
> Severity: critical
> Justification: breaks the whole system
This is incorrect, it only breaks itself.
> [   17.037855] installing Xen timer for CPU 8
> [   17.086802] random: fast init done
> [   17.128477] smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
Please try upgrading your firmware first.  It seems to provide incorrect
data.

Bastian

-- 
... bacteriological warfare ... hard to believe we were once foolish
enough to play around with that.
		-- McCoy, "The Omega Glory", stardate unknown

Debian Bug Tracking System

2017-Jul-03 14:36 UTC

head link

[Pkg-xen-devel] Processed: Re: Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

Processing control commands:
> severity -1 importantBug #866952 [xen-system-amd64] xen-system-amd64: Xen 4.8 Install on Stretch
Crashes on Boot
Severity set to 'important' from 'critical'

-- 
866952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866952
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems

Bill MacAllister

2017-Jul-04 06:28 UTC

head link

[Pkg-xen-devel] Bug#866952: Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

Thanks very much for you quick response.

On Monday, July 3, 2017 7:34:30 AM PDT, Bastian Blank
wrote:> Control: severity -1 important
>
> On Sun, Jul 02, 2017 at 03:37:40PM -0700, Bill MacAllister wrote:
>> Package: xen-system-amd64
>> Version: 4.8.1-1+deb9u1
>> Severity: critical
>> Justification: breaks the whole system
>
> This is incorrect, it only breaks itself.
This made me smile. I would argue that the system is not up long enough 
for us to know what is working and what is broken. You are certainly 
right Xen definitely is broken.
>> [   17.037855] installing Xen timer for CPU 8
>> [   17.086802] random: fast init done
>> [   17.128477] smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
>
> Please try upgrading your firmware first.  It seems to provide incorrect
> data.
I should have thought of this, thanks for the pointer. I have downloaded 
the latest from Dell and applied it. Unfortunately it did not move the
problem.

What do you think I should try next?

Bill
> Bastian

Berillions

2017-Sep-13 20:20 UTC

head link

[Pkg-xen-devel] Bug#866952: Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

Hi Bill,

Do you still have your crash at boot ?
Because i had the same problem than you with my Desktop (Ryzen Rx1700 + AMD
Rx560) and the solution that i found is to add this option in the Xen Grub
command line :
iommu=dom0-passthrough.

With it, my Dom0 boot correctly.

Cheers,
Maxime
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20170913/f491bde7/attachment.html>

Radoslav Bodó

2017-Sep-15 19:09 UTC

head link

[Pkg-xen-devel] Bug#866952: Workaround: limit cpu's of dom0

I'm facing the same issue on Dell R510 with up to date firmware.
Workaround posted by Joachim Braun <joachim.braun at sysoft.de>'s
worked
> dom0_max_vcpus=4 dom0_vcpus_pin
Best regards
bodik

Hans van Kranenburg

2019-Jan-23 20:31 UTC

head link

[Pkg-xen-devel] Bug#866952: Xen 4.8 crashes...

tags 866952 + moreinfo
thanks

Hi Bill, Thomas, Joachim, Maxime and Radoslav,

I'm hunting down old bug reports in the Xen packages, and also ran into
this one:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866952

The bug report is a collection of seemingly similar problems with a
bunch of proposed solutions, but the end result is a pile of things that
can't really be acted on.

I suggest to close it, and will do so soon, unless there's someone who
still has a clear reproducable problem. But, even in that case I'd
recommend starting a new separate one.

Thanks,
Hans

Debian Bug Tracking System

2019-Jan-23 20:33 UTC

head link

[Pkg-xen-devel] Processed: Re: Xen 4.8 crashes...

Processing commands for control at bugs.debian.org:
> tags 866952 + moreinfoBug #866952 [xen-system-amd64] xen-system-amd64: Xen 4.8 Install on Stretch
Crashes on Boot
Added tag(s) moreinfo.> thanksStopping processing here.

Please contact me if you need assistance.
-- 
866952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866952
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems

Thomas Stegbauer

2019-Jan-23 21:36 UTC

head link

[Pkg-xen-devel] Bug#866952: Xen 4.8 crashes...

Hi Hans, 

thank you for the response. 
As the server at this time was already end of support, we switched to VMware
ESXi free

regards 
Thomas 

-- 
Firma Stegbauer datawork GmbH & Co. KG 
Oberjulbachring 9 
84387 Julbach 

Tel.: +49 (8571) 9251222 
E-Mail: thomas.stegbauer at stegbauer.info 
Internet: www.stegbauer.info 

Unternehmenssitz: Julbach 
Handelsregister beim Amtsgericht: Landshut 
Handelsregister-Nummer: HRA 10671 

Persönlich haftende Gesellschafterin: 
Firma Stegbauer datawork Verwaltungs GmbH - Sitz: Julbach 
Handelsregister beim Amtsgericht: Landshut 
Handelsregisternummer: HRB 9147 
Geschäftsführer: Thomas Stegbauer 
> Von: "Hans van Kranenburg" <hans at knorrie.org>
> An: "866952" <866952 at bugs.debian.org>, "bill"
<bill at ca-zephyr.org>, "Thomas
> Stegbauer" <thomas.stegbauer at stegbauer.info>, "Joachim
Braun"
> <joachim.braun at sysoft.de>, "Berillions" <berillions
at gmail.com>, "Radoslav Bodó"
> <bodik at cesnet.cz>
> Gesendet: Mittwoch, 23. Januar 2019 21:31:10
> Betreff: Re: Xen 4.8 crashes...
> tags 866952 + moreinfo
> thanks
> Hi Bill, Thomas, Joachim, Maxime and Radoslav,
> I'm hunting down old bug reports in the Xen packages, and also ran into
> this one:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866952
> The bug report is a collection of seemingly similar problems with a
> bunch of proposed solutions, but the end result is a pile of things that
> can't really be acted on.
> I suggest to close it, and will do so soon, unless there's someone who
> still has a clear reproducable problem. But, even in that case I'd
> recommend starting a new separate one.
> Thanks,
> Hans-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190123/36f5484b/attachment.html>

Radoslav Bodó

2019-Jan-23 22:09 UTC

head link

[Pkg-xen-devel] Bug#866952: Xen 4.8 crashes...

thanks for your concern.

Currently I'm fine with the workaround I've right now. Debian Buster
(and new xen version) will be released sometimes this year, so I would
reopen a new bug if the problem persist on the server after upgrade ...

Thank you and best regards
bodik

Dne 01/23/2019 v 09:31 PM Hans van Kranenburg napsal(a):> tags 866952 + moreinfo
> thanks
> 
> Hi Bill, Thomas, Joachim, Maxime and Radoslav,
> 
> I'm hunting down old bug reports in the Xen packages, and also ran into
> this one:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866952
> 
> The bug report is a collection of seemingly similar problems with a
> bunch of proposed solutions, but the end result is a pile of things that
> can't really be acted on.
> 
> I suggest to close it, and will do so soon, unless there's someone who
> still has a clear reproducable problem. But, even in that case I'd
> recommend starting a new separate one.

Debian Bug Tracking System

2019-Feb-22 15:30 UTC

head link

[Pkg-xen-devel] Bug#866952: marked as done (xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot)

Your message dated Fri, 22 Feb 2019 16:26:06 +0100
with message-id <2bd79c38-b2ee-2f70-0cd4-fdd60b662cae at knorrie.org>
and subject line Re: Xen 4.8 crashes...
has caused the Debian Bug report #866952,
regarding xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
866952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866952
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Bill MacAllister <bill at ca-zephyr.org>
Subject: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot
Date: Sun, 02 Jul 2017 15:37:40 -0700
Size: 14962
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190222/55b8bb11/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Hans van Kranenburg <hans at knorrie.org>
Subject: Re: Xen 4.8 crashes...
Date: Fri, 22 Feb 2019 16:26:06 +0100
Size: 7827
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190222/55b8bb11/attachment-0001.mht>

Pkg xen devel - Jul 2017 - Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

[Pkg-xen-devel] Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

[Pkg-xen-devel] Bug#866952: Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

[Pkg-xen-devel] Processed: Re: Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

[Pkg-xen-devel] Bug#866952: Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

[Pkg-xen-devel] Bug#866952: Bug#866952: xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot

[Pkg-xen-devel] Bug#866952: Workaround: limit cpu's of dom0

[Pkg-xen-devel] Bug#866952: Xen 4.8 crashes...

[Pkg-xen-devel] Processed: Re: Xen 4.8 crashes...

[Pkg-xen-devel] Bug#866952: Xen 4.8 crashes...

[Pkg-xen-devel] Bug#866952: Xen 4.8 crashes...

[Pkg-xen-devel] Bug#866952: marked as done (xen-system-amd64: Xen 4.8 Install on Stretch Crashes on Boot)