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

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

Il 29/07/2015 13:04, Wei Liu ha scritto:
> On Wed, Jul 29, 2015 at 12:59:04PM +0200, Fabio Fantoni wrote:
> > Il 29/07/2015 12:44, Wei Liu ha scritto:
> > > On Wed, Jul 29, 2015 at 12:42:41PM +0200, Fabio Fantoni wrote:
> > > > Il 29/07/2015 11:58, Wei Liu ha scritto:
> > > > > On Wed, Jul 29, 2015 at 11:31:30AM +0200, Fabio Fantoni wrote:
> > > > > > Today I retried ovmf after long time from previous, I tried old fedora 20
> > > > > > uefi domUs and still boot correctly but trying to boot from cdrom using
> > > > > > boot='dc' or boot='d' don't boot from cdrom (seems didn't try) but boot from
> > > > > > harddisk (even with boot='d').
> > > > > > After booting fedora I checked the cdrom and see it correctly, the problem
> > > > > > seems only about boot order.
> > > > > > xen is build from staging git based on commit
> > > > > > 44313ab77f3e3c5b566ea4f23b0e32bfd5eafa29 and ovmf is from debian package
> > > > > > 0~20150106.5c2d456b-1.
> > > > > >
> > > > > > If you need more informations/tests tell me and I'll post them.
> > > > > >
> > > > > > Thanks for any reply and sorry for my bad english.
> > > > > OK, the commit you tested contains the fix to booting OVMF.
> > > > >
> > > > > Do you have serial log?
> > > > >
> > > > > Wei.
> > > > You mean ovmf serial log? probably I did it in past but I not remember how
> > > > and with a fast search I not found (probably was some years ago when I
> > > > started to try ovmf and initially with xen domUs was not working at all)
> > > > I found only serial="pty" commented in my tests domUs cfg probably related
> > > > but I don't remember how to see/store the output, can you tell me it please?
> > > I meant Xen serial log. And you probably need to increase your log level
> > > in Xen command line.
> > >
> > > Wei.
> > Sorry for my stupid question, what xen serial log you mean? serial of dom0
> > for debug domU's internal boot seems very strange to me.
> Because firmware (in this case, OVMF) writes something to console as
> guest output.
>
> > this is my actual dom0 grub entry is:
> > > menuentry 'RAID - Debian 7.8 (wheezy) con Linux 3.16.0-0.bpo.4-amd64 e XEN
> > > 4.6-unstable' --class debian --class gnu-linux --class gnu --class os
> > > --class xen {
> > >         set fallback="1"
> > >         set root='(RAID-ROOT)'
> > >         echo    'Caricamento Hypervisor Xen 4.6-unstable...'
> > >         multiboot       /boot/xen.gz placeholder dom0_mem=2G,max:3G
> > >         echo    'Caricamento Linux 3.16.0-0.bpo.4-amd64 ...'
> > >         module  /boot/vmlinuz-3.16.0-0.bpo.4-amd64 placeholder
> > > root=/dev/mapper/RAID-ROOT ro swiotlb=65762 quiet
> > >         echo    'Caricamento ramdisk iniziale...'
> > >         module  /boot/initrd.img-3.16.0-0.bpo.4-amd64
> > > }
> > this is an old entry I used for debug dom0 boot problem:
> > > menuentry 'Wheezy con Linux 3.2.0-4-amd64 e XEN 4.4 - RAID - Debug su
> > > Seriale' --class debian --class gnu-linux --class gnu --class os {
> > >     set root='(RAID-ROOT)'
> > >     echo    'Caricamento Hypervisor Xen 4.4...'
> > >     multiboot    /boot/xen-4.4-amd64.gz placeholder dom0_mem=2G,max:2G
> > > swiotlb=65762 loglvl=all guest_loglvl=all sync_console console_to_ring
> > > com2=19200,8n1 console=com2
> > >     echo    'Caricamento Linux 3.2.0-4-amd64...'
> > >     linux    /boot/vmlinuz-3.2.0-4-amd64 placeholder
> > > root=/dev/mapper/RAID-ROOT ro console=hvc0 earlyprintk=xen nomodeset
> > >     echo    'Caricamento ramdisk iniziale...'
> > >     initrd    /boot/initrd.img-3.2.0-4-amd64
> > > }
> > About dom0 you mean add only "loglvl=all guest_loglvl=all" or also other
> > thing?
> > And about domU?
> I think your configuration is alright.
>
> Actually you can use xl dmesg to get the log. The interesting part is
> hvmloader information.
>
> Wei.
>
> > Thanks for any reply.
Here the xl dmesg about fedora with ovmf:
> (d14) HVM Loader
> (d14) Detected Xen v4.6-unstable
> (d14) Xenbus rings @0xfeffc000, event channel 1
> (d14) System requested OVMF
> (d14) CPU speed is 2660 MHz
> (d14) Relocating guest memory for lowmem MMIO space disabled
> (XEN) irq.c:276: Dom14 PCI link 0 changed 0 -> 5
> (d14) PCI-ISA link 0 routed to IRQ5
> (XEN) irq.c:276: Dom14 PCI link 1 changed 0 -> 10
> (d14) PCI-ISA link 1 routed to IRQ10
> (XEN) irq.c:276: Dom14 PCI link 2 changed 0 -> 11
> (d14) PCI-ISA link 2 routed to IRQ11
> (XEN) irq.c:276: Dom14 PCI link 3 changed 0 -> 5
> (d14) PCI-ISA link 3 routed to IRQ5
> (d14) pci dev 01:3 INTA->IRQ10
> (d14) pci dev 02:0 INTA->IRQ11
> (d14) pci dev 03:0 INTA->IRQ5
> (d14) pci dev 04:0 INTA->IRQ5
> (d14) pci dev 06:0 INTA->IRQ11
> (d14) pci dev 1d:0 INTA->IRQ10
> (d14) pci dev 1d:1 INTB->IRQ11
> (d14) pci dev 1d:2 INTC->IRQ5
> (d14) pci dev 1d:7 INTD->IRQ5
> (d14) No RAM in high memory; setting high_mem resource base to 100000000
> (d14) pci dev 02:0 bar 14 size 001000000: 0f0000008
> (d14) pci dev 05:0 bar 10 size 001000000: 0f1000008
> (d14) pci dev 06:0 bar 30 size 000040000: 0f2000000
> (d14) pci dev 05:0 bar 30 size 000010000: 0f2040000
> (d14) pci dev 03:0 bar 10 size 000004000: 0f2050000
> (d14) pci dev 04:0 bar 14 size 000001000: 0f2054000
> (d14) pci dev 05:0 bar 18 size 000001000: 0f2055000
> (d14) pci dev 1d:7 bar 10 size 000001000: 0f2056000
> (d14) pci dev 02:0 bar 10 size 000000100: 00000c001
> (d14) pci dev 06:0 bar 10 size 000000100: 00000c101
> (d14) pci dev 06:0 bar 14 size 000000100: 0f2057000
> (d14) pci dev 04:0 bar 10 size 000000020: 00000c201
> (d14) pci dev 1d:0 bar 20 size 000000020: 00000c221
> (d14) pci dev 1d:1 bar 20 size 000000020: 00000c241
> (d14) pci dev 1d:2 bar 20 size 000000020: 00000c261
> (d14) pci dev 01:1 bar 20 size 000000010: 00000c281
> (d14) Multiprocessor initialisation:
> (d14)  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... 
> done.
> (d14)  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... 
> done.
> (d14) Testing HVM environment:
> (d14)  - REP INSB across page boundaries ... passed
> (d14)  - GS base MSRs and SWAPGS ... passed
> (d14) Passed 2 of 2 tests
> (d14) Writing SMBIOS tables ...
> (d14) Loading OVMF ...
> (XEN) d14v0 Over-allocation for domain 14: 524545 > 524544
> (XEN) memory.c:155:d14v0 Could not allocate order=0 extent: id=14 
> memflags=0 (0 of 1)
> (d14) Loading ACPI ...
> (d14) S3 disabled
> (d14) S4 disabled
> (d14) vm86 TSS at fc012c80
> (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:
> (d15) Booting from DVD/CD...
> (d15) Device reports MEDIUM NOT PRESENT
> (d15) scsi_is_ready returned -1
> (d15) Boot failed: Could not read from CDROM (code 0003)
> (d15) enter handle_18:
> (d15)   NULL
> (d15) Booting from Hard Disk...
> (d15) Booting from 0000:7c00

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