On 28.01.20 22:50, Saroj Sapkota wrote:
I'm trying to run jailhouse on Jetson tx2 kit. I downloaded the
jailhouse and compiled it and run the command
=>sudo insmod Downloads/linux-jailhouse-jetson/driver/jailhouse.ko
// there is no error message in terminal console
but it gives following output on the serial console:
tx2@tx2-desktop:~$ [ 129.954491] jailhouse: loading out-of-tree module
taints kernel.
After this I tried to enable jailhouse through this command
=>sudo jailhouse enable Downloads/linux-jetson/configs/arm64/jetson-tx2.cell
// terminal displays: JAILHOUSE_ENABLE: Invalid argument
//and on the terminal console it displays:
[ 333.421533] jailhouse: mem_region_request failed for hypervisor
memory mem_region_request failed for hypervisor memory
mem_region_request failed for hypervisor memory mem_region_request
failed for hypervisor memory.
[ 333.428303] jailhouse: Did you reserve the memory with "memmap=" or
"mem="?
I have changed /boot/extlinux/extlinux.conf file as follows:
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet
**mem=7808M vmalloc=512M**
# When testing a custom kernel, it is recommended that you create a
backup of
# the original kernel and add a new entry to this file so that the
device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
# LABEL backup
# MENU LABEL backup kernel
# LINUX /boot/Image.backup
# INITRD /boot/initrd
# APPEND ${cbootargs}*
*
*
*
but this change is not working. So what's the wrong in this
extlinux.conf file as boot up is ignoring *mem=7808M vmalloc=512M *this
statement.*
*
So, /proc/cmdline of the booted system is not containing your change?
Then I would say your system is using a different boot configuration
mechanism. Where did you get the image from? Is U-Boot involved in the
boot-up? What does "printenv" report about how the boot is configured?
Maybe you need to adjust the command line in the environment instead.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/6e69283d-90dd-4579-7640-c5d585a2a9ad%40siemens.com.
