Devuan bug report logs - #343
xen: Fails to boot Xen by default

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Elliott Mitchell <ehem+devuan@m5p.com>
Subject: bug#343: marked as done (xen: Fails to boot Xen by default)
Message-ID: <handler.343.D343.16074810032647.ackdone@bugs.devuan.org>
References: <X9A1/hQ/s7/jQ8dF@mattapan.m5p.com>
 <20190729203636.GA33621@mattapan.m5p.com>
X-Devuan-PR-Message: closed 343
X-Devuan-PR-Package: xen-hypervisor-4.8-amd64
Reply-To: 343@bugs.devuan.org
Date: Wed, 09 Dec 2020 02:33:01 +0000
Content-Type: multipart/mixed; boundary="----------=_1607481181-2670-0"

[Message part 1 (text/plain, inline)]

Your message dated Tue, 8 Dec 2020 18:27:10 -0800
with message-id <X9A1/hQ/s7/jQ8dF@mattapan.m5p.com>
and subject line #343 Fixed with Xen 4.11 packages
has caused the Devuan bug report #343,
regarding xen: Fails to boot Xen by default
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@bugs.devuan.org
immediately.)


-- 
343: https://bugs.devuan.org/cgi/bugreport.cgi?bug=343
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Elliott Mitchell <ehem+devuan@m5p.com>

To: submit@bugs.devuan.org

Subject: xen: Fails to boot Xen by default

Date: Mon, 29 Jul 2019 13:36:36 -0700

Package: xen-hypervisor-4.8-amd64
Version: 4.8.5+shim4.10.2+xsa282-1+deb9u11

The 4.8 version of the Xen package has
'GRUB_DEFAULT="Debian GNU/Linux, with Xen hypervisor"' at the bottom of
/etc/default/grub.d/xen.cfg.  Unfortunately this fails since Devuan is a
distinct distribution and the match fails.

I think the older solution recommended for Wheezy and Squeeze
(https://wiki.debian.org/Xen#Prioritize_booting_Xen_over_native_Linux) of
adding a symbolic link to /etc/grub.d functions better as it doesn't rely
on an exact string match.  That would require coordination with Debian to
rework handling of /etc/grub.d (make a 10_default script which is
meant to be overridden by packages and rename 10_linux to 11_linux).


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

[Message part 3 (message/rfc822, inline)]

From: Elliott Mitchell <ehem+devuan@m5p.com>

To: 343-close@bugs.devuan.org

Subject: #343 Fixed with Xen 4.11 packages

Date: Tue, 8 Dec 2020 18:27:10 -0800

Somewhere during the work between 4.8 and 4.11, this bug was fixed.
Originally the file attempting to control the behavior was in
xen-hypervisor-<version>-<arch>, but the 4.11 packages moved it to
xen-hypervisor-common (/etc/default/grub.d/xen.cfg).

I'm guessing this also caused problems for Ubuntu and pretty well all
other Debian derivatives.  I still find I prefer using dpkg-divert to
rearrange /etc/grub.d more suited to me.

This issue though is without any doubt, fixed.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Send a report that this bug log contains spam.