Your message dated Wed, 6 Feb 2019 20:36:04 +0100
with message-id <[email protected]>
and subject line Re: Xen stuck at boot "device-mapper: ioctl: …"
has caused the Debian Bug report #912592,
regarding Xen stuck at boot "device-mapper: ioctl: …"
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 [email protected]
immediately.)
--
912592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912592
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xen-hypervisor
Version: 4.8-amd64
Severity: Critical
Since, at least, linux-image-4.16.0-2-amd64, Debian Sid stuck at boot.
With older kernels, it just works.
Before getting cryptsetup prompt, we get a blank screen.
If we remove "quiet" from grub, we can see that Debian stuck after
discovering usb devices, and seems just before loading cryptsetup prompt.
The last lines look like something like this (I am not sure):
/ device-mapper: uevent: version …/
/ device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised:
[email protected]/
Here some packages related
//
Package: xen-utils-4.11
Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-5 amd64
Package: xen-utils-4.8
Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 amd64
Package: dmsetup
version: 2:1.02.145-4.1 amd64
Package: cryptsetup-*
version: 2:2.0.5-1
--- End Message ---
--- Begin Message ---
On 2/6/19 8:41 AM, zer0 divide wrote:
> Hi,
>
> I am using Devuan since…
Ok, thanks for your feedback!
Closing now.
> On 1/20/19 6:49 PM, Hans van Kranenburg wrote:
>> severity 912592 normal
>> tags 912592 + moreinfo
>> thanks
>>
>> Hi zer0 divide,
>>
>> Thanks for your report.
>>
>> I have never used the combination of Xen dom0 and cryptsetup myself.
>>
>> Did you already find out what the cause of this issue is? It sounds a
>> bit like a problem with your initramfs. Or, can you explain why you
>> think the problem is caused by a defect in Xen?
>>
>> If not, can you show more debug logging?
>>
>> Good luck,
>> Hans van Kranenburg
>>
--- End Message ---
