Bug 1705676 - edk2 doesn't always enabled the graphical display on arm/aarch64
Summary: edk2 doesn't always enabled the graphical display on arm/aarch64
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: edk2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paolo Bonzini
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2019-05-02 18:10 UTC by Peter Robinson
Modified: 2019-07-02 19:28 UTC (History)
9 users (show)

(edit)
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)

Description Peter Robinson 2019-05-02 18:10:25 UTC
There doesn't seem to be any regulatly repeatable, sometimes it works and sometimes it doesn't, when run with the same cmd line but sometimes the graphical display isn't enabled by tianocore and you get the following error on the graphical console:

"Guest has not initialised the display (yet)"

It would be useful to have it consistently enabled and usable.

Comment 1 Peter Robinson 2019-05-02 18:11:10 UTC
edk2-aarch64-20190308stable-1.fc29.noarch
edk2-arm-20190308stable-1.fc29.noarch
edk2-ovmf-20190308stable-1.fc29.noarch

Comment 2 Jeremy Linton 2019-07-02 17:16:02 UTC
I must have forgotten to click save when I wrote this a couple weeks ago: Basically I was having problems too until I switched the graphics to pci-virtio graphics+spice+usb keyboard in virt-manager. Using the following qemu command line seems to work consistently with F30 for me:

/usr/bin/qemu-system-aarch64 -name guest=fedora30 -machine virt-3.1,accel=kvm,gic-version=3 -cpu host -m 2048  -smp 1,sockets=1,cores=1,threads=1 
-drive file=/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw,if=pflash,format=raw 
-drive file=/var/lib/libvirt/qemu/nvram/fedora30_VARS.fd,if=pflash,format=raw  
-device qemu-xhci 
-device virtio-gpu-pci 
-drive file=/var/lib/libvirt/images/fedora30.qcow2
-device usb-kbd  
-display gtk


This is with:

[root@mammon-tx2 jlinton]# rpm -qa |grep edk2
edk2-aarch64-20190308stable-1.fc30.noarch
edk2-ovmf-20190308stable-1.fc30.noarch


Maybe the default fedora/aarch64 profile could use the addition of a graphics console?

Comment 3 Jeremy Linton 2019-07-02 17:26:03 UTC
Moved back to a f29 machine, a setup a gicv2 config via virt-manager. That generates a qemu command with `-machine virt-3.0,accel=kvm,usb=off,dump-guest-core=off,gic-version=2 -cpu host` and that seems fine too as does a similar TCG config emulating aarch64 on x86.

Comment 4 Jeremy Linton 2019-07-02 19:28:46 UTC
In the case of OZ this seems to be more a problem with the default ACPI config telling the kernel that the default console is ttyAMA0. Rather if 

<kernelparam>console=tty0</kernelparam>

is placed in the .tdl file, the console is switched back to the graphical head. My tweaks to explicitly ask for a virtio console via libvirt apparently aren't needed (the flashing tianocore logo, blurb about an empty DTB and then a blank screen happen either way).


Note You need to log in before you can comment on or make changes to this bug.