Pkg xen devel - Jan 2019 - Bug#915063: xen-hypervisor-4.8-amd64: xen 4.8 fails to boot

Package: src:xen
Version: 4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I installed xen hypervisor 4.8 and rebooted to Xen, I am used to xen and run it
on servers
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
try grub kernel xen parameters (iommu )
   * What was the outcome of this action?
blackscreen at gdm3 login session
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (500,
'oldstable'), (11, 'testing'), (10, 'experimental'),
(10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

xen-hypervisor-4.8-amd64 depends on no packages.

Versions of packages xen-hypervisor-4.8-amd64 recommends:
ii  xen-utils-4.8  4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10

xen-hypervisor-4.8-amd64 suggests no packages.

-- debconf-show failed

severity -1 normal
thanks

Hi,

On 11/30/18 12:31 AM, gregory bahde wrote:
> Package: src:xen
> Version: 4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate
***
> 
>    * What led up to the situation?
> I installed xen hypervisor 4.8 and rebooted to Xen, I am used to xen and
run it
> on servers
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> try grub kernel xen parameters (iommu )
Can you tell us a bit more about what you were doing or trying to
accomplish?

Just "I was trying out random command line parameters" and then
reporting a critical bug does not sound very convincing. :)

The "breaks the whole system" justification would be justified if by
using this parameter on the xen command line would have destroyed your
entire computer, the filesystem, whatever, or in any case, caused
irrepairable damage to things that are not related to Xen at all. If
you're able to remove the parameter and then just happily use your
system again as before, then it didn't break your whole system for sure.

Thanks,
Hans
>    * What was the outcome of this action?
> blackscreen at gdm3 login session
>    * What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***
> 
> 
> 
> -- System Information:
> Debian Release: 9.6
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable'),
(500, 'oldstable'), (11, 'testing'), (10,
'experimental'), (10, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/16 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> xen-hypervisor-4.8-amd64 depends on no packages.
> 
> Versions of packages xen-hypervisor-4.8-amd64 recommends:
> ii  xen-utils-4.8  4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10
> 
> xen-hypervisor-4.8-amd64 suggests no packages.
> 
> -- debconf-show failed
> 
> _______________________________________________
> Pkg-xen-devel mailing list
> Pkg-xen-devel at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-xen-devel
>

tags 915063 + moreinfo
thanks

Hi Gregory,

I'm tagging this report moreinfo now, since it clearly needs your
cooperation to advance.

Please let us know if you have addition information on what you were
trying to do, and which exact error messages you encoutered etc...

We might close this bug in the future if there's no response any more.

Thanks,
Hans

Processing commands for control at bugs.debian.org:
> tags 915063 + moreinfo
Bug #915063 [src:xen] xen-hypervisor-4.8-amd64: xen 4.8 fails to boot
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Your message dated Fri, 22 Feb 2019 19:10:48 +0100
with message-id <d83b883b-1670-92b9-9d5e-1009cae510f1 at knorrie.org>
and subject line Re: xen-hypervisor-4.8-amd64: xen 4.8 fails to boot
has caused the Debian Bug report #915063,
regarding xen-hypervisor-4.8-amd64: xen 4.8 fails to 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.)


-- 
915063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915063
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: gregory bahde <gregory.bahde at laposte.net>
Subject: xen-hypervisor-4.8-amd64: xen 4.8 fails to boot
Date: Fri, 30 Nov 2018 00:31:19 +0100
Size: 2878
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190222/4d9dcb4a/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Hans van Kranenburg <hans at knorrie.org>
Subject: Re: xen-hypervisor-4.8-amd64: xen 4.8 fails to boot
Date: Fri, 22 Feb 2019 19:10:48 +0100
Size: 7454
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190222/4d9dcb4a/attachment-0001.mht>