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

[Xen-devel] Help regarding bringing up dom0 for lager board



Hi, I am trying to bring up Dom0 and DomU in xen in lager board. I have followed the instructions in https://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Lager . I am unable to boot Dom0. I am getting the following log.


----------------------------------------------------------
| LAGER SPI_BOOT_LOADER (USER:S25FL512) V0.12 2013.04.09 |
|        -----   QUAD READ (DMA Version)   -----         |
----------------------------------------------------------
 Now Loading ....... com

U-Boot 2014.10 (Nov 03 2016 - 17:24:44)

CPU: Renesas Electronics R8A7790 rev 1.0
Board: Lager
I2C:   ready
DRAM:  2 GiB
SF: Detected S25FL512S_256K with page size 512 Bytes, erase size 256 KiB, total 64 MiB
In:    serial
Out:   serial
Err:   serial
Net:   sh_eth
Hit any key to stop autoboot:  0
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.1.1; our IP address is 192.168.1.100
Filename 'xen-uImage'.
Load address: 0x70007fc0
Loading: #################################################################
     #################################################################
     ########################
     2.5 MiB/s
done
Bytes transferred = 787392 (c03c0 hex)
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.1.1; our IP address is 192.168.1.100
Filename 'uImage-r8a7790-lager-xen.dtb'.
Load address: 0x70f00000
Loading: #########
     1.8 MiB/s
done
Bytes transferred = 44950 (af96 hex)
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.1.1; our IP address is 192.168.1.100
Filename 'zImage-uImage'.
Load address: 0x72000000
Loading: #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #########################################################
     2.5 MiB/s
done
Bytes transferred = 2618920 (27f628 hex)
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.1.1; our IP address is 192.168.1.100
Filename 'xenpolicy-4.7.1'.
Load address: 0x74000000
Loading: ##
     878.9 KiB/s
done
Bytes transferred = 9906 (26b2 hex)
## Booting kernel from Legacy Image at 70007fc0 ...
   Image Name:   XEN
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    787328 Bytes = 768.9 KiB
   Load Address: 90000000
   Entry Point:  90000000
## Flattened Device Tree blob at 70f00000
   Booting using the fdt blob at 0x70f00000
   Loading Kernel Image ... OK
   Loading Device Tree to 40ef2000, end 40efff95 ... OK

Starting kernel ...

- UART enabled -
- CPU 00000000 booting -
- Xen starting in Hyp mode -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000040000000 - 000000007fffffff
(XEN) RAM: 0000000140000000 - 00000001ffffffff
(XEN)
(XEN) MODULE[0]: 0000000040ef2000 - 0000000040efd000 Device Tree 
(XEN) MODULE[1]: 0000000072000000 - 000000007227f628 Kernel      
(XEN) MODULE[2]: 0000000074000000 - 00000000740026b2 XSM         
(XEN)  RESVD[0]: 000000007ff9a000 - 000000007ff9a120
(XEN)  RESVD[1]: 0000000040ef2000 - 0000000040efd000
(XEN)
(XEN) Command line: console=dtuart dom0_mem=1G
(XEN) Placing Xen at 0x000000007fc00000-0x000000007fe00000
(XEN) Update BOOTMOD_XEN from 0000000090000000-0000000090105781 => 000000007fc00000-000000007fd05781
(XEN) Xen heap: 00000001f8000000-0000000200000000 (32768 pages)
(XEN) Dom heap: 1015808 pages
(XEN) Domain heap initialised
(XEN) Platform: Renesas R-Car Gen2
(XEN) Taking dtuart configuration from /chosen/stdout-path
(XEN) Looking for dtuart at "/serial@e6e60000", options ""
 Xen 4.7.1
(XEN) Xen version 4.7.1  (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) 4.8.4) debug=y Mon Nov  7 11:44:45 IST 2016
(XEN) Latest ChangeSet:
(XEN) Processor: 413fc0f2: "ARM Limited", variant: 0x3, part 0xc0f, rev 0x2
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00001131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 02010555
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 40000000 01240000 02102211
(XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 10000 KHz
(XEN) GICv2: WARNING: The GICC size is too small: 0x1000 expected 0x2000
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000f1001000
(XEN)         gic_cpu_addr=00000000f1002000
(XEN)         gic_hyp_addr=00000000f1004000
(XEN)         gic_vcpu_addr=00000000f1006000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 416 lines, 8 cpus, secure (IID 0200043b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
(XEN) Bringing up CPU1
- CPU 00000001 booting -
- Xen starting in Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
- CPU 00000002 booting -
- Xen starting in Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
- CPU 00000003 booting -
- Xen starting in Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 3 booted.
(XEN) Bringing up CPU4
(XEN) CPU4 never came online
(XEN) Failed to bring up CPU 4 (error -5)
(XEN) Bringing up CPU5
(XEN) CPU5 never came online
(XEN) Failed to bring up CPU 5 (error -5)
(XEN) Bringing up CPU6
(XEN) CPU6 never came online
(XEN) Failed to bring up CPU 6 (error -5)
(XEN) Bringing up CPU7
(XEN) CPU7 never came online
(XEN) Failed to bring up CPU 7 (error -5)
(XEN) Brought up 4 CPUs
(XEN) P2M: 40-bit IPA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 0000000072000000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000048000000-0x00000070000000 (640MB)
(XEN) BANK[1] 0x000001d8000000-0x000001f0000000 (384MB)
(XEN) Grant table range: 0x0000007fc00000-0x0000007fc64000
(XEN) Loading zImage from 0000000072000000 to 000000004fc00000-000000004fe7f628
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x0000000050000000-0x000000005000ab50
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) ........done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 276kB init memory.
(XEN) traps.c:2505:d0v0 HSR=0x93820007 pc=0xc001d084 gva=0xe7804060 gpa=0x000000e6160060


It gets stuck here.
Dom0 is not booted. Can somebody please suggest ways to correct it?
I am attaching the dts file I have used.

Attachment: r8a7790-lager-xen.dts
Description: audio/vnd.dts

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

 


Rackspace

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