Re: [Xen-devel] [xen-unstable test] 59040: regressions - FAIL

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Mon, Jul 06, 2015 at 01:57:28PM +0100, Ian Campbell wrote:
> On Mon, 2015-07-06 at 13:47 +0100, Ian Jackson wrote:
> > > >  test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 
> > > > debian-hvm-install fail REGR. vs. 58965
> > > 
> > > http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/xen-unstable.html
> > > 
> > > 2015-07-03 15:39:29 Z executing ssh ... root@xxxxxxxxxxxxx xl list
> > > 2015-07-03 15:39:30 Z guest debianhvm.guest.osstest not present on this 
> > > host
> > > 2015-07-03 15:39:30 Z FAILURE: guest unexpectedly shutdown; state is ''
> > > failure: guest unexpectedly shutdown; state is ''
> > > 
> > > The xl log just says:
> > > 
> > > Waiting for domain debianhvm.guest.osstest (domid 1) to die [pid 4412]
> > > Domain 1 has shut down, reason code 0 0x0
> > > Action for shutdown reason code 0 is destroy
> > > Domain 1 needs to be cleaned up: destroying the domain
> > > Done. Exiting now
> > 
> > This is quite weird.
> 
> I just spotted near the end of
> http://logs.test-lab.xenproject.org/osstest/logs/59040/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/serial-italia1.log
> that the BIOS failed to find a device to boot from, for some reason
> (which is still weird)...
> 
> Jul  3 15:38:29.941066 (d1) HVM Loader
> Jul  3 15:38:29.941085 (d1) Detected Xen v4.6-unstable
> Jul  3 15:38:29.949058 (d1) Xenbus rings @0xfeffc000, event channel 1
> Jul  3 15:38:29.949105 (d1) System requested ROMBIOS
> Jul  3 15:38:29.949145 (d1) CPU speed is 3093 MHz
> Jul  3 15:38:29.957103 (d1) Relocating guest memory for lowmem MMIO space 
> enabled
> Jul  3 15:38:29.957138 (XEN) irq.c:276: Dom1 PCI link 0 changed 0 -> 5
> Jul  3 15:38:29.965066 (d1) PCI-ISA link 0 routed to IRQ5
> Jul  3 15:38:29.965085 (XEN) irq.c:276: Dom1 PCI link 1 changed 0 -> 10
> Jul  3 15:38:29.973094 (d1) PCI-ISA link 1 routed to IRQ10
> Jul  3 15:38:29.973113 (XEN) irq.c:276: Dom1 PCI link 2 changed 0 -> 11
> Jul  3 15:38:29.981088 (d1) PCI-ISA link 2 routed to IRQ11
> Jul  3 15:38:29.981132 (XEN) irq.c:276: Dom1 PCI link 3 changed 0 -> 5
> Jul  3 15:38:29.989050 (d1) PCI-ISA link 3 routed to IRQ5
> Jul  3 15:38:29.989087 (d1) pci dev 01:2 INTD->IRQ5
> Jul  3 15:38:29.989102 (d1) pci dev 01:3 INTA->IRQ10
> Jul  3 15:38:29.997056 (d1) pci dev 03:0 INTA->IRQ5
> Jul  3 15:38:29.997072 (d1) pci dev 04:0 INTA->IRQ5
> Jul  3 15:38:29.997086 (d1) No RAM in high memory; setting high_mem resource 
> base to 100000000
> Jul  3 15:38:30.005050 (d1) pci dev 02:0 bar 10 size 002000000: 0f0000008
> Jul  3 15:38:30.013064 (d1) pci dev 03:0 bar 14 size 001000000: 0f2000008
> Jul  3 15:38:30.013088 (d1) pci dev 02:0 bar 14 size 000001000: 0f3000000
> Jul  3 15:38:30.021068 (d1) pci dev 03:0 bar 10 size 000000100: 00000c001
> Jul  3 15:38:30.029048 (d1) pci dev 04:0 bar 10 size 000000100: 00000c101
> Jul  3 15:38:30.029068 (d1) pci dev 04:0 bar 14 size 000000100: 0f3001000
> Jul  3 15:38:30.037043 (d1) pci dev 01:2 bar 20 size 000000020: 00000c201
> Jul  3 15:38:30.037076 (d1) pci dev 01:1 bar 20 size 000000010: 00000c221
> Jul  3 15:38:30.045054 (d1) Multiprocessor initialisation:
> Jul  3 15:38:30.045093 (d1)  - CPU0 ... 36-bit phys ... fixed MTRRs ... var 
> MTRRs [1/8] ... done.
> Jul  3 15:38:30.053063 (d1)  - CPU1 ... 36-bit phys ... fixed MTRRs ... var 
> MTRRs [1/8] ... done.
> Jul  3 15:38:30.061060 (d1) Testing HVM environment:
> Jul  3 15:38:30.061098 (d1)  - REP INSB across page boundaries ... passed
> Jul  3 15:38:30.069053 (d1)  - GS base MSRs and SWAPGS ... passed
> Jul  3 15:38:30.069087 (d1) Passed 2 of 2 tests
> Jul  3 15:38:30.069122 (d1) Writing SMBIOS tables ...
> Jul  3 15:38:30.077038 (d1) Loading ROMBIOS ...
> Jul  3 15:38:30.077071 (d1) 16892 bytes of ROMBIOS high-memory extensions:
> Jul  3 15:38:30.085038 (d1)   Relocating to 0xfc001000-0xfc0051fc ... done
> Jul  3 15:38:30.085077 (d1) Creating MP tables ...
> Jul  3 15:38:30.093048 (d1) Loading Cirrus VGABIOS ...
> Jul  3 15:38:30.093079 (d1) Loading PCI Option ROM ...
> Jul  3 15:38:30.093106 (d1)  - Manufacturer: http://ipxe.org
> Jul  3 15:38:30.101089 (d1)  - Product name: iPXE
> Jul  3 15:38:30.101118 (d1) Option ROMs:
> Jul  3 15:38:30.101157 (d1)  c0000-c8fff: VGA BIOS
> Jul  3 15:38:30.109054 (d1)  c9000-d8fff: Etherboot ROM
> Jul  3 15:38:30.109070 (d1) Loading ACPI ...
> Jul  3 15:38:30.109084 (d1) vm86 TSS at fc011480
> Jul  3 15:38:30.109121 (d1) BIOS map:
> Jul  3 15:38:30.117085 (d1)  f0000-fffff: Main BIOS
> Jul  3 15:38:30.117114 (d1) E820 table:
> Jul  3 15:38:30.117138 (d1)  [00]: 00000000:00000000 - 00000000:0009e000: RAM
> Jul  3 15:38:30.125089 (d1)  [01]: 00000000:0009e000 - 00000000:000a0000: 
> RESERVED
> Jul  3 15:38:30.125113 (d1)  HOLE: 00000000:000a0000 - 00000000:000e0000
> Jul  3 15:38:30.133060 (d1)  [02]: 00000000:000e0000 - 00000000:00100000: 
> RESERVED
> Jul  3 15:38:30.141086 (d1)  [03]: 00000000:00100000 - 00000000:2fc00000: RAM
> Jul  3 15:38:30.141104 (d1)  HOLE: 00000000:2fc00000 - 00000000:fc000000
> Jul  3 15:38:30.149034 (d1)  [04]: 00000000:fc000000 - 00000001:00000000: 
> RESERVED
> Jul  3 15:38:30.149079 (d1) Invoking ROMBIOS ...
> Jul  3 15:38:30.157028 (XEN) stdvga.c:147:d1v0 entering stdvga and caching 
> modes
> Jul  3 15:38:30.157075 (d1) VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 
> vruppert Exp $
> Jul  3 15:38:30.165046 (d1) Bochs BIOS - build: 06/23/99
> Jul  3 15:38:30.165085 (d1) $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
> Jul  3 15:38:30.173034 (d1) Options: apmbios pcibios eltorito PMM 
> Jul  3 15:38:30.181025 (d1) 
> Jul  3 15:38:30.181038 (d1) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (10000 
> MBytes)
> Jul  3 15:38:30.181065 (d1) ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
> Jul  3 15:38:30.189055 (d1) 
> Jul  3 15:38:30.189088 (d1) 
> Jul  3 15:38:30.189100 (d1) 
> Jul  3 15:38:30.189111 (d1) Press F12 for boot menu.
> Jul  3 15:38:30.189127 (d1) 
> Jul  3 15:38:30.197055 (d1) Booting from CD-Rom...
> Jul  3 15:38:30.197083 (d1) 626MB medium detected
> Jul  3 15:38:30.197113 (d1) CDROM boot failure code : 0005
> Jul  3 15:38:30.205047 (d1) Boot from CD-Rom failed: could not read the boot 
> disk
> Jul  3 15:38:30.205088 (d1) 
> Jul  3 15:38:30.205106 (d1) Booting from Hard Disk...
> Jul  3 15:38:30.213051 (d1) Boot from Hard Disk failed: not a bootable disk
> Jul  3 15:38:30.213093 (d1) 
> Jul  3 15:38:30.213106 (d1) 
> Jul  3 15:38:30.213121 (d1) No bootable device.
> Jul  3 15:38:30.221017 (d1) Powering off in 30 seconds.
> Jul  3 15:38:30.221033 (XEN) hvm.c:2408:d1v0 All CPUs offline -- powering off.

I saw this bug since the introduction of amd64-i386 stubdom test case.
Now it looks like intermittent, i.e. we failed at the beginning, passed
at some point, now it failed again.

Wei.

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