Your message dated Wed, 24 Jul 2019 11:49:39 +0200
with message-id <20190724094939.euazqbotcww4i...@shell.thinkmo.de>
and subject line Re: Bug#932149: Action taken due to junk email
has caused the Debian Bug report #932149,
regarding Buster install requires more ram than documented
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 ow...@bugs.debian.org
immediately.)
--
932149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Boot method: xl create buster.cfg
Image version: Multiple. Please see below.
Machine: Xen DomU (on HP Proliant Dom0)
Memory: 512M
Partitions: N/A (10G allocated for xvda)
Base System Installation Checklist:
[O] = OK, [E] = Error, [ ] = didn't try it
Initial boot: [E] Kernel boots, d-i fails to launch.
Detect network card: [ ]
Configure network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]
Attempting to install Buster on a freshly created Xen DomU fails early with
the following in the log:
[ 2.698206] Run /init as init process
[ 2.777783] xen_netfront: Initialising Xen virtual ethernet driver
/sbin/reopen-console: line 26: can't create /var/log/reopen-console:
nonexistent directory
/sbin/reopen-console: line 26: can't create /var/log/reopen-console:
nonexistent directory
/sbin/reopen-console: line 26: can't create /var/log/reopen-console:
nonexistent directory
/sbin/reopen-console: line 26: can't create /var/log/reopen-console:
nonexistent directory
/sbin/reopen-console: line 26: can't create /var/log/reopen-console:
nonexistent directory
/sbin/reopen-console: line 69: can't create /var/run/console-devices:
nonexistent directory
/sbin/reopen-console: line 69: can't create /var/run/console-devices:
nonexistent directory
/sbin/reopen-console: line 71: can't create /var/run/console-preferred:
nonexistent directory
/sbin/reopen-console: line 26: can't create /var/log/reopen-console:
nonexistent directory
/sbin/reopen-console: line 26: can't create /var/log/reopen-console:
nonexistent directory
cat: can't open '/var/run/console-preferred': No such file or directory
[ 2.957523] steal-ctty[125]: segfault at 0 ip 00007fbce02c4160 sp
00007ffe4dde3830 error 4 in libc.so.6[7fbce021f000+148000]
[ 2.957551] Code: 8b e8 74 36 04 00 0f 1f 40 00 55 48 89 e5 41 57 41 56 41 55 41
54 53 48 83 ec 48 64 48 8b 04 25 28 00 00 00 48 89 45 c8 31 c0 <80> 3f 00 0f 84
47 01 00 00 49 89 f4 be 2f 00 00 00 48 89 fb 49 89
Segmentation fault
cat: can't open '/var/log/reopen-console': No such file or directory
rm: can't remove '/var/log/reopen-console': No such file or directory
touch: /var/run/brltty-Xorg: No such file or directory
touch: /var/run/brltty-Xorg: No such file or directory
touch: /var/run/brltty-Xorg: No such file or directory
The last error, about brltty-Xorg, seems to be repeated perpetually.
Proceeding with installation is not possible. Pressing Ctrl-C yields no
visible result.
This happens both with the release image from:
http://deb.debian.org/debian/dists/buster/main/installer-amd64/20190702/images/netboot/xen/
and the latest nightly built from:
https://d-i.debian.org/daily-images/amd64/20190715-00:24/netboot/xen/
Providing "-- console=hvc0", "-- console=tty0", "-- console=" and "" as
values for the 'extra' config variable makes no difference. No additional
config options in xl.cfg, apart from pointing out kernel and initial
ramdisk.
To the best of my understanding, this issue is not mentioned in neither the
Release Notes nor the Installation Guide for Buster. The Xen page on
Debian's wiki is also a bit thin on Buster specific details.
For what it's worth Dom0 is running Stretch with Xen 4.8, and has several
fully functional DomU instances also running Stretch.
One might guess #768657 is related in some way, but unfortunately I do not
currently fully understand it. I'm reluctant to post directly to it since it
seems too old (November 2014) to be causing failure only for Buster, but
please feel free to merge this report with it if confident the issue is
caused by the same root cause.
--
/Martin
--- End Message ---
--- Begin Message ---
On Wed, Jul 24, 2019 at 10:40:14AM +0200, Martin Samuelsson wrote:
> As a consequence of recieving spam, I'm suspending this email address.
So, closing.
Bastian
--
Conquest is easy. Control is not.
-- Kirk, "Mirror, Mirror", stardate unknown
--- End Message ---
