Re: [Xen-devel] unable to boot from cdrom using OVMF in latest xen-unstable

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Wed, Jul 29, 2015 at 01:15:24PM +0200, Fabio Fantoni wrote:
[...]
> >(d14) BIOS map:
> >(d14)  ffe00000-ffffffff: Main BIOS
> >(d14) E820 table:
> >(d14)  [00]: 00000000:00000000 - 00000000:000a0000: RAM
> >(d14)  HOLE: 00000000:000a0000 - 00000000:000f0000
> >(d14)  [01]: 00000000:000f0000 - 00000000:00100000: RESERVED
> >(d14)  [02]: 00000000:00100000 - 00000000:7eead000: RAM
> >(d14)  HOLE: 00000000:7eead000 - 00000000:fc000000
> >(d14)  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
> >(d14) Invoking OVMF ...
> >(XEN) irq.c:276: Dom14 PCI link 0 changed 5 -> 11
> >(XEN) irq.c:276: Dom14 PCI link 1 changed 10 -> 11
> >(XEN) irq.c:276: Dom14 PCI link 2 changed 11 -> 10
> >(XEN) irq.c:276: Dom14 PCI link 3 changed 5 -> 10
> 
> The strange thing is that I not found lines "Boot from" similar to domUs
> with seabios instead, for example a w10 domU, seabios and boot='dc' and with
> empty cdrom have also these lines:

Right. That's because OVMF doesn't write to the correct port. Sigh.

It requires recompiling OVMF to make it write to serial console, which
is probably too much trouble for you.

Another thing to try is to use VNC to connect to your DomU to see if
there is anything useful there.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel