I am using petalinux and vivado 2016.04 and microzed 7010 board for my project.
I have followed the steps =>I have set board in QSPI mode by jumpers. I have TFTPed the imaged.ub on board (run netboot)and mounted the roofs from my PC by NFS.
For this, when NFS is configed in petalinux-config, I had to disable initramfs in kernel config manually.
If I don't disable initramfs in kernel(petalinux-config -c kernel ) but NFS is configured (petalinux-config), rootfs is being mounted from QSPI.
I am beginer to petalinux sdk and microzed board. What is the reson makes it mount rootfs from QSPI even if I configured nfs but did not disable initramfs in kernel and my bootargs is
INPUTS :
1 . "bootargs=console=ttyPS0,115200 earlyprintk root=/dev/nfs nfsroot=172.16.9.187:/tftpboot/nfsroot,tcp,v4 ip=172.16.9.25 rw"
manualy i cross-verified the mounting of rootfs by NFS from PC to board.
2 . "mount -o nolock -t nfs ip_addr:/tftpboot/nfsroot /home/root/"
Any help will be appreciated. Thanks in advance.
Regards,
Pritam
I have got an useful links for this.
https://landley.net/writing/rootfs-intro.html
https://landley.net/writing/rootfs-howto.html
Related
I'm a neewbie to embedded linux.
I was trying to compile the kernel(debian 10.3) manually from the uboot on beaglebone balck but even though i have passed the correct root file directory, it get stuck on "waiting for root device /dev/mmcblk1p1 .
When I was trying to boot the BBB from uboot with the following commands
setenv bootargs console tyyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait
load mmc 1:1 0x82000000 /boot/vmlinuz-4.19.94+ti-r42
load mmc 1:1 0x88000000 /boot/dtbs/4.19.94+ti-r42/am335x-boneblack-uboot-univ.dtb
Uboot commands(emmc)
I get this
result
But when i flash an sd card with the same image file
and execute the same commands( with different partitions and all) in the uboot uboot commands(sd card)
I'm able to compile the kernel
The partitions on the emmc-
partitions on eMMC
I'm using the buildroot version-20011.02 for kernel, toolchain and filesystem.My customized board ARMV7 cortexA9 SoC.Kernel version is 3.18.41.
Build the kernel(uImage), Buildroot toolchain, rootfs.tar.gz.
Enable the filesystem tyep ext4 in buildroot and also in kernel.
Extracting this rootfs.tar.gz to /export/users/buildroot/.
exporting this directory by using
exportfs -a, exportfs -rv and restart the nfs server.It seems everything is fine on nfs server side.
Here I'm sharing the "make menuconfig" system configuration -->
Init system (BusyBox) --->
Even I tried with Init system (systemV) --->
with bootargs as bootargs console=ttyAM0,115200n8 root=/dev/nfs rw rootwait ip=dhcp nfsroot=192.168.1.40:/export/users/buildroot,tcp,v3 init=/sbin/init
Every time I'm getting below log:
VFS: mounted fs via nfs
devtmpfs is mounted.
Kernel panic - not syncing:Attempted to kill init, exit code=0x000000b
Please help me out how to resolve this issue.
This may help you.
As you said, there is a log like below.
Kernel panic - not syncing:Attempted to kill init, exit code=0x000000b
This means init(busybox) is exited and the exit code is 0xb.
So kernel goes into panic.
Maybe this is caused by a network problem. But we cannot conclude this is due to network or not, for now.
You said, you saw crashing, without NFS.
I think resolving that crash maybe better way to solve this situation.
Please share crash log without NFS configuration. If you share log, I will check it.
Is it possible to trace guest OS execution (break/watchpoints, single-stepping) when kvm is used and cpu is set to host?
If I run qemu with
qemu-system-x86_64 -no-kvm -cpu core2duo -m 256 -cdrom kernel.iso -s -S
target remote :1234 //on gdb commande line
tracing goes fine but when I run using
qemu-system-x86_64 -enable-kvm -cpu host -m 256 -cdrom kernel.iso
no breakpoint works (guest never stops) so my question. If yes, can someone point me the right config?
I do need kvm to expose PMU features to the guest.
*PMU : Performance Monitoring Unit
Ok, I figured out what i was missing.
With kvm enabled and cpu set to host, use hardware breakpoint instead of software breakpoint.
The only problem is that our budget in hardware breakpoint is limited
What you want to do is called: Virtual Machine Introspection (VMI).
Take a look at these two papers:
Virtual machine introspection: Techniques and applications
A Survey on Hypervisor Based Monitoring: Approaches, Applications, and Evolutions
I get a new kernel(3.14) from kontron for my board after i compiled and try to run it on my board but i getting the following error any one can help me !
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
The kernel can't find its root filesystem.
Investigate why that is the case. Where is the kernel looking for it? Check the kernel config and/or the command line passed from the bootloader. Check that the kernel has all the drivers to actually access the hardware hosting the root filesystem. Has the kernel the needed filesystem support complied in?
I have an Amazon EC2 instance. I booted up a volume and attached it to /dev/sdj. I edited my fstab file to have the line
/dev/sdj /home/ec2-user/mydirectory xfs noatime 0 0
Then I mounted it (sudo mount /home/ec2-user/mydirectory)
However, running the "mount" command says the following:
/dev/xvdj on /home/ec2-user/mydirectory type xfs (rw,noatime)
What? Why is it /dev/xvdj instead of /dev/sdj?
The devices are named /dev/xvdX rather than sdX in 11.04. This was a kernel change. The kernel name for xen block devices is 'xvd'. Previously Ubuntu carried a patch to rename those devices as sdX. That patch became problematic.
https://askubuntu.com/a/47909