[Xen-devel] passthrough
Hi, Is it possible to give each channels of uart to different guests via pass through mechanism? regards Georgeeldhojohn ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] passthrough
Thanks for the reply. we are using renesas rcar h3 board. Does it supports? On Tuesday, May 23, 2017, Jan Beulich wrote: > >>> On 23.05.17 at 11:38, > > wrote: > > Is it possible to give each channels of uart to different guests via pass > > through mechanism? > > If each channel is represented by a separate PCI device/function, > then likely yes. If they're all one PCI device, or not a PCI device > at all, then you may be able to hand them through (by allowing > each guest to access the respective port numbers or MMIO space), > but an IOMMU in the system could not be leveraged to make this > half way secure. > > Jan > > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] regarding Dom U pv guests
Hi, I was trying to study the working of xen. From what I understood, dom0 issues a hypercall to create domU. but I couldn't understand where the dtb for domU comes from?. I found the flow from hypercall to domain_create function. please help me... ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Regarding changing memory for DOM0
Hai all, Sorry for the delay First of all Thank you very much for the quick reply. I tried the same with MMC root .It boot up successfully but after typing xl list I am getting following errors libxl: error: libxl.c:662:libxl_list_domain: getting domain info list: Permission denied During next booting, the memory card got corrupted. U-Boot 2015.04 (Feb 15 2017 - 15:16:02) CPU: Renesas Electronics R8A7795 rev 1.1 Board: Salvator-X I2C: ready DRAM: 3.9 GiB MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2 In:serial Out: serial Err: serial Net: Board Net Initialization Failed No ethernet found. Hit any key to stop autoboot: 0 Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Wrong Image Format for bootm command ERROR: can't get kernel image On Aug 14, 2017 5:41 PM, "Andrii Anisov" wrote: > Hello Julien, > > > On 14.08.17 14:50, Julien Grall wrote: > >> The kernel should really be able to deal with memory below and above 4GB. >> > Yes, it should. I suppose a bug somewhere in Renesas eth driver. > Meanwhile George John could make some investigations. > > Otherwise the problem would be exactly the same on baremetal as the board >> support seems to have bank above 4GB... >> >> The first step here is to check that NFS is working on baremetal. I don't >> remember if this has been yet done. >> > NFS does work baremetal. It is the default BSP configuration. > NFS works when Dom0 has 752 MB ram under 4GB. > > -- > > *Andrii Anisov* > > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Regarding hdmi sharing in xen
> > Dear Andrii Anisov, Thank you for the reply. We are using R-Car H3 salvator X. > It really depends on the setup you need. Our plan is to run Linux as Dom0 and Android as DomU. The Linux portion will be having 1 HDMI display and the Android porion will be having 1 HDMI. Can we share the DU and use the HDMI port as it is in the guests? In case the DU is shared, will it be possible to Passthrough the HDMI to other Guests? Regards, George ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] Android bring up over xen for Rcar-H3
Hi all, I want to bring up Android over Xen as Dom0 on Rcar-H3 salvator x board. Can anybody please share the procedure to do so.?. Regards, George ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] Regarding changing memory for DOM0
Hi,
I am running Xen on Rcar H3 which is now configured Dom0 memory as 752M
and need to change it as 2048M.I attempted to change it by
xl mem-set (xl mem-set 0 2048M) where 0 is Dom0 ID.It result following
error
root@salvator-x-xen-dom0:~# xl list
NameID Mem VCPUsState
Time(s)
Domain-0 0 752 4 r-
11.4
root@salvator-x-xen-dom0:~#
my try as folows
-
root@salvator-x-xen-dom0:~# xl mem-set 0 2048m
xl: libxl.c:345: libxl_defbool_val: Assertion
`!libxl_defbool_is_default(db)' failed.
[ 256.101168] audit: type=1701 audit(255.882:3): auid=4294967295 uid=0
gid=0 ses=4294967295 pid=2972 comm="xl" exe="/usr/sbin/xl" sig=6
Aborted
root@salvator-x-xen-dom0:~#
next I tried it by modifying bootargs in the dts file
before modification
--
chosen {
bootargs = "dom0_mem=752M console=dtuart dtuart=serial0
dom0_max_vcpus=4 bootscrub=0 flask_enforcing=1 loglvl=all";
xen,dom0-bootargs = "console=hvc0 root=/dev/nfs
nfsroot=192.168.1.100:/exports/rfs_xen/ ip=192.168.1.1:192.168.1.100 rw
rootwait ignore_loglevel cma=128M";
.
.
.
.
.
}
after modification
--
chosen {
bootargs = "dom0_mem=2048M console=dtuart dtuart=serial0
dom0_max_vcpus=4 bootscrub=0 flask_enforcing=1 loglvl=all";
xen,dom0-bootargs = "console=hvc0 root=/dev/nfs
nfsroot=192.168.1.100:/exports/rfs_xen/ ip=192.168.1.1:192.168.1.100 rw
rootwait ignore_loglevel cma=128M";
.
.
.
.
.
}
but unfortunately file system crashes while booting
xen version is 4.8.0
any help please
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Re: [Xen-devel] Regarding changing memory for DOM0
Hi all, Thank you for the reply. I checked with xen version 4.9, Still the error for the filesystem persists. What seems to be the problem?. I am attaching the log for the above error and also the dts file I am using. Regards, George NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.9 NOTICE: BL2: PRR is R-Car H3 ES1.1 NOTICE: BL2: Boot device is HyperFlash(80MHz) NOTICE: BL2: LCM state is CM NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x52 NOTICE: BL2: DDR2400(rev.0.15) NOTICE: BL2: DRAM Split is 4ch NOTICE: BL2: QoS is default setting(rev.0.32) NOTICE: BL2: v1.1(release):3ad02ac NOTICE: BL2: Built : 15:16:01, Feb 15 2017 NOTICE: BL2: Normal boot NOTICE: BL2: dst=0xe631a208 src=0x818 len=512(0x200) NOTICE: BL2: dst=0x43f0 src=0x8180400 len=6144(0x1800) NOTICE: BL2: dst=0x4400 src=0x81c len=65536(0x1) NOTICE: BL2: dst=0x4410 src=0x820 len=524288(0x8) NOTICE: BL2: dst=0x4900 src=0x864 len=1048576(0x10) U-Boot 2015.04 (Feb 15 2017 - 15:16:02) CPU: Renesas Electronics R8A7795 rev 1.1 Board: Salvator-X I2C: ready DRAM: 3.9 GiB MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2 In:serial Out: serial Err: serial Net: ravb Hit any key to stop autoboot: 0 ravb Waiting for PHY auto negotiation to complete.. done ravb: 100Base/Full Using ravb device TFTP from server 192.168.1.100; our IP address is 192.168.1.1 Filename 'xen-uImage'. Load address: 0x4808 Loading: # # ### 129.9 KiB/s done Bytes transferred = 721296 (b0190 hex) ravb:0 is connected to ravb. Reconnecting to ravb ravb Waiting for PHY auto negotiation to complete.. done ravb: 100Base/Full Using ravb device TFTP from server 192.168.1.100; our IP address is 192.168.1.1 Filename 'r8a7795-salvator-x-dom0.dtb'. Load address: 0x4800 Loading: # 12.7 KiB/s done Bytes transferred = 65776 (100f0 hex) ravb:0 is connected to ravb. Reconnecting to ravb ravb Waiting for PHY auto negotiation to complete.. done ravb: 100Base/Full Using ravb device TFTP from server 192.168.1.100; our IP address is 192.168.1.1 Filename 'Image'. Load address: 0x7a00 Loading: # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
[Xen-devel] Regarding hdmi sharing in xen
hi, I am a newbie. Please correct if I am wrong?. I have a r-car H3 board with Dom0 and two DomU's. Do we have to passthrough one of the hdmi ports to the one guest if we could implement GPU sharing between Dom0 and one DomU in r-car h3 board.? ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] Error in Xen while booting for salvator-X (M3 Board)
Hi, I was trying out xen in salvator-X(M3 Board as described in https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X I ran in to following error: U-Boot 2015.04 (Feb 21 2017 - 14:24:48) CPU: Renesas Electronics R8A7796 rev 1.0 Board: Salvator-X I2C: ready DRAM: 3.9 GiB MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2 In:serial Out: serial Err: serial Net: Board Net Initialization Failed No ethernet found. Hit any key to stop autoboot: 0 819584 bytes read in 89 ms (8.8 MiB/s) 64927 bytes read in 23 ms (2.7 MiB/s) 14038016 bytes read in 1188 ms (11.3 MiB/s) 10319 bytes read in 19 ms (530.3 KiB/s) ## Booting kernel from Legacy Image at 4808 ... Image Name: XEN Image Type: AArch64 Linux Kernel Image (uncompressed) Data Size:819520 Bytes = 800.3 KiB Load Address: 7808 Entry Point: 7808 Verifying Checksum ... OK ## Flattened Device Tree blob at 4800 Booting using the fdt blob at 0x4800 Loading Kernel Image ... OK Using Device Tree in place at 4800, end 48012d9e Starting kernel ... - UART enabled - - CPU booting - - Current EL 0008 - - Xen starting at EL2 - - Zero BSS - - Setting up control registers - - Turning on paging - - Ready - (XEN) Checking for initrd in /chosen (XEN) RAM: 4800 - 7fff (XEN) RAM: 0005 - 00053fff (XEN) RAM: 0006 - 00063fff (XEN) RAM: 0007 - 00073fff (XEN) (XEN) MODULE[0]: 4800 - 4801 Device Tree (XEN) MODULE[1]: 7a00 - 7c00 Kernel (XEN) MODULE[2]: 7c00 - 7c01 XSM (XEN) RESVD[0]: 4800 - 4801 (XEN) (XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0 dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1 (XEN) Placing Xen at 0x7fe0-0x8000 (XEN) Update BOOTMOD_XEN from 7808-78196e01 => 7fe0-7ff16e01 After this, it hangs. What could be the possible reason? Regards, George ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Error in Xen while booting for salvator-X (M3 Board)
Hi,
Thanks for the reply,
I am using Linux version 4.6.
The memory nodes were already squashed. When I have used a different
version of Xen, it booted to dom0. but still the crash occurs as shown in
the log below.
I have also noticed that for salvator x M3 board(r8a7796) the dtb file used
was r8a7795-salvator-x-dom0.dtb
Is it ok?
regards,
George
On Fri, Feb 24, 2017 at 8:43 PM, Oleksandr Tyshchenko
wrote:
> Hi,
>
> Not 100% sure, but anyway...
>
> Can you recheck after squashing all memory nodes to a single one.
>
> ---
> I guess, you have following in your device tree:
>
> memory@4800 {
> device_type = "memory";
> /* first 128MB is reserved for secure area. */
> reg = <0x0 0x4800 0x0 0x3800>;
> };
>
> memory@5 {
> device_type = "memory";
> reg = <0x5 0x 0x0 0x4000>;
> };
>
> memory@6 {
> device_type = "memory";
> reg = <0x6 0x 0x0 0x4000>;
> };
>
> memory@7 {
> device_type = "memory";
> reg = <0x7 0x 0x0 0x4000>;
> };
>
> ---
> Try to make next:
>
> memory@4800 {
> device_type = "memory";
> /* first 128MB is reserved for secure area. */
> reg = <0x0 0x4800 0x0 0x3800>,
> <0x5 0x 0x0 0x4000>,
> <0x6 0x 0x0 0x4000>,
> <0x7 0x 0x0 0x4000>;
> };
>
>
>
> On Fri, Feb 24, 2017 at 4:53 PM, Julien Grall
> wrote:
> >
> >
> > On 21/02/17 12:03, George John wrote:
> >>
> >> Hi,
> >
> >
> > Hello,
> >
> >
> >> I was trying out xen in salvator-X(M3 Board as described
> >> in
> >> https://wiki.xenproject.org/wiki/Xen_ARM_with_
> Virtualization_Extensions/Salvator-X
> >>
> >> I ran in to following error:
> >>
> >>
> >> U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
> >>
> >> CPU: Renesas Electronics R8A7796 rev 1.0
> >> Board: Salvator-X
> >> I2C: ready
> >> DRAM: 3.9 GiB
> >> MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
> >> In:serial
> >> Out: serial
> >> Err: serial
> >> Net: Board Net Initialization Failed
> >> No ethernet found.
> >> Hit any key to stop autoboot: 0
> >> 819584 bytes read in 89 ms (8.8 MiB/s)
> >> 64927 bytes read in 23 ms (2.7 MiB/s)
> >> 14038016 bytes read in 1188 ms (11.3 MiB/s)
> >> 10319 bytes read in 19 ms (530.3 KiB/s)
> >> ## Booting kernel from Legacy Image at 4808 ...
> >>Image Name: XEN
> >>Image Type: AArch64 Linux Kernel Image (uncompressed)
> >>Data Size:819520 Bytes = 800.3 KiB
> >>Load Address: 7808
> >>Entry Point: 7808
> >>Verifying Checksum ... OK
> >> ## Flattened Device Tree blob at 4800
> >>Booting using the fdt blob at 0x4800
> >>Loading Kernel Image ... OK
> >>Using Device Tree in place at 4800, end 48012d9e
> >>
> >> Starting kernel ...
> >>
> >> - UART enabled -
> >> - CPU booting -
> >> - Current EL 0008 -
> >> - Xen starting at EL2 -
> >> - Zero BSS -
> >> - Setting up control registers -
> >> - Turning on paging -
> >> - Ready -
> >> (XEN) Checking for initrd in /chosen
> >> (XEN) RAM: 4800 - 7fff
> >> (XEN) RAM: 0005 - 00053fff
> >> (XEN) RAM: 0006 - 00063fff
> >> (XEN) RAM: 0007 - 00073fff
> >> (XEN)
> >> (XEN) MODULE[0]: 4800 - 4801 Device Tree
> >> (XEN) MODULE[1]: 7a00 - 7c00 Kernel
> >> (XEN) MODULE[2]: 7c00 - 7c01 XSM
> >> (XEN) RESVD[0]: 4800 - 4801
> >> (XEN)
> >> (XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0
> >> dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1
> >> (XEN) Placing Xen at 0x7fe0-0x8000
> >> (XEN) Update BOOTMOD_XEN from 7808-78196e01 =>
> >> 7fe0-7ff16e01
> >
> >
> > Which kernel version is it?
> >
> >>
> >>
> >>
> >>
> >>
> >>
> >> After this, it hangs. What could be the possible reason?
> >
> >
> > Xen will initialize the heap and then continue into the boot. I would add
> > more debug around setup_mm to see where it failed.
> >
> > Regards,
> >
> > --
> > Julien Grall
> >
> > ___
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > https://lists.xen.org/xen-devel
>
>
>
> --
> Regards,
>
> Oleksandr Tyshchenko
>
log_27_feb2017
Description: Binary data
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Re: [Xen-devel] Error in Xen while booting for salvator-X (M3 Board)
Hi,
Thanks for the support. I think I solved the problem partially.
@Andrii
> So I guess you see the abort on access to a peripheral missing on r8a7796
> but described in a device tree for r8a7795.
>
You were right. I commented out &sata and &rcarsound nodes from the device
tree created for xen and made some other modifications. The Dom0 now boots
without crash.
@Oleksandr
> PFA the DTS I use for M3ULCB board
Thank you very much. I used it for reference. I got a bit lucky because of
the fact that H3 and M3 are similar.
Still the framebuffer is not coming up. I will try to update with the logs
Thanks and regards,
George
On Mon, Feb 27, 2017 at 4:25 PM, Oleksandr Andrushchenko wrote:
> Hi,
>
> PFA the DTS I use for M3ULCB board
>
>
>
> On 02/27/2017 12:48 PM, Oleksandr Tyshchenko wrote:
>
>> Hi.
>>
>> On Mon, Feb 27, 2017 at 12:29 PM, George John
>> wrote:
>>
>>> Hi,
>>> Thanks for the reply,
>>> I am using Linux version 4.6.
>>> The memory nodes were already squashed. When I have used a different
>>> version
>>> of Xen, it booted to dom0. but still the crash occurs as shown in the log
>>> below.
>>>
>>> I have also noticed that for salvator x M3 board(r8a7796) the dtb file
>>> used
>>> was r8a7795-salvator-x-dom0.dtb
>>> Is it ok?
>>>
>> I don't know about M3 board.
>> CC my colleague who plays with M3 board. Hope, that he can shed some
>> lights.
>>
>> regards,
>>> George
>>>
>>> On Fri, Feb 24, 2017 at 8:43 PM, Oleksandr Tyshchenko <
>>> olekst...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Not 100% sure, but anyway...
>>>>
>>>> Can you recheck after squashing all memory nodes to a single one.
>>>>
>>>> ---
>>>> I guess, you have following in your device tree:
>>>>
>>>> memory@4800 {
>>>> device_type = "memory";
>>>> /* first 128MB is reserved for secure area. */
>>>> reg = <0x0 0x4800 0x0 0x3800>;
>>>> };
>>>>
>>>> memory@5 {
>>>> device_type = "memory";
>>>> reg = <0x5 0x 0x0 0x4000>;
>>>> };
>>>>
>>>> memory@6 {
>>>> device_type = "memory";
>>>> reg = <0x6 0x 0x0 0x4000>;
>>>> };
>>>>
>>>> memory@7 {
>>>> device_type = "memory";
>>>> reg = <0x7 0x 0x0 0x4000>;
>>>> };
>>>>
>>>> ---
>>>> Try to make next:
>>>>
>>>> memory@4800 {
>>>> device_type = "memory";
>>>> /* first 128MB is reserved for secure area. */
>>>> reg = <0x0 0x4800 0x0 0x3800>,
>>>> <0x5 0x 0x0 0x4000>,
>>>> <0x6 0x 0x0 0x4000>,
>>>> <0x7 0x 0x0 0x4000>;
>>>> };
>>>>
>>>>
>>>>
>>>> On Fri, Feb 24, 2017 at 4:53 PM, Julien Grall
>>>> wrote:
>>>>
>>>>>
>>>>> On 21/02/17 12:03, George John wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>>
>>>>> I was trying out xen in salvator-X(M3 Board as described
>>>>>> in
>>>>>>
>>>>>> https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization
>>>>>> _Extensions/Salvator-X
>>>>>>
>>>>>> I ran in to following error:
>>>>>>
>>>>>>
>>>>>> U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
>>>>>>
>>>>>> CPU: Renesas Electronics R8A7796 rev 1.0
>>>>>> Board: Salvator-X
>>>>>> I2C: ready
>>>>>> DRAM: 3.9 GiB
>>>>>> MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
>>>>>> In:serial
>>>>>> Out: serial
>>>>>> Err: serial
>>>>>> Net: Board Net Initialization Failed
>>>>>> No ethernet found.
>>>>>> Hit any key to stop autoboot: 0
>>>>>> 819584 bytes read in 89 ms (8.8 MiB/s)
>>>>>> 64927 bytes read in 23 ms (2.7 MiB/s)
>>>>>> 14038016 byt
Re: [Xen-devel] Help regarding bringing up dom0 for lager board
Thanks it was really the problem of dts. I just followed the proceedings of Ferger in Mailing lists who tried to bring up Dom0 in lager, and I got it booted up. But now the problem is with rootfs. I am checking on that.. Thanks and regards, George On Tue, Nov 8, 2016 at 5:20 PM, Julien Grall wrote: > > > On 07/11/2016 16:39, George John wrote: > >> Hi, >> > > Hello, > > (XEN) Freed 276kB init memory. >> (XEN) traps.c:2505:d0v0 HSR=0x93820007 pc=0xc001d084 gva=0xe7804060 >> gpa=0x00e6160060 >> > > Looking at the log, DOM0 is trying to access an region that is not mapped > (0x00e6160060). > > When booting Xen is going through the device tree and mapping to dom0 all > the regions described. So it seems that this region is not present in the > device tree. > > Which Linux kernel are you using? I would recommend you to try the latest > as possible and use the device-tree provided in arch/arm/boot/dts/ to see > if it solves the problem. > > Cheers, > > -- > Julien Grall > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] Error regarding filesystem in Dom0 in lager board
Hi, I just bumped in to some errors related to filesystem . The following is the log. I am using xen 4.7.1 along with linux kernel 3.19.8 as Dom0 Starting kernel ... - UART enabled - - CPU booting - - Xen starting in Hyp mode - - Zero BSS - - Setting up control registers - - Turning on paging - - Ready - (XEN) Checking for initrd in /chosen (XEN) RAM: 4000 - 7fff (XEN) RAM: 00014000 - 0001 (XEN) (XEN) MODULE[0]: 40ef2000 - 40efe000 Device Tree (XEN) MODULE[1]: 7200 - 722a0660 Kernel (XEN) MODULE[2]: 7400 - 7400284f XSM (XEN) RESVD[0]: 7ff9a000 - 7ff9a120 (XEN) RESVD[1]: 40ef2000 - 40efe000 (XEN) (XEN) Command line: console=dtuart dom0_mem=1G (XEN) Placing Xen at 0x7fc0-0x7fe0 (XEN) Update BOOTMOD_XEN from 9000-90105781 => 7fc0-7fd05781 (XEN) Xen heap: 0001f800-0002 (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 "serial0", options "38400n8" (XEN) WARNING: UART configuration is not supported Xen 4.7.1 (XEN) Xen version 4.7.1 (tel...@tvm.telxsi.com) (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: 1131:00011011 (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle (XEN) Extensions: GenericTimer Security (XEN) Debug Features: 02010555 (XEN) Auxiliary Features: (XEN) Memory Model Features: 10201105 4000 0124 02102211 (XEN) ISA Features: 02101110 13112111 21232041 2131 10011142 (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1 KHz (XEN) GICv2: WARNING: The GICC size is too small: 0x1000 expected 0x2000 (XEN) GICv2 initialization: (XEN) gic_dist_addr=f1001000 (XEN) gic_cpu_addr=f1002000 (XEN) gic_hyp_addr=f1004000 (XEN) gic_vcpu_addr=f1006000 (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 0001 booting - - Xen starting in Hyp mode - - Setting up control registers - - Turning on paging - - Ready - (XEN) CPU 1 booted. (XEN) Bringing up CPU2 - CPU 0002 booting - - Xen starting in Hyp mode - - Setting up control registers - - Turning on paging - - Ready - (XEN) CPU 2 booted. (XEN) Bringing up CPU3 - CPU 0003 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 @ 7200 (XEN) Allocating 1:1 mappings totalling 1024MB for dom0: (XEN) BANK[0] 0x004800-0x007000 (640MB) (XEN) BANK[1] 0x01d800-0x01f000 (384MB) (XEN) Grant table range: 0x007fc0-0x007fc64000 (XEN) Loading zImage from 7200 to 4fc0-4fe79fb8 (XEN) Allocating PPI 16 for event channel interrupt (XEN) Loading dom0 DTB to 0x5000-0x5000ab70 (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. Booting Linux on physical CPU 0x0 Linux version 3.19.8 (teltvm@teltvm2038x) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #23 Mon Nov 14 17:20:55 IST 2016 CPU: ARMv7 Processor [413fc0f2] revision 2 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Machine model: Lager Ignoring memory block 0x1d800 - 0x1f000 Truncating RAM at 0x4800-0x7000 to -0x6f00 Memory policy: Data cache writeback [ cut here ] WARNING: CPU: 0 PID: 0 at arch/arm/kernel/devtree.c:144 arm_dt_init_cpu_maps+0xc0/0x12c() DT /cpu 2 nodes greater than max cores 1, capping them CPU: 0 PID: 0
Re: [Xen-devel] Error regarding filesystem in Dom0 in lager board
Ok thanks for the reply, I have applied the dts file. My observations are: Adding hypervisor node has no effect on booting. For me even without hypervisor node it is getting booted up to mounting filesystem. After that point the system hangs as given in the log. Adding psci node results in breakdown of Xen. Xen gets crashed without booting linux DOM0. regards, George On Wed, Nov 16, 2016 at 11:38 PM, Iurii Mykhalskyi < iurii.mykhals...@globallogic.com> wrote: > Hi, > > Try to use attached files as DTS. I didn't tested, but looks like there > are few missed nodes: > - hypervisor > - psci > > I'm not sure, that Linux & Xen will correctly inter-works without them. > > With the best regards, > Iurii Mykhalskyi > > > > On Wed, Nov 16, 2016 at 7:23 PM, George John > wrote: > >> Hi, >> I just bumped in to some errors related to filesystem . The following is >> the log. I am using xen 4.7.1 along with linux kernel 3.19.8 as Dom0 >> >> Starting kernel ... >> >> - UART enabled - >> - CPU booting - >> - Xen starting in Hyp mode - >> - Zero BSS - >> - Setting up control registers - >> - Turning on paging - >> - Ready - >> (XEN) Checking for initrd in /chosen >> (XEN) RAM: 4000 - 7fff >> (XEN) RAM: 00014000 - 0001 >> (XEN) >> (XEN) MODULE[0]: 40ef2000 - 40efe000 Device Tree >> (XEN) MODULE[1]: 7200 - 722a0660 Kernel >> (XEN) MODULE[2]: 7400 - 7400284f XSM >> (XEN) RESVD[0]: 7ff9a000 - 7ff9a120 >> (XEN) RESVD[1]: 40ef2000 - 40efe000 >> (XEN) >> (XEN) Command line: console=dtuart dom0_mem=1G >> (XEN) Placing Xen at 0x7fc0-0x7fe0 >> (XEN) Update BOOTMOD_XEN from 9000-90105781 => >> 7fc0-7fd05781 >> (XEN) Xen heap: 0001f800-0002 (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 "serial0", options "38400n8" >> (XEN) WARNING: UART configuration is not supported >> Xen 4.7.1 >> (XEN) Xen version 4.7.1 (tel...@tvm.telxsi.com) (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: 1131:00011011 >> (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle >> (XEN) Extensions: GenericTimer Security >> (XEN) Debug Features: 02010555 >> (XEN) Auxiliary Features: >> (XEN) Memory Model Features: 10201105 4000 0124 02102211 >> (XEN) ISA Features: 02101110 13112111 21232041 2131 10011142 >> (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1 KHz >> (XEN) GICv2: WARNING: The GICC size is too small: 0x1000 expected 0x2000 >> (XEN) GICv2 initialization: >> (XEN) gic_dist_addr=f1001000 >> (XEN) gic_cpu_addr=f1002000 >> (XEN) gic_hyp_addr=f1004000 >> (XEN) gic_vcpu_addr=f1006000 >> (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 0001 booting - >> - Xen starting in Hyp mode - >> - Setting up control registers - >> - Turning on paging - >> - Ready - >> (XEN) CPU 1 booted. >> (XEN) Bringing up CPU2 >> - CPU 0002 booting - >> - Xen starting in Hyp mode - >> - Setting up control registers - >> - Turning on paging - >> - Ready - >> (XEN) CPU 2 booted. >> (XEN) Bringing up CPU3 >> - CPU 0003 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
Re: [Xen-devel] Error regarding filesystem in Dom0 in lager board
Hi, On Sat, Nov 19, 2016 at 3:06 AM, Julien Grall wrote: > > > On 16/11/2016 11:23, George John wrote: > >> Hi, >> > > Hello George, > > I just bumped in to some errors related to filesystem . The following is >> the log. I am using xen 4.7.1 along with linux kernel 3.19.8 as Dom0 >> > > [...] > > sh_mobile_sdhi sh_mobile_sdhi.0: mmc1 base at 0xee10 clock rate 97 MHz >> ata1: link resume succeeded after 1 retries >> ata1: SATA link down (SStatus 0 SControl 300) >> sh_mobile_sdhi sh_mobile_sdhi.2: mmc2 base at 0xee14 clock rate 48 MHz >> asoc-simple-card asoc-simple-card: ak4642-hifi <-> rcar_sound mapping ok >> input: gpio-keys as /devices/platform/gpio-keys/input/input0 >> �H�EXT4-fs (mmcblk0p1): error count since last fsck: 24 >> EXT4-fs (mmcblk0p1): initial error at time 11: mb_free_blocks:1450: >> inode 67523: block 296960 >> EXT4-fs (mmcblk0p1): last error at time 10: ext4_free_inode:340 >> > > It looks like the filesystem is corrupted. Have you tried to verify the > filesystem with fsck? > No, I haven't verified the filesystem. But the filesystem is working with no problems for native linux. Also Network file system( working with native linux) is not working when linux is running above xen. So I assumed it may be the problem with accessibility of hardware by linux when running above the hypervisor. > >> After this the system hangs >> > > Do you mean that even Xen is becoming inaccessible? > > You can try to switch to the Xen console by type 3-times "CTRL-a". You > should see a message from Xen telling you it has switched to Xen. If it > works, then only DOM0 is hanging. > Yes, I have tried that. Xen is also becoming inaccessible. Nothing works after the system hang. > > Regards, > > -- > Julien Grall > Regards, George ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Error regarding filesystem in Dom0 in lager board
Thank you all, what Andrii suggested was really the problem. I modified the uart driver in the kernel, so that it won't disable the port the xen was using(scif0). Now the linux Dom0 was booted up. But the new problem now occured was that filesystem getting stuck before login prompt. I assume it was the problem when the serial getty service tries to use the scif0 port the xen was using. Can any one suggest me a solution.?. I am attaching the log Thanks and regards, George On Mon, Nov 21, 2016 at 4:45 PM, Andrii Anisov wrote: > John, > > I guess you should remove descriptions of clocks and pins of a serial > port owned by XEN from the DTSI. > Normally kernel decides that they are not used, so disables them and > you think your system hangs. > I'm not really sure why you are reached this far (rootfs mounting), it > should be "hanged" earlier. But it could be you case. > > Sincerely, > Andrii Anisov. > > > On Sun, Nov 20, 2016 at 5:44 PM, George John > wrote: > > Hi, > > > > > > On Sat, Nov 19, 2016 at 3:06 AM, Julien Grall > wrote: > >> > >> > >> > >> On 16/11/2016 11:23, George John wrote: > >>> > >>> Hi, > >> > >> > >> Hello George, > >> > >>> I just bumped in to some errors related to filesystem . The following > is > >>> the log. I am using xen 4.7.1 along with linux kernel 3.19.8 as Dom0 > >> > >> > >> [...] > >> > >>> sh_mobile_sdhi sh_mobile_sdhi.0: mmc1 base at 0xee10 clock rate 97 > >>> MHz > >>> ata1: link resume succeeded after 1 retries > >>> ata1: SATA link down (SStatus 0 SControl 300) > >>> sh_mobile_sdhi sh_mobile_sdhi.2: mmc2 base at 0xee14 clock rate 48 > >>> MHz > >>> asoc-simple-card asoc-simple-card: ak4642-hifi <-> rcar_sound mapping > ok > >>> input: gpio-keys as /devices/platform/gpio-keys/input/input0 > >>> �H�EXT4-fs (mmcblk0p1): error count since last fsck: 24 > >>> EXT4-fs (mmcblk0p1): initial error at time 11: mb_free_blocks:1450: > >>> inode 67523: block 296960 > >>> EXT4-fs (mmcblk0p1): last error at time 10: ext4_free_inode:340 > >> > >> > >> It looks like the filesystem is corrupted. Have you tried to verify the > >> filesystem with fsck? > > > > > > No, I haven't verified the filesystem. But the filesystem is working > with no > > problems for native linux. Also Network file system( working with native > > linux) is not working when linux is running above xen. So I assumed it > may > > be the problem with accessibility of hardware by linux when running above > > the hypervisor. > > > >>> > >>> > >>> After this the system hangs > >> > >> > >> Do you mean that even Xen is becoming inaccessible? > >> > >> You can try to switch to the Xen console by type 3-times "CTRL-a". You > >> should see a message from Xen telling you it has switched to Xen. If it > >> works, then only DOM0 is hanging. > > > > > > Yes, I have tried that. Xen is also becoming inaccessible. Nothing works > > after the system hang. > > > >> > >> > >> Regards, > >> > >> -- > >> Julien Grall > > > > > > > > Regards, > > George > > > > > > ___ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > https://lists.xen.org/xen-devel > > > log_22-11-2016 Description: Binary data ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] prebuilt binaries for arm-cortex a15 dom0 modules for xen
Hi, I am a newbie working on xen. I have brought up Dom0 in lager board. I want to bring up Dom U in lager. I would like to know whether there are any prebuilt binaries for xen dom0 modules for arm cortex a15 . regards, George ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] Intel board support for xen
Hi all, I am a newbie in xen. I wish to know which all intel platforms support xen hypervisor?. Thanks and Regards, George ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] Xen on lager for DOMU
Hi all, I was able to bring up Dom0 in lager board by steps followed by charles. What could be the steps I could follow to bring up DomU in xen for lager board.?..How to bring xen-utils in the filesystem(yocto build) of Dom0 linux for configuring DomU. Regards, George ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Xen on lager for DOMU
Thank you all for the positive replies. I will try it out. Thanks and regards, George On Fri, Jan 27, 2017 at 2:11 PM, Iurii Mykhalskyi < iurii.mykhals...@globallogic.com> wrote: > Hi George, > > I didn't test official Renesas yocto layer for Lager board. > > But general approach to bring-up xen-tools in Dom0 rootfs are follow: > 1. clone meta-virtualization layer along with other layers > 2. Append xen-base package into default package list (e.g. > core-image-minimal or weston-image-minimal). > 3. In addition you need to add Xen specific options to Dom0 kernel config > (please refer to [1] as reference). > > After that please refer to Oleksandr mail about DomU start-up. > > [1] https://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs > > With the best regards, > Iurii > > > On Fri, Jan 27, 2017 at 9:46 AM, Oleksandr Andrushchenko < > andr2...@gmail.com> wrote: > >> On 01/26/2017 09:11 PM, Julien Grall wrote: >> >>> >>> >>> On 24/01/2017 13:05, George John wrote: >>> >>>> Hi all, >>>> >>> >>> Hello, >>> >>> >>> I was able to bring up Dom0 in lager board by steps followed by charles. >>>> What could be the steps I could follow to bring up DomU in xen for lager >>>> board.?.. >>>> >>> >>> You can give a look to: >>> - https://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs >>> - https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization >>> _Extensions#DomU_kernel_and_DTS >>> >>> Alternatively, you can find a distribution where the kernel has Xen >>> options enabled. >>> >> For testing and some development on ARM64 I use Ubuntu for DomU [2], [3] >> >>> It may be the case in Yocto, or you can look at centos (see [1]). >>> >>> How to bring xen-utils in the filesystem(yocto build) of Dom0 >>> >>>> linux for configuring DomU. >>>> >>> >>> I don't know much about Yocto. I have CCed Iurri who I think is using >>> Yocto. It might be able to help you here. >>> >>> Cheers, >>> >>> [1] https://blog.xenproject.org/2015/10/05/xen-in-centos-7-aarch64/ >>> >>> [2] https://github.com/xen-troops/manifests/wiki/DomU-Ubuntu-on-H3-M3 >> [3] https://help.ubuntu.com/community/Xen >> > > > > -- > > Iurii Mykhalskyi | Lead Software Engineer > GlobalLogic > P +38.044.492.9695x3664 M +38.096.311.5467 S mad-nemoi > www.globallogic.com > <http://www.globallogic.com/> > http://www.globallogic.com/email_disclaimer.txt > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Intel board support for xen
hi, Thanks for the reply. I want to bring up xen on an intel embedded development platform. I am going to buy one. Can you suggest a intel development platform for embedded applications on which xen could work? Thanks and regards, George On Friday, December 9, 2016, Konrad Rzeszutek Wilk wrote: > On Fri, Dec 09, 2016 at 06:40:07PM +0530, George John wrote: > > Hi all, > > > > I am a newbie in xen. I wish to know which all intel platforms support > xen > > hypervisor?. > > All the ones that can do 64-bit mode. > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Intel board support for xen
no, I meant some embedded platform like say for example minnowboard. Any other boards like minnowboard? thanks and regards, George On Mon, Dec 12, 2016 at 8:11 PM, Konrad Rzeszutek Wilk < konrad.w...@oracle.com> wrote: > On Mon, Dec 12, 2016 at 12:56:32PM +0530, George John wrote: > > hi, > > > > Thanks for the reply. I want to bring up xen on an intel embedded > > development platform. I am going to buy one. Can you suggest a intel > > development platform for embedded applications on which xen could work? > > Um, your laptop? You desktop? > > > > Thanks and regards, > > George > > > > > > On Friday, December 9, 2016, Konrad Rzeszutek Wilk < > konrad.w...@oracle.com> > > wrote: > > > > > On Fri, Dec 09, 2016 at 06:40:07PM +0530, George John wrote: > > > > Hi all, > > > > > > > > I am a newbie in xen. I wish to know which all intel platforms > support > > > xen > > > > hypervisor?. > > > > > > All the ones that can do 64-bit mode. > > > > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] Intel board support for xen
ok thank you very much On Tuesday, December 13, 2016, Konrad Rzeszutek Wilk wrote: > On Tue, Dec 13, 2016 at 10:58:53AM +0530, George John wrote: > > no, I meant some embedded platform like say for example minnowboard. Any > > other boards like minnowboard? > > Based n > https://ark.intel.com/products/78477/Intel-Atom- > Processor-E3826-1M-Cache-1_46-GHz > > It has 64-bit support so you are all good. > > > > thanks and regards, > > George > > > > On Mon, Dec 12, 2016 at 8:11 PM, Konrad Rzeszutek Wilk < > > konrad.w...@oracle.com > wrote: > > > > > On Mon, Dec 12, 2016 at 12:56:32PM +0530, George John wrote: > > > > hi, > > > > > > > > Thanks for the reply. I want to bring up xen on an intel embedded > > > > development platform. I am going to buy one. Can you suggest a intel > > > > development platform for embedded applications on which xen could > work? > > > > > > Um, your laptop? You desktop? > > > > > > > > Thanks and regards, > > > > George > > > > > > > > > > > > On Friday, December 9, 2016, Konrad Rzeszutek Wilk < > > > konrad.w...@oracle.com > > > > > wrote: > > > > > > > > > On Fri, Dec 09, 2016 at 06:40:07PM +0530, George John wrote: > > > > > > Hi all, > > > > > > > > > > > > I am a newbie in xen. I wish to know which all intel platforms > > > support > > > > > xen > > > > > > hypervisor?. > > > > > > > > > > All the ones that can do 64-bit mode. > > > > > > > > > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] help regarding intel board
hi, Can anybody give a list of intel based boards for automotive embedded use case in which xen could be installed?. regards, George ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[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: 0x70f0 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: 0x7200 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: 0x7400 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: 9000 Entry Point: 9000 ## Flattened Device Tree blob at 70f0 Booting using the fdt blob at 0x70f0 Loading Kernel Image ... OK Loading Device Tree to 40ef2000, end 40efff95 ... OK Starting kernel ... - UART enabled - - CPU booting - - Xen starting in Hyp mode - - Zero BSS - - Setting up control registers - - Turning on paging - - Ready - (XEN) Checking for initrd in /chosen (XEN) RAM: 4000 - 7fff (XEN) RAM: 00014000 - 0001 (XEN) (XEN) MODULE[0]: 40ef2000 - 40efd000 Device Tree (XEN) MODULE[1]: 7200 - 7227f628 Kernel (XEN) MODULE[2]: 7400 - 740026b2 XSM (XEN) RESVD[0]: 7ff9a000 - 7ff9a120 (XEN) RESVD[1]: 40ef2000 - 40efd000 (XEN) (XEN) Command line: console=dtuart dom0_mem=1G (XEN) Placing Xen at 0x7fc0-0x7fe0 (XEN) Update BOOTMOD_XEN from 9000-90105781 => 7fc0-7fd05781 (XEN) Xen heap: 0001f800-0002 (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@e6e6", 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: 1131:00011011 (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle (XEN) Extensions: GenericTimer Security (XEN) Debug Features: 02010555 (XEN) Auxiliary Features: (XEN) Memory Model Features: 10201105 4000 0124 02102211 (XEN) ISA Features: 02101110 13112111 21232041 2131 10011142 (XEN) Generic Timer IRQ: phys=30 hyp=2
