http://bugzilla.suse.com/show_bug.cgi?id=976250
http://bugzilla.suse.com/show_bug.cgi?id=976250#c13
Gary Ching-Pang Lin
I didn't find anything wrong in the log :-(
What if you add this line?
bios_override='/usr/share/qemu/ovmf-x86_64.bin'
I installed these latest packages
kernel-default-4.5.4-2.1.gb14d2a1.x86_64 ovmf-2015+git1462940744.321151f-20.1.x86_64 qemu-ovmf-x86_64-2015+git1462940744.321151f-20.1.noarch xen-4.7.0_03-441.1.x86_64 xen-libs-4.7.0_03-441.1.x86_64 xen-tools-4.7.0_03-441.1.x86_64
My packages: kernel-default-4.6.0-1.1.gaf7ce24.x86_64 ovmf-2015+git1462940744.321151f-20.1.x86_64 qemu-ovmf-x86_64-2015+git1462940744.321151f-20.1.noarch qemu-x86-2.5.93-327.8.x86_64 xen-4.7.0_03-442.1.x86_64 xen-libs-4.7.0_03-442.1.x86_64 xen-tools-4.7.0_03-442.1.x86_64 I am using Leap 42.1 + Kernel:Stable + Virtualization
and added to guest.cfg
builder = 'hvm' xen_platform_pci = 1 device_model_version="qemu-xen" device_model_args = ["-debugcon", "file:debug.log", "-global","isa-debugcon.iobase=0x402"] bios = 'ovmf' + bios_override = '/usr/share/qemu/ovmf-x86_64.bin' ...
Here is my config: builder = 'hvm' name = 's0-efi' vcpus = 2 memory = 1024 disk = ['/home/linux/VM/s0-efi.qcow2,qcow2,xvda,w'] on_poweroff="destroy" on_reboot="destroy" on_crash="destroy" sdl=1 serial='pty' bios='ovmf' device_model_args = ["-debugcon", "file:debug.log", "-global", "isa-debugcon.iobase=0x402"]
Now on reboot I **can** boot the Guest and get to it like usual via SSH. I didn't check the Guest thoroughly yet, but its services seem to be running, at least.
But when I check at the Dom0 console, I get "(null)" for Names,
xl list Name ID Mem VCPUs State Time(s) (null) 0 4096 1 r----- 66.6 (null) 1 2049 1 -b---- 18.2
Mine: linux-hjgb:/home/linux # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 2671 4 r----- 1107.0 s0-efi 3 1024 1 ------ 7.4 I don't know why (null) showed in your system but ovmf is unlikely to change the name of Domain0. This might be other problem. The problems I see in your case are: 1. The certificate prompt This is a prompt from shim in openSUSE when SecureBoot is enabled. Xen by default uses "/usr/share/qemu/ovmf-x86_64-ms.bin" which contains the UEFI KEK and CA keys. shim is supposed to ask the user once and saves the answer in a non-volatile variable. Unfortunately, Xen currently doesn't support pflash devices, so the variable couldn't be saved reliably. Maybe we should switch to ovmf-x86_64.bin for openSUSE. You mentioned that the guest didn't boot after choosing yes. Did you only check status with the serial console? or also connect to the guest with VNC? Shim should load grub2 immediately and I'm not aware of any bug in this part. Could you try to boot the guest again with SDL or VNC? 2. d1v0 Over-allocation for domain 1: 524545 > 524544 Did you find the message from the serial console of the host? My test machine doesn't have a serial port. Might need to find a way to get the message. -- You are receiving this mail because: You are on the CC list for the bug.