[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Problem on test with ovmf



On Wed, Oct 29, 2014 at 04:21:10PM +0100, Fabio Fantoni wrote:
> I saw that pv on ovmf are finally accepted upstream so I tested updated ovmf
> (pvdisk-v5 from people/aperard/ovmf.git).
> I tried to install windows 7 pro 64 bit domUs but it show only black screen
> after initial windows dvd loading bar.
> I saw these errors in xl dmesg:
> *(XEN) page_alloc.c:1646:d2v0 Over-allocation for domain 2: 524545 >
> 524544**
> **(XEN) memory.c:155:d2v0 Could not allocate order=0 extent: id=2 memflags=0
> (0 of 1)*

Those errors are not real issue. Here, hvmloader try to allocate some
more memory, which fail (with the two printed error), so hvmloader move
on and try something different. The boot is not affected.

About your issue with Win7, have you try to boot it without vga="qxl" ?

Thanks for testing.

> I have almost 10 gb of ram free so is not lack of resources problem but
> seems unexpected case or bug in hvmloader or other xen part.
> I also check qemu log but there is any warning or errors.
> 
> Here the full xl dmesg about the domU:
> >(d2) HVM Loader
> >(d2) Detected Xen v4.5-unstable
> >(d2) Xenbus rings @0xfeffc000, event channel 1
> >(d2) System requested OVMF
> >(d2) CPU speed is 2660 MHz
> >(d2) Relocating guest memory for lowmem MMIO space disabled
> >(XEN) irq.c:270: Dom2 PCI link 0 changed 0 -> 5
> >(d2) PCI-ISA link 0 routed to IRQ5
> >(XEN) irq.c:270: Dom2 PCI link 1 changed 0 -> 10
> >(d2) PCI-ISA link 1 routed to IRQ10
> >(XEN) irq.c:270: Dom2 PCI link 2 changed 0 -> 11
> >(d2) PCI-ISA link 2 routed to IRQ11
> >(XEN) irq.c:270: Dom2 PCI link 3 changed 0 -> 5
> >(d2) PCI-ISA link 3 routed to IRQ5
> >(d2) pci dev 01:3 INTA->IRQ10
> >(d2) pci dev 02:0 INTA->IRQ11
> >(d2) pci dev 03:0 INTA->IRQ5
> >(d2) pci dev 04:0 INTA->IRQ5
> >(d2) pci dev 05:0 INTA->IRQ10
> >(d2) pci dev 06:0 INTA->IRQ11
> >(d2) pci dev 1d:0 INTA->IRQ10
> >(d2) pci dev 1d:1 INTB->IRQ11
> >(d2) pci dev 1d:2 INTC->IRQ5
> >(d2) pci dev 1d:7 INTD->IRQ5
> >(d2) No RAM in high memory; setting high_mem resource base to 100000000
> >(d2) pci dev 05:0 bar 10 size 004000000: 0f0000000
> >(d2) pci dev 05:0 bar 14 size 004000000: 0f4000000
> >(d2) pci dev 02:0 bar 14 size 001000000: 0f8000008
> >(d2) pci dev 06:0 bar 30 size 000040000: 0f9000000
> >(d2) pci dev 05:0 bar 30 size 000010000: 0f9040000
> >(d2) pci dev 03:0 bar 10 size 000004000: 0f9050000
> >(d2) pci dev 05:0 bar 18 size 000002000: 0f9054000
> >(d2) pci dev 04:0 bar 14 size 000001000: 0f9056000
> >(d2) pci dev 1d:7 bar 10 size 000001000: 0f9057000
> >(d2) pci dev 02:0 bar 10 size 000000100: 00000c001
> >(d2) pci dev 06:0 bar 10 size 000000100: 00000c101
> >(d2) pci dev 06:0 bar 14 size 000000100: 0f9058000
> >(d2) pci dev 04:0 bar 10 size 000000020: 00000c201
> >(d2) pci dev 05:0 bar 1c size 000000020: 00000c221
> >(d2) pci dev 1d:0 bar 20 size 000000020: 00000c241
> >(d2) pci dev 1d:1 bar 20 size 000000020: 00000c261
> >(d2) pci dev 1d:2 bar 20 size 000000020: 00000c281
> >(d2) pci dev 01:1 bar 20 size 000000010: 00000c2a1
> >(d2) Multiprocessor initialisation:
> >(d2)  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
> >(d2)  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
> >(d2) Testing HVM environment:
> >(d2)  - REP INSB across page boundaries ... passed
> >(d2)  - GS base MSRs and SWAPGS ... passed
> >(d2) Passed 2 of 2 tests
> >(d2) Writing SMBIOS tables ...
> >(d2) Loading OVMF ...
> >(XEN) page_alloc.c:1646:d2v0 Over-allocation for domain 2: 524545 > 524544
> >(XEN) memory.c:155:d2v0 Could not allocate order=0 extent: id=2 memflags=0
> >(0 of 1)
> >(d2) Loading ACPI ...
> >(d2) S3 disabled
> >(d2) S4 disabled
> >(d2) vm86 TSS at fc012c80
> >(d2) BIOS map:
> >(d2)  ffe00000-ffffffff: Main BIOS
> >(d2) E820 table:
> >(d2)  [00]: 00000000:00000000 - 00000000:000a0000: RAM
> >(d2)  HOLE: 00000000:000a0000 - 00000000:000f0000
> >(d2)  [01]: 00000000:000f0000 - 00000000:00100000: RESERVED
> >(d2)  [02]: 00000000:00100000 - 00000000:77eab000: RAM
> >(d2)  HOLE: 00000000:77eab000 - 00000000:fc000000
> >(d2)  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
> >(d2) Invoking OVMF ...
> >(XEN) irq.c:270: Dom2 PCI link 0 changed 5 -> 11
> >(XEN) irq.c:270: Dom2 PCI link 1 changed 10 -> 11
> >(XEN) irq.c:270: Dom2 PCI link 2 changed 11 -> 10
> >(XEN) irq.c:270: Dom2 PCI link 3 changed 5 -> 10
> 
> And the domU's xl cfg:
> name='W7-UEFI'
> builder="hvm"
> bios="ovmf"
> memory=2048
> vcpus=2
> acpi_s3=0
> acpi_s4=0
> vif=['bridge=xenbr0,mac=00:16:3e:b6:c7:d1']
> disk=['/mnt/vm/disks/W7-UEFI.disk1.xm,raw,hda,rw','/mnt/vm/iso/W7PRO64SP1.iso,raw,hdb,ro,cdrom']
> boot='dc'
> device_model_version="qemu-xen"
> viridian=1
> vnc=0
> keymap="it"
> on_crash="destroy"
> vga="qxl"
> spice=1
> spicehost='0.0.0.0'
> spiceport=6006
> spicedisable_ticketing=1
> spicevdagent=1
> spice_clipboard_sharing=0
> spiceusbredirection=4
> soundhw="hda"
> localtime=1
> usbversion=2
> 
> I did other ovmf tests very long time ago, probably one year or more and I
> not remember exactly them.
> 
> If you need more informations and or test tell me and I'll post them.
> 
> Thanks for any reply and sorry for my bad english.

-- 
Anthony PERARD

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.