So I'm not really sure if it's a bug with OVMF or with the VM, but I have a
Leap VM that doesn't boot anymore (on my Tumbleweed host). Unfortunately, I had
updates both on the host (Tumbleweed) and on the guest (Leap).
What I'm seeing is the TianoCore boot splash, then black screen, then just a
cursor that is not even blinking.
I'm really not sure how to debug this further to identify the culprit :/
This is what I see in the libvirt log for this VM:
2016-04-01 13:03:24.631+0000: starting up libvirt version: 1.3.2, qemu version:
2.4.0, hostname: saint-ismier.site
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name SUSE-Tools-Leap -S -machine
pc-i440fx-2.4,accel=kvm,usb=off,vmport=off -cpu IvyBridge -drive
file=/usr/share/qemu/ovmf-x86_64-code.bin,if=pflash,format=raw,unit=0,readonly=on
-drive
file=/var/lib/libvirt/qemu/nvram/SUSE-Tools-Leap_VARS.fd,if=pflash,format=raw,unit=1
-m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
65a5399f-110d-406c-9977-e686e1110152 -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-SUSE-Tools-Leap/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew
-global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -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=0x6.0x7 -device
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive
file=/home/vuntz/work/VMs/images/SUSE-Tools-Leap.qcow2,format=qcow2,if=none,id=drive-ide0-0-0
-device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2
-drive
file=/home/vuntz/work/VMs/isos/openSUSE-Tumbleweed-Rescue-CD-x86_64-Current.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on
-device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1,bootindex=1
-netdev tap,fd=25,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:46:bb:a4,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
-spice
port=5901,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
-k fr -device
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,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 -chardev
spicevmc,id=charredir1,name=usbredir -device
usb-redir,chardev=charredir1,id=redir1 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -object
rng-random,id=objrng0,filename=/dev/random -device
virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x8 -msg timestamp=on
(process:13312): GLib-WARNING **: gmem.c:483: custom memory allocation vtable
not supported
char device redirected to /dev/pts/6 (label charserial0)
main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 0.148000 ms, bitrate 23813953488
bps (22710.755814 Mbps)
red_dispatcher_set_cursor_peer:
inputs_connect: inputs channel client create
qemu: terminating on signal 15 from pid 1449
red_channel_client_disconnect_dummy: rcc=0x5630f6eebb80 (channel=0x5630f7623110
type=5 id=0)
snd_channel_put: SndChannel=0x5630f5fa9630 freed
red_channel_client_disconnect_dummy: rcc=0x5630f6e4be90 (channel=0x5630f76252b0
type=6 id=0)
snd_channel_put: SndChannel=0x5630f78fd2f0 freed
2016-04-01 13:03:33.398+0000: shutting down