About bootburn -l option in DrivePX2
Is there a way to install Linux directly on the hardware without hypervisor on DrivePX2? Will "bootburn -l" do that? Also, is there a document that gives little insight about Vibrante Hypervisor? I could find little information from http://docs.nvidia.com/drive/nvvib_docs/index.html#page/NVIDIA%2520Vibrante%2520Linux%2520DPX%2520Development%2520Guide%2Ftheory_of_operation_dpx.html%23wwpID0ELHA but it does not provide much insight. Will be interested to know the performance difference with or without hypervisor etc. Thanks Anup
Is there a way to install Linux directly on the hardware without hypervisor on DrivePX2? Will "bootburn -l" do that?

Also, is there a document that gives little insight about Vibrante Hypervisor? I could find little information from http://docs.nvidia.com/drive/nvvib_docs/index.html#page/NVIDIA%2520Vibrante%2520Linux%2520DPX%2520Development%2520Guide%2Ftheory_of_operation_dpx.html%23wwpID0ELHA but it does not provide much insight. Will be interested to know the performance difference with or without hypervisor etc.

Thanks
Anup

#1
Posted 11/30/2017 09:55 PM   
Dear anup.pemmaiah, There’s a bit more clear description of the flashing commands here. Thanks. http://docs.nvidia.com/drive/nvvib_docs/index.html#page/NVIDIA%2520Vibrante%2520Linux%2520DPX%2520Development%2520Guide%2FAppendix%2FQSG_lnx_SU.html%23wwpID0E0OB0HA
Dear anup.pemmaiah,

There’s a bit more clear description of the flashing commands here. Thanks.
http://docs.nvidia.com/drive/nvvib_docs/index.html#page/NVIDIA%2520Vibrante%2520Linux%2520DPX%2520Development%2520Guide%2FAppendix%2FQSG_lnx_SU.html%23wwpID0E0OB0HA

#2
Posted 12/04/2017 12:17 AM   
Hi SteveNV, Thank you for the link. I have been following the info in the link for all my work, but it does not provide detailed answer for my questions. I had read in some link that Vibrante Hypervisor can be run as a Level-1 hypervisor (Just the hypervisor on the bare metal without any OS and the guest OS's can then be loaded on them) or as part of Linux(which I assume something similar to Qemu/KVM). Not sure if that article gave the correct information about the Vibrante Hypervisor. Therefore, I wanted to get more information about the hypervisor. Thanks Anup
Hi SteveNV,

Thank you for the link. I have been following the info in the link for all my work, but it does not provide detailed answer for my questions. I had read in some link that Vibrante Hypervisor can be run as a Level-1 hypervisor (Just the hypervisor on the bare metal without any OS and the guest OS's can then be loaded on them) or as part of Linux(which I assume something similar to Qemu/KVM). Not sure if that article gave the correct information about the Vibrante Hypervisor. Therefore, I wanted to get more information about the hypervisor.

Thanks
Anup

#3
Posted 12/04/2017 07:56 PM   
Dear anup.pemmaiah, The bootburn -l option will flash Linux without HV. The Foundation document give more information about Virtualization. http://docs.nvidia.com/drive/nvfdn_docs/index.html#page/NVIDIA%2520Vibrante%2520Foundation%2520Development%2520Guide%2FGetting%2520Started%2Fhypervisor_use.html%23
Dear anup.pemmaiah,

The bootburn -l option will flash Linux without HV.
The Foundation document give more information about Virtualization.
http://docs.nvidia.com/drive/nvfdn_docs/index.html#page/NVIDIA%2520Vibrante%2520Foundation%2520Development%2520Guide%2FGetting%2520Started%2Fhypervisor_use.html%23

#4
Posted 12/07/2017 10:04 AM   
Thank you SteveNV. That helps. I have another question about flashing. I see on a DrivePX2 system there are two directories under /lib/modules $ ls /lib/modules/ 4.4.38-rt49-tegra 4.4.38-tegra While flashing with "./bootburn.sh -b p2379c01-t186b -l", looks like it is taking by default quickboot_qspi_rt_linux.cfg file and flashing into real time linux kernel. Since I see non-rt (4.4.38-tegra) in /lib/modules, is there way to reboot without flashing into non-rt(4.4.38-tegra) kernel or should I reflash the board with "./bootburn.sh -b p2379c01-t186b -l -k quickboot_qspi_linux_intramfs.cfg" to boot into non-rt image? Thanks Anup
Thank you SteveNV. That helps. I have another question about flashing.

I see on a DrivePX2 system there are two directories under /lib/modules
$ ls /lib/modules/
4.4.38-rt49-tegra 4.4.38-tegra

While flashing with "./bootburn.sh -b p2379c01-t186b -l", looks like it is taking by default quickboot_qspi_rt_linux.cfg file and flashing into real time linux kernel. Since I see non-rt (4.4.38-tegra) in /lib/modules, is there way to reboot without flashing into non-rt(4.4.38-tegra) kernel or should I reflash the board with "./bootburn.sh -b p2379c01-t186b -l -k quickboot_qspi_linux_intramfs.cfg" to boot into non-rt image?

Thanks
Anup

#5
Posted 12/13/2017 12:37 AM   
Scroll To Top

Add Reply