Re: [Xen-devel] Regarding changing memory for DOM0

[Stefano Stabellini]

On Wed, 30 Aug 2017, George John wrote:
> 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

This is usually due to a mismatch of the version of the hypervisor and the 
version of the tools.


> 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 changing memory for DOM0

[George John]

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 changing memory for DOM0

[Andrii Anisov]

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 changing memory for DOM0

[Julien Grall]

On 11/08/17 09:55, Andrii Anisov wrote:

Hello George,


Hello,



On 11.08.17 10:16, George John wrote:

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.

I've looked through the log and it is the same as on my table. Yes,
nfs-root can not be mounted with this configuration. With root on MMC
this setup will work.
This issue should be debugged, but I have my hands full so can not do it
now.

The only thing I see from this point that this setup has less memory
under 4GB (640MB vs 752MB). Theoretically lack of DMA-able RAM can lead
to network malfunction.
So the question is if it's a real cause, and why XEN does not allocate
whole under-4GB RAM to dom0.


The kernel should really be able to deal with memory below and above 
4GB. 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.


Cheers,

--
Julien Grall

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

Re: [Xen-devel] Regarding changing memory for DOM0

[Andrii Anisov]

Hello George,


On 11.08.17 10:16, George John wrote:
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.
I've looked through the log and it is the same as on my table. Yes, 
nfs-root can not be mounted with this configuration. With root on MMC 
this setup will work.
This issue should be debugged, but I have my hands full so can not do it 
now.


The only thing I see from this point that this setup has less memory 
under 4GB (640MB vs 752MB). Theoretically lack of DMA-able RAM can lead 
to network malfunction.
So the question is if it's a real cause, and why XEN does not allocate 
whole under-4GB RAM to dom0.


--

*Andrii Anisov*

*
*


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

Re: [Xen-devel] Regarding changing memory for DOM0

[George John]

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: #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #
 #

Re: [Xen-devel] Regarding changing memory for DOM0

[Andrii Anisov]

On 03.08.17 16:58, Andrii Anisov wrote:

Let me check with a block device root.

It does work with root on mmcblk1p1.

So I suggest to George to update his XEN by moving to 4.9 or by 
backporting mentioned patch.


Not sure what is broken for nfs-root. Would not deal with it now, maybe 
later.


--

*Andrii Anisov*


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

Re: [Xen-devel] Regarding changing memory for DOM0

[Andrii Anisov]

On 03.08.17 16:49, Julien Grall wrote:
Looking at the log, there is 640MB of RAM allocated below 4GB. So is 
it the same issue?

I do not know what the issue George exactly has. I do not see his log.
Let me check with a block device root.


Also, which version of Xen are you comparing with?

I'm not comparing, just checked on my table with my current setup.

--

*Andrii Anisov*



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

Re: [Xen-devel] Regarding changing memory for DOM0

[Julien Grall]

On 03/08/17 14:46, Andrii Anisov wrote:


On 03.08.17 16:38, Andrii Anisov wrote:

If I recall correctly related issue was fixed in 4.9.


It's ugly.
I've reproduced the setup on my table, with the current master. It does
not work.
XEN allocated Dom0 memory properly:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 7a00
(XEN) Allocating 1:1 mappings totalling 2048MB for dom0:
(XEN) BANK[0] 0x005000-0x007800 (640MB)
(XEN) BANK[1] 0x06-0x064000 (1024MB)
(XEN) BANK[2] 0x071800-0x073000 (384MB)
(XEN) Grant table range: 0x073fe0-0x073fe64000
(XEN) Loading zImage from 7a00 to
5008-5208
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x5800-0x5800fd09
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.

But my nfs-root is not mounted :(


Looking at the log, there is 640MB of RAM allocated below 4GB. So is it 
the same issue?


Also, which version of Xen are you comparing with?

Cheers,

--
Julien Grall

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

Re: [Xen-devel] Regarding changing memory for DOM0

[Andrii Anisov]

On 03.08.17 16:38, Andrii Anisov wrote:

If I recall correctly related issue was fixed in 4.9.


It's ugly.
I've reproduced the setup on my table, with the current master. It does 
not work.

XEN allocated Dom0 memory properly:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 7a00
(XEN) Allocating 1:1 mappings totalling 2048MB for dom0:
(XEN) BANK[0] 0x005000-0x007800 (640MB)
(XEN) BANK[1] 0x06-0x064000 (1024MB)
(XEN) BANK[2] 0x071800-0x073000 (384MB)
(XEN) Grant table range: 0x073fe0-0x073fe64000
(XEN) Loading zImage from 7a00 to 
5008-5208

(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x5800-0x5800fd09
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.

But my nfs-root is not mounted :(


--

*Andrii Anisov*



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

Re: [Xen-devel] Regarding changing memory for DOM0

[Julien Grall]

On 03/08/17 14:38, Andrii Anisov wrote:

Hello Julien, George


On 03.08.17 16:11, Julien Grall wrote:

... I am not sure to understand the relation between the file system
crashing and the amount of RAM. Having the full log here would be
helpful. Is it because all the memory allocated is above 4GB?

Yep, the salvator-x board has 1GB RAM under 4GB mark and the rest 3GB
above.
Moreover 128MB from the RAM below 4GB mark are taken for secure world.

If I recall correctly related issue was fixed in 4.9.


I guess you refer to commit ab5b00ab49 "xen/arm: domain_build: allocate 
lowmem for dom0 as much as possible". We can consider to backport it to 
Xen 4.8 and Xen 4.7.


Cheers,

--
Julien Grall

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

Re: [Xen-devel] Regarding changing memory for DOM0

[Andrii Anisov]

Hello Julien, George


On 03.08.17 16:11, Julien Grall wrote:
... I am not sure to understand the relation between the file system 
crashing and the amount of RAM. Having the full log here would be 
helpful. Is it because all the memory allocated is above 4GB?
Yep, the salvator-x board has 1GB RAM under 4GB mark and the rest 3GB 
above.

Moreover 128MB from the RAM below 4GB mark are taken for secure world.

If I recall correctly related issue was fixed in 4.9.

--

*Andrii Anisov*



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

Re: [Xen-devel] Regarding changing memory for DOM0

[Julien Grall]

On 03/08/17 09:57, George John wrote:

Hi,


Hello,


 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.


This was already reported few days ago. Please see:

https://lists.xenproject.org/archives/html/xen-devel/2017-07/msg01461.html

However...


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


... I am not sure to understand the relation between the file system 
crashing and the amount of RAM. Having the full log here would be 
helpful. Is it because all the memory allocated is above 4GB?



xen version is 4.8.0


Do you have any requirement to use 4.8? If so, you should at least use 
the latest 4.8 version (i.e 4.8.1). If not, I would recommend to move to 
xen 4.9 if not unstable.


Also, what is your Linux version?

Cheers,

--
Julien Grall

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

[Xen-devel] Regarding changing memory for DOM0

[George John]

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