Re: [Xen-users] HVMLoader bug - staging

[Paulina Szubarczyk <paulinaszubarczyk@xxxxxxxxx>]

On 09/06/2016 06:13 PM, Anthony PERARD wrote:
> On Tue, Sep 06, 2016 at 02:55:10PM +0200, Paulina Szubarczyk wrote:
> > I have just updated the Xen staging branch (from commit '20624fde57^' to
> > '50c7203cc101^') and a domain that was working fine just a couple hours ago
> > now fails to create with the log from xl dmesg:
> >
> > (d1) Loading SeaBIOS ...
> > (d1) no BIOS ROM image found
> > (d1) *** HVMLoader bug at hvmloader.c:370
> > (d1) *** HVMLoader crashed.
> >
> > I see there were some changes according SeaBIOS in this period.
> > Is it a regression or should I adjust my configuration?
> >
> > Following a broader xl dmesg log:
> >
> > (XEN) memory.c:213:d0v3 Could not allocate order=18 extent: id=1 memflags=0
> > (0 of 1)
> > (XEN) memory.c:213:d0v3 Could not allocate order=9 extent: id=1 memflags=0
> > (2 of 4)
> > (XEN) memory.c:213:d0v3 Could not allocate order=9 extent: id=1 memflags=0
> > (0 of 4)
> > (XEN) memory.c:213:d0v3 Could not allocate order=9 extent: id=1 memflags=0
> > (0 of 4)
> > (XEN) memory.c:213:d0v3 Could not allocate order=9 extent: id=1 memflags=0
> > (0 of 4)
> > (XEN) memory.c:213:d0v3 Could not allocate order=9 extent: id=1 memflags=0
> > (0 of 4)
> > (XEN) memory.c:213:d0v3 Could not allocate order=9 extent: id=1 memflags=0
> > (0 of 4)
> > (XEN) HVM1 save: CPU
> > (XEN) HVM1 save: PIC
> > (XEN) HVM1 save: IOAPIC
> > (XEN) HVM1 save: LAPIC
> > (XEN) HVM1 save: LAPIC_REGS
> > (XEN) HVM1 save: PCI_IRQ
> > (XEN) HVM1 save: ISA_IRQ
> > (XEN) HVM1 save: PCI_LINK
> > (XEN) HVM1 save: PIT
> > (XEN) HVM1 save: RTC
> > (XEN) HVM1 save: HPET
> > (XEN) HVM1 save: PMTIMER
> > (XEN) HVM1 save: MTRR
> > (XEN) HVM1 save: VIRIDIAN_DOMAIN
> > (XEN) HVM1 save: CPU_XSAVE
> > (XEN) HVM1 save: VIRIDIAN_VCPU
> > (XEN) HVM1 save: VMCE_VCPU
> > (XEN) HVM1 save: TSC_ADJUST
> > (XEN) HVM1 restore: CPU 0
> > (d1) HVM Loader
> > (d1) Detected Xen v4.8-unstable
> > (d1) Xenbus rings @0xfeffc000, event channel 1
> > (d1) System requested SeaBIOS
> > (d1) CPU speed is 1696 MHz
> > (d1) Relocating guest memory for lowmem MMIO space disabled
> > (XEN) irq.c:275: Dom1 PCI link 0 changed 0 -> 5
> > (d1) PCI-ISA link 0 routed to IRQ5
> > (XEN) irq.c:275: Dom1 PCI link 1 changed 0 -> 10
> > (d1) PCI-ISA link 1 routed to IRQ10
> > (XEN) irq.c:275: Dom1 PCI link 2 changed 0 -> 11
> > (d1) PCI-ISA link 2 routed to IRQ11
> > (XEN) irq.c:275: Dom1 PCI link 3 changed 0 -> 5
> > (d1) PCI-ISA link 3 routed to IRQ5
> > (d1) pci dev 01:2 INTD->IRQ5
> > (d1) pci dev 01:3 INTA->IRQ10
> > (d1) pci dev 02:0 INTA->IRQ11
> > (d1) pci dev 04:0 INTA->IRQ5
> > (d1) No RAM in high memory; setting high_mem resource base to 100000000
> > (d1) pci dev 03:0 bar 10 size 002000000: 0f0000008
> > (d1) pci dev 02:0 bar 14 size 001000000: 0f2000008
> > (d1) pci dev 04:0 bar 30 size 000040000: 0f3000000
> > (d1) pci dev 03:0 bar 30 size 000010000: 0f3040000
> > (d1) pci dev 03:0 bar 14 size 000001000: 0f3050000
> > (d1) pci dev 02:0 bar 10 size 000000100: 00000c001
> > (d1) pci dev 04:0 bar 10 size 000000100: 00000c101
> > (d1) pci dev 04:0 bar 14 size 000000100: 0f3051000
> > (d1) pci dev 01:2 bar 20 size 000000020: 00000c201
> > (d1) pci dev 01:1 bar 20 size 000000010: 00000c221
> > (d1) Multiprocessor initialisation:
> > (d1)  - CPU0 ... 39-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
> > (d1) Testing HVM environment:
> > (d1)  - REP INSB across page boundaries ... passed
> > (d1)  - GS base MSRs and SWAPGS ... passed
> > (d1) Passed 2 of 2 tests
> > (d1) Writing SMBIOS tables ...
> > (d1) Loading SeaBIOS ...
> > (d1) no BIOS ROM image found
> > (d1) *** HVMLoader bug at hvmloader.c:370
> > (d1) *** HVMLoader crashed.
>
> Could you send the output of:
> xl -vvv create ..
>
> > the domain .cfg file:
> > #
> > # Kernel
> > #`
> > builder = 'hvm'
> > memory  = '3072'
> > vcpus   = '1'
> > boot    = "c"
> > bootloader = "pygrub"
> You have the bootloader option here, but it seams to be a PV guest
> config only, according to the man. Does your guest work without it?
Yes, it works without that option.

> In any case, there is probably a bug if someone try to use 'kernel'
> config option with an HVM guest.
It is a newbie mistake here, I run make clean but without configure.
I am sorry for a trouble. It seems to work fine right now.

> Thanks,
>
> > #
> > # Disk devices
> > #
> > disk    = ['phy:/dev/vg0/suse,hda,w']
> > acpi    = '1'
> > apic    = '1'
> > pae     = '1'
> > serial  = 'pty'
> > usb     = '1'
> >
> > #
> > # Networking
> > #
> > vif     = ['bridge=xenbr0']
> > dhcp    = 'dhcp'
> >
> >
> > Thank you,
> > Paulina Szubarczyk
Thank you,
Paulina

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users