syslinux menu is displayed when a desktop ISO is powered from virt-manager and SPICE enabled.

[Jean-Baptiste Lallement]

If a desktop ISO is booted from virt-manager it displays the syslinux menu (text menu that a user gets when a key is pressed on boot)
The menu is not displayed when the image is booted from a command line with virsh start.

I expect the behaviour to be the same than booting on hardware, the syslinux should not be displayed and the ISO boots to ubiquity-dm (Ubiquity dialog showing the options try or install Ubuntu)

This is always reproducible on the same machine with ISOs of different flavours, but not all the physical machines running the same version of libvirt and qemu exhibit this behaviour.

Switching to VNC or booting directly from virt-manager without the UI works around this issue.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: virt-manager 1:1.5.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 5 15:03:40 2018
InstallationDate: Installed on 2014-07-15 (1360 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
PackageArchitecture: all
SourcePackage: virt-manager
UpgradeStatus: Upgraded to bionic on 2018-03-24 (11 days ago)

[Christian Ehrhardt  (paelzer)]

We discussed on IRC, but I have to admit I'm unsure what to do on this.
Especially since different hosts with same SW levels are exposing different behavior.

Closing with a quote from IRC
[15:20] <jibel> but really don't spend time on this, I can use the command line

Thanks for the discussion still, lets mark it incomplete (for why it affects only some hosts) and low (as you are ok with it for now).

[Launchpad Janitor (janitor)]

[Expired for virt-manager (Ubuntu) because there has been no activity for 60 days.]

[Jean-Baptiste Lallement (jibel)]

Switching from spice to VNC works around the issue.

[Jean-Baptiste Lallement (jibel)]

I tried spicy from the package spice-client-gtk and doesn't have this problem. So this issue is only with the spice client in libvirt.

[Christian Ehrhardt  (paelzer)]

Common misunderstanding :-)
s/with the spice client in libvirt/with the spice client in virt-manager/
Which are different sources/projects.

But other than that interesting - thanks Jibel for trying alternative spice clients!