Virtual Manager hangs booting artful iso

Bug #1714638 reported by Kev Bowring on 2017-09-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Undecided
Unassigned

Bug Description

If I boot iso or an installed virt machine using virtual manager it hangs mid-boot.

kvm -m 2048 -cdrom /mnt/Data/iso/Xubuntu/17.10/artful-desktop-amd64.iso from a terminal works fine.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: virt-manager 1:1.4.0-5ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Sep 2 08:20:39 2017
PackageArchitecture: all
SourcePackage: virt-manager
UpgradeStatus: No upgrade log present (probably fresh install)

Kev Bowring (flocculant) wrote :

Hi Kev,
can you report:
- The generated XML of the guest you created with virt-manager
  $ virsh dumpxml <guestname>
- The qemu commandline that is issues, you'll find that at the end of
  /var/log/libvirt/qemu/<guestname>.log

I fetched the current image and ran just the same.
Qemu cmdline is:

/usr/bin/kvm-spice -name guest=ubuntu17.04,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-ubuntu17.04/master-key.aes -machine pc-i440fx-artful,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Broadwell-noTSX -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid fcd72ce9-7ca3-41d8-9ea1-d016310f71e5 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-ubuntu17.04/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-reboot -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/var/lib/libvirt/images/ubuntu17.04.qcow2,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/home/ubuntu/artful-desktop-amd64.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5b:1e:e9,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on

For now confirming the issue.

On the "trivial" working case the console is "less graphical" and it boots through the splash screen.

On the guest as created by virt-manager it initialized a bigger, smother but also hanging console for the guest that hands on the splash screen.
So it loads the initial bits form the ISO, you select language, but then after selecting "install ubuntu" the load hangs on the splash screen.

Adding the cd permanently as:
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/ubuntu/artful-desktop-amd64.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>

Changed in virt-manager (Ubuntu):
status: New → Confirmed

Virsh adds video as default like:
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
    </video>

Matched the cmdline: -device qxl-vga

The default of libvirt is:
    <video>
      <model type='cirrus' vram='16384' heads='1' primary='yes'/>
    </video>

Matches the cmdline: -device cirrus-vga,id=video0

Switching back to the default cirros graphics console makes it working again.

Also type='vga' which matched qemu-cmdline "std" works.
So both qemu defaults (cirrus = old, vga = new), and the libvirt default (cirrus) work.
But the qxl as selected by virt-manager fails.

Get me right - in terms of graphical console both are working fine, but the guest hangs itself up with one, but not the other two.

There is no qemu hang, dump and so on associated.

Furthermore it only seems to be the boot splash that hangs, changing "splash" on the install prompt to "nosplash" makes it perfectly working.

All that I could find afterwards in the UI is good, so I don't think it is so much a bug in virt-manager (or the rest of the virt stack) - if it is switching away from qxl as a default would be a workaround, but for many cases that is preferred.

Instead atm I'd think this is something on the splash screen that breaks/hangs with that graphics driver.

I also checked e.g. Xenial ISO and there it worked which makes this even more an artful-splash-screen issue than of the virt stack.

After I knew what I learned from debugging so far I found bug 1711358 - so this here is actually a dup.

Changed in virt-manager (Ubuntu):
status: Confirmed → Invalid
Kev Bowring (flocculant) wrote :

@ paelzer - thanks for looking and finding the dupe

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers