Bug 38605 - UCS-4 not installable on Xen
UCS-4 not installable on Xen
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UCS Installer
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-05-26 17:51 CEST by Philipp Hahn
Modified: 2019-01-03 07:15 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016092321000747
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2015-05-26 17:51:43 CEST
1. Booting UCS-4 just displays a colorful screen
2. Using text mode creates a white screen.
3. Using text mode and "xen_emul_unplug=never" get the installer to work.


For debugging:

ucr set grub/quiet=no grub/loglevel=7 grub/bootsplash=nosplash grub/append=xen_emul_unplug=never grub/rootdelay=0
cat >/etc/default/grub <<__EOF__
GRUB_CMDLINE_LINUX="text console=tty0 console=ttyS0,115200,8,N,1 xen_emul_unplug=never"
__EOF__
update-grub

shows

[   31.209083] xenbus_probe_frontend: Timeout connecting to device: device/vfb/0 (local state 3, remote state 1)
[   31.212418] xenbus_probe_frontend: Device with no driver: device/vbd/768
[   31.215886] xenbus_probe_frontend: Device with no driver: device/vbd/832
[   31.219375] xenbus_probe_frontend: Device with no driver: device/vif/0


Seems to be a problem with framebuffer and HVM: <https://github.com/coreos/bugs/issues/208>


VM has 2 frame-buffers and seems to pick the PV (xen) one, while VNC is connected to the simple VGA one:

# fbset -fb /dev/fb0 -i
mode "800x600"
    geometry 800 600 800 600 32
    timings 0 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode
Frame buffer device information:
    Name        : xen
    Address     : 0
    Size        : 2097152
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 0
    YPanStep    : 0
    YWrapStep   : 0
    LineLength  : 3200
    Accelerator : No

# fbset -fb /dev/fb1 -i
mode "800x600"
    geometry 800 600 800 600 24
    timings 0 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode
Frame buffer device information:
    Name        : simple
    Address     : 0xf0000000
    Size        : 1441792
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 0
    YPanStep    : 0
    YWrapStep   : 0
    LineLength  : 2400
    Accelerator : No

# lspci -s 2
00:02.0 VGA compatible controller: Cirrus Logic GD 5446


# cat /dev/urandom >/dev/fb1
successfully fills the VNC console with random data

TODO: Check drivers/video/xen-fbfront.c if it can be disabled run-time "console=tty"... might work.
Comment 1 Philipp Hahn univentionstaff 2015-05-27 08:16:38 CEST
For the *installed* system the "simple framebuffer" matches the VGA card and must be chosen as the primary frame buffer device:

# cat /proc/fb 
0 xen
1 simple
# ucr set grub/append="fbcon=map:1"

There still is the annoying 30s delay because of the missing driver for non-functional device/vfb/0.

The graphical installer still does NOT work: With "fbcon=map:1" the top-left corner is shown, but shifted to the right and scaled up largely.

The text installer also does not work with "fbcon=map:1" alone: The 2nd console works, but the one where the installer is started stays black.

Strangely there is a 3rd FB called "VGA16 VGA", which might be what is used by the Debian Installer.
Comment 2 Stefan Gohmann univentionstaff 2016-10-18 08:31:03 CEST
Once again: Ticket #2016092321000747

> FEEDBACK: Installation in einer XEN-Umgebung funktioniert nur mit Hindernissen 
> "vga=normal".
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:15:56 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.