On completion of the install you click on Done then the install is dropped onto a plain black screen.
It will remain on this screen till the enter button is pressed.
Should display press enter to restart and remove install media or something along those lines.
kde neon, current stable on kvm with uefi and spice qxl gfx. I will be trying on actual hardware at the weekend but want to make sure is was mostly functioning before I did.
That is most curious. openqa also uses kvm with uefi and qxl, so it should be seeing the problem as well oO. And so am I for the record.
Can you make a video of the entire installation maybe (from start up to shutdown)? The recording tool vokoscreen works well for me.
Does it work with the ubuntu 18.04 ISO? Do you have the VM on a HDD or SSD? What's your host system?
I can't reproduce this with neon 16.04 base as host system. I even tried with exactly the way you fire up the VM; no dice.
My best guess is that you are seeing a bug in ovmf/spice/qxl. It looks like plymouth doesn't start (in time? could be a timing issue, which would explain why I don't see it and why it also doesn't happen on bare metal), so fallback logic kicks in which would print the prompt on the console instead of plymouth .... why you don't get that displayed either is beyond me though; quick theory is that somehow virt-viewer dropped you onto a console display, even though you didn't specify one so there is no console display to drop you to in theory ^^
This is working as expected on hardware after switching out OVMF.fd for OVMF_CODE.fd OVMF_VAR.fd I'm now seeing a gui screen but still no text (assume for now it is working as expected) I'll dig into more my side after
tested on hardware using neon 18.04 as a host in virt-manager using uefi and everything worked as expected so it might just be the 16.04 version of kvm that is having issues.
HA! Now that you mention it, both I and our openqa setup use a newer OVMF as the old one actually was bugging out with qxl and uefi :)
Although I think the bug we had was it shutting down, but then failing to reinitialize the display on reboot (which ought to be clearly a firmware problem). Anyway, newer OVMF is the way to go indeed.