topic Re: QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) in QorIQ

topic Re: QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) in QorIQ https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386112#M1567 <HTML><HEAD></HEAD><BODY><P>Also when I tried as below</P><P>sudo ~/QorIQ-SDK-V1.6-20140619-yocto/build_t1040rdb_release/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-ppc64 -kernel uImage  -net nic,model=e1000 -net tap,ifname=tap0,script=no,downscript=no -cpu e5500 -M ppce500 <STRONG>-initrd fsl-image-core-t1040rdb.ext2.gz</STRONG> -no-reboot -show-cursor -no-reboot -m 384 --append "root=/dev/ram console=ttyS0 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=256M <STRONG>ramdisk_size=700000</STRONG>" -nographic -serial tcp::4444,server,telnet QEMU 1.7.0 monitor - type 'help' for more information</P><P></P><P>Boot output for the same is given below</P><P>RAMDISK: gzip image found at block 0</P><P>swapper/0 invoked oom-killer: gfp_mask=0x10200d0, order=0, oom_score_adj=0</P><P>CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.6+gc29fe1a #1</P><P>Call Trace:</P><P>[ce033a60] [c0006f50] show_stack+0x40/0x150 (unreliable)</P><P>[ce033aa0] [c0694d2c] dump_stack+0x78/0xa0</P><P>[ce033ab0] [c0693a3c] dump_header.isra.11+0x54/0x160</P><P>[ce033af0] [c00b3d80] out_of_memory+0x290/0x2a0</P><P>[ce033b30] [c00b80a8] __alloc_pages_nodemask+0x6c8/0x720</P><P>[ce033be0] [c00b0be4] grab_cache_page_write_begin+0x74/0xe0</P><P>[ce033c10] [c012b9cc] block_write_begin+0x3c/0xa0</P><P>[ce033c30] [c00b0574] generic_file_buffered_write+0x194/0x270</P><P>[ce033cb0] [c00b2050] __generic_file_aio_write+0x1d0/0x480</P><P>[ce033d10] [c01315a0] blkdev_aio_write+0x70/0xc0</P><P>[ce033d50] [c00f6e50] do_sync_write+0x70/0xd0</P><P>[ce033db0] [c00f77c8] vfs_write+0xc8/0x1e0</P><P>[ce033dd0] [c00f7ecc] SyS_write+0x4c/0xc0</P><P>[ce033e00] [c0862380] compr_flush+0x30/0x78</P><P>[ce033e10] [c0879124] gunzip+0x2b4/0x36c</P><P>[ce033e50] [c08626e8] rd_load_image+0x320/0x5e8</P><P>[ce033ea0] [c0862ac8] initrd_load+0x50/0x2dc</P><P>[ce033ed0] [c08620a4] prepare_namespace+0xe0/0x1d0</P><P>[ce033ef0] [c0861958] kernel_init_freeable+0x1bc/0x1d0</P><P>[ce033f20] [c0002808] kernel_init+0x18/0x170</P><P>[ce033f40] [c000fce0] ret_from_kernel_thread+0x5c/0x64</P><P>Mem-Info:</P><P>DMA per-cpu:</P><P>CPU    0: hi:   42, btch: 7 usd:   6</P><P>active_anon:0 inactive_anon:0 isolated_anon:0</P><P> active_file:0 inactive_file:0 isolated_file:0</P><P> unevictable:11906 dirty:7 writeback:0 unstable:0</P><P> free:494 slab_reclaimable:205 slab_unreclaimable:436</P><P> mapped:0 shmem:0 pagetables:0 bounce:0</P><P> free_cma:0</P><P>DMA free:1976kB min:2000kB low:2500kB high:3000kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:47624kB isolated(anon):0kB isolated(file):0kB present:262144kB managed:250064kB mlocked:0kB dirty:28kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:820kB slab_unreclaimable:1744kB kernel_stack:224kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes</P><P>lowmem_reserve[]: 0 0 0 0</P><P>DMA: 0*4kB 1*8kB (R) 1*16kB (R) 1*32kB (R) 0*64kB 1*128kB (R) 1*256kB (R) 1*512kB (R) 1*1024kB (R) 0*2048kB 0*4096kB 0*8192kB 0*16384kB = 1976kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1024kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=4096kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=16384kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=65536kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=262144kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB</P><P>11915 total pagecache pages</P><P>0 pages in swap cache</P><P>Swap cache stats: add 0, delete 0, find 0/0</P><P>Free swap  = 0kB</P><P>Total swap = 0kB</P><P>65536 pages RAM</P><P>0 pages HighMem/MovableOnly</P><P>3020 pages reserved</P><P>[ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name</P><P>Kernel panic - not syncing: Out of memory and no killable processes...</P><P></P><P>I have tried even with ramdisk_size= 307200 but similar output we get at boot time. I am looking for an option through which I can make QEMU to use hard drive as boot device and not RAMFS as the application we want to test will require storage and it should not go into RAM as it will bloat at sometime.</P><P></P><P>Please let me know if you need more information.</P><P></P><P>Thanks,</P><P>Abhinav</P></BODY></HTML> Tue, 06 Jan 2015 10:36:02 GMT abhinavbipnesh 2015-01-06T10:36:02Z QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386109#M1564 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>While trying to start the QEMU emulation using qemu-system-ppc64 I am getting error as below from the boot log</P><P></P><P>. . . .</P><P>Trying to unpack rootfs image as initramfs...</P><P>rootfs image is not initramfs (no cpio magic); looks like an initrd</P><P>Freeing initrd memory: 81324K (c3000000 - c7f6b000)</P><P>audit: initializing netlink socket (disabled)</P><P>type=2000 audit(0.592:1): initialized</P><P>HugeTLB registered 1 MB page size, pre-allocated 0 pages</P><P>HugeTLB registered 4 MB page size, pre-allocated 0 pages</P><P>HugeTLB registered 16 MB page size, pre-allocated 0 pages</P><P>HugeTLB registered 64 MB page size, pre-allocated 0 pages</P><P>HugeTLB registered 256 MB page size, pre-allocated 0 pages</P><P>HugeTLB registered 1 GB page size, pre-allocated 0 pages</P><P>. . .</P><P>RAMDISK: gzip image found at block 0</P><P>RAMDISK: incomplete write (22321 != 32768)</P><P>write error</P><P>VFS: Mounted root (ext2 filesystem) on device 1:0.</P><P>devtmpfs: mounted</P><P>Freeing unused kernel memory: 288K (c08a4000 - c08ec000)</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=454704, limit=262144</P><P>Buffer I/O error on device ram0, logical block 227351</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=455366, limit=262144</P><P>Buffer I/O error on device ram0, logical block 227682</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=463142, limit=262144</P><P>Buffer I/O error on device ram0, logical block 231570</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=454704, limit=262144</P><P>Buffer I/O error on device ram0, logical block 227351</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=455366, limit=262144</P><P>Buffer I/O error on device ram0, logical block 227682</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=463142, limit=262144</P><P>Buffer I/O error on device ram0, logical block 231570</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=418868, limit=262144</P><P>Buffer I/O error on device ram0, logical block 209433</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=424160, limit=262144</P><P>Buffer I/O error on device ram0, logical block 212079</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=427966, limit=262144</P><P>Buffer I/O error on device ram0, logical block 213982</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=418868, limit=262144</P><P>Buffer I/O error on device ram0, logical block 209433</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=424160, limit=262144</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=427966, limit=262144</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=418868, limit=262144</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=424160, limit=262144</P><P>attempt to access beyond end of device</P><P>ram0: rw=0, want=427966, limit=262144</P><P>Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.</P><P>CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.6+gc29fe1a #2</P><P>Call Trace:</P><P>[ce033e80] [c0007190] show_stack+0x40/0x150 (unreliable)</P><P>[ce033ec0] [c06cc978] dump_stack+0x78/0xa0</P><P>[ce033ed0] [c06cacb8] panic+0xd8/0x1fc</P><P>[ce033f20] [c0002b9c] kernel_init+0x16c/0x170</P><P>[ce033f40] [c000ff20] ret_from_kernel_thread+0x5c/0x64</P><P>Rebooting in 180 seconds..Connection closed by foreign host.</P><P></P><P>The command which I fired for bring up the machine is given below</P><P><STRONG>sudo ~/QorIQ-SDK-V1.6-20140619-yocto/build_t1040rdb_release/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-ppc64 -kernel uImage  -net nic,model=e1000 -net tap,ifname=tap0,script=no,downscript=no -cpu e5500 -M ppce500 <SPAN style="color: #ffff00;">-initrd fsl-image-virt-t1040rdb-20150105132202.rootfs.ext2.gz</SPAN> -no-reboot -show-cursor -no-reboot -m 256 --append "root=/dev/ram rw console=ttyS0,115200 ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=256M " -serial tcp::4444,server,telnet -drive file=mydisk,cache=none,if=virtio -nographic</STRONG></P><P></P><P>Now when we try to pass -hda option for below command</P><P> sudo ~/QorIQ-SDK-V1.6-20140619-yocto/build_t1040rdb_release/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-ppc64 -kernel uImage  -net nic,model=e1000 -net tap,ifname=tap0,script=no,downscript=no -cpu e5500 -M ppce500 <STRONG>-hda fsl-image-virt-t1040rdb-20150105132202.rootfs.ext2.gz</STRONG> -no-reboot -show-cursor -no-reboot -m 256 --append "root=/dev/hda rw console=ttyS0,115200 ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=256M " -serial tcp::4444,server,telnet -drive file=mydisk,cache=none,if=virtio -nographic</P><P></P><P>The error being reported is given below</P><P>VFS: Cannot open root device "hda" or unknown-block(0,0): error -6</P><P>Please append a correct "root=" boot option; here are the available partitions:</P><P>fe00         1048576 vda  driver: virtio_blk</P><P>  fe01         1047552 vda1 0f1cd4fc-01</P><P>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)</P><P>CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.6+gc29fe1a #2</P><P>Call Trace:</P><P>[ce03bda0] [c0007190] show_stack+0x40/0x150 (unreliable)</P><P>[ce03bde0] [c06cc978] dump_stack+0x78/0xa0</P><P>[ce03bdf0] [c06cacb8] panic+0xd8/0x1fc</P><P>[ce03be40] [c08a4ce4] mount_block_root+0x1b0/0x248</P><P>[ce03bea0] [c08a4fb0] mount_root+0xfc/0x110</P><P>[ce03bed0] [c08a514c] prepare_namespace+0x188/0x1d0</P><P>[ce03bef0] [c08a4958] kernel_init_freeable+0x1bc/0x1d0</P><P>[ce03bf20] [c0002a48] kernel_init+0x18/0x170</P><P>[ce03bf40] [c000ff20] ret_from_kernel_thread+0x5c/0x64</P><P>Rebooting in 180 seconds..Connection closed by foreign host.</P><P></P><P>So any thoughts how to make system boot using a -hda and not using -initrd as we want to have IMAGE_ROOT_FS=1G so that we can have some space for working with application and other dependent library.</P><P></P><P>Please let me know if you need more information.</P><P></P><P>Thanks,</P><P>Abhinav</P></BODY></HTML> Mon, 05 Jan 2015 13:40:41 GMT https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386109#M1564 abhinavbipnesh 2015-01-05T13:40:41Z Re: QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386110#M1565 <HTML><HEAD></HEAD><BODY><P>Hello <SPAN class="replyToName">Abhinav Bipnesh,</SPAN></P><P></P><P>For ramdisk boot, please specify "ramdisk_size=700000" in bootargs, and check whether using "fsl-image-minimal-t1040rdb.ext2.gz.u-boot" would be better.</P><P></P><P>For harddisk boot, please specify the exact harddisk block, for example --append "root=/dev/sda1 rw console=ttyS0,115200", please try whether it could work without specifying -hda.</P><P><STRONG><BR /></STRONG></P><P>Thanks,</P><P>Yiping</P></BODY></HTML> Tue, 06 Jan 2015 09:20:31 GMT https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386110#M1565 yipingwang 2015-01-06T09:20:31Z Re: QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386111#M1566 <HTML><HEAD></HEAD><BODY><P>Hi Yiping,</P><P></P><P>I have tried as suggested below are the output of the same</P><P></P><P>sudo ~/QorIQ-SDK-V1.6-20140619-yocto/build_t1040rdb_release/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-ppc64 -kernel uImage  -net nic,model=e1000 -net tap,ifname=tap0,script=no,downscript=no -cpu e5500 -M ppce500  <STRONG>fsl-image-core-t1040rdb-20150106083454.rootfs.ext2.gz</STRONG> -no-reboot -show-cursor -no-reboot -m 384 --append "root=/dev/sda1 console=ttyS0 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=256M " -nographic -serial tcp::4444,server,telnet</P><P></P><P>Boot output:</P><P><STRONG>VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6</STRONG></P><P><STRONG>Please append a correct "root=" boot option; here are the available partitions:</STRONG></P><P><STRONG>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)</STRONG></P><P><STRONG>CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.6+gc29fe1a #1</STRONG></P><P><STRONG> </STRONG></P><P>Using ramdisk_size option:</P><P>sudo ~/QorIQ-SDK-V1.6-20140619-yocto/build_t1040rdb_release/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-ppc64 -kernel uImage  -net nic,model=e1000 -net tap,ifname=tap0,script=no,downscript=no -cpu e5500 -M ppce500 <STRONG>fsl-image-core-t1040rdb-20150106083454.rootfs.ext2.gz.u-boot</STRONG> -no-reboot -show-cursor -no-reboot -m 384 --append "root=/dev/ram console=ttyS0 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=256M <STRONG>ramdisk_size=700000</STRONG>" -nographic -serial tcp::4444,server,telnet</P><P><STRONG>Boot output:</STRONG></P><P><STRONG>List of all partitions:</STRONG></P><P><STRONG>No filesystem could mount root, tried:  ext3 ext2 cramfs vfat ntfs</STRONG></P><P><STRONG>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)</STRONG></P><P><STRONG>CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.6+gc29fe1a #1</STRONG></P><P><STRONG><BR /></STRONG></P><P>So it seems the root file system are not properly created as it didn't identify sda1 or hda etc as I have tried such option. I have used below command for building up the things</P><P>$bitbake fsl-image-core</P><P></P><P>and below are the local.conf contains extra configuration</P><P>IMAGE_INSTALL_append += "boost-dev util-linux curl"</P><P>CORE_IMAGE_EXTRA_INSTALL += "boost-dev"</P><P>CORE_IMAGE_EXTRA_INSTALL += "util-linux"</P><P>CORE_IMAGE_EXTRA_INSTALL += "curl"</P><P>TOOLCHAIN_TARGET_TASK += "boost-dev"</P><P>TOOLCHAIN_TARGET_TASK += "util-linux"</P><P>TOOLCHAIN_TARGET_TASK += "curl"</P><P></P><P>IMAGE_INSTALL_append = " qemu"</P><P>IMAGE_FSTYPES += "ext2 ext3"</P><P></P><P>Please let me know if you need more information.</P><P></P><P>Thanks,</P><P>Abhinav</P></BODY></HTML> Tue, 06 Jan 2015 10:20:08 GMT https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386111#M1566 abhinavbipnesh 2015-01-06T10:20:08Z Re: QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386112#M1567 <HTML><HEAD></HEAD><BODY><P>Also when I tried as below</P><P>sudo ~/QorIQ-SDK-V1.6-20140619-yocto/build_t1040rdb_release/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-ppc64 -kernel uImage  -net nic,model=e1000 -net tap,ifname=tap0,script=no,downscript=no -cpu e5500 -M ppce500 <STRONG>-initrd fsl-image-core-t1040rdb.ext2.gz</STRONG> -no-reboot -show-cursor -no-reboot -m 384 --append "root=/dev/ram console=ttyS0 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=256M <STRONG>ramdisk_size=700000</STRONG>" -nographic -serial tcp::4444,server,telnet QEMU 1.7.0 monitor - type 'help' for more information</P><P></P><P>Boot output for the same is given below</P><P>RAMDISK: gzip image found at block 0</P><P>swapper/0 invoked oom-killer: gfp_mask=0x10200d0, order=0, oom_score_adj=0</P><P>CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.6+gc29fe1a #1</P><P>Call Trace:</P><P>[ce033a60] [c0006f50] show_stack+0x40/0x150 (unreliable)</P><P>[ce033aa0] [c0694d2c] dump_stack+0x78/0xa0</P><P>[ce033ab0] [c0693a3c] dump_header.isra.11+0x54/0x160</P><P>[ce033af0] [c00b3d80] out_of_memory+0x290/0x2a0</P><P>[ce033b30] [c00b80a8] __alloc_pages_nodemask+0x6c8/0x720</P><P>[ce033be0] [c00b0be4] grab_cache_page_write_begin+0x74/0xe0</P><P>[ce033c10] [c012b9cc] block_write_begin+0x3c/0xa0</P><P>[ce033c30] [c00b0574] generic_file_buffered_write+0x194/0x270</P><P>[ce033cb0] [c00b2050] __generic_file_aio_write+0x1d0/0x480</P><P>[ce033d10] [c01315a0] blkdev_aio_write+0x70/0xc0</P><P>[ce033d50] [c00f6e50] do_sync_write+0x70/0xd0</P><P>[ce033db0] [c00f77c8] vfs_write+0xc8/0x1e0</P><P>[ce033dd0] [c00f7ecc] SyS_write+0x4c/0xc0</P><P>[ce033e00] [c0862380] compr_flush+0x30/0x78</P><P>[ce033e10] [c0879124] gunzip+0x2b4/0x36c</P><P>[ce033e50] [c08626e8] rd_load_image+0x320/0x5e8</P><P>[ce033ea0] [c0862ac8] initrd_load+0x50/0x2dc</P><P>[ce033ed0] [c08620a4] prepare_namespace+0xe0/0x1d0</P><P>[ce033ef0] [c0861958] kernel_init_freeable+0x1bc/0x1d0</P><P>[ce033f20] [c0002808] kernel_init+0x18/0x170</P><P>[ce033f40] [c000fce0] ret_from_kernel_thread+0x5c/0x64</P><P>Mem-Info:</P><P>DMA per-cpu:</P><P>CPU    0: hi:   42, btch: 7 usd:   6</P><P>active_anon:0 inactive_anon:0 isolated_anon:0</P><P> active_file:0 inactive_file:0 isolated_file:0</P><P> unevictable:11906 dirty:7 writeback:0 unstable:0</P><P> free:494 slab_reclaimable:205 slab_unreclaimable:436</P><P> mapped:0 shmem:0 pagetables:0 bounce:0</P><P> free_cma:0</P><P>DMA free:1976kB min:2000kB low:2500kB high:3000kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:47624kB isolated(anon):0kB isolated(file):0kB present:262144kB managed:250064kB mlocked:0kB dirty:28kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:820kB slab_unreclaimable:1744kB kernel_stack:224kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes</P><P>lowmem_reserve[]: 0 0 0 0</P><P>DMA: 0*4kB 1*8kB (R) 1*16kB (R) 1*32kB (R) 0*64kB 1*128kB (R) 1*256kB (R) 1*512kB (R) 1*1024kB (R) 0*2048kB 0*4096kB 0*8192kB 0*16384kB = 1976kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1024kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=4096kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=16384kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=65536kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=262144kB</P><P>Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB</P><P>11915 total pagecache pages</P><P>0 pages in swap cache</P><P>Swap cache stats: add 0, delete 0, find 0/0</P><P>Free swap  = 0kB</P><P>Total swap = 0kB</P><P>65536 pages RAM</P><P>0 pages HighMem/MovableOnly</P><P>3020 pages reserved</P><P>[ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name</P><P>Kernel panic - not syncing: Out of memory and no killable processes...</P><P></P><P>I have tried even with ramdisk_size= 307200 but similar output we get at boot time. I am looking for an option through which I can make QEMU to use hard drive as boot device and not RAMFS as the application we want to test will require storage and it should not go into RAM as it will bloat at sometime.</P><P></P><P>Please let me know if you need more information.</P><P></P><P>Thanks,</P><P>Abhinav</P></BODY></HTML> Tue, 06 Jan 2015 10:36:02 GMT https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386112#M1567 abhinavbipnesh 2015-01-06T10:36:02Z Re: QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386113#M1568 <HTML><HEAD></HEAD><BODY><P>Along with that I was trying to do a NFS boot for the same but getting below error, seems I am messing up with options. The steps follow to make NFS stuff is given below</P><OL><LI>tar -C "/home/<username>/rootfs/" --numeric-owner -xzf "fsl-image-core-t1040rdb-20150106174259.rootfs.tar.gz"</LI><LI>Started NFS server and did a configuration in exportfs /home/<username>/rootfs   192.168.7.100(rw,sync) (Directory has 755 mode)</LI><LI>Fire below command for QEMU</LI></OL><P>     sudo ~/QorIQ-SDK-V1.6-20140619-yocto/build_t1040rdb_release/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-ppc64 -kernel uImage  -net nic,model=e1000 -net tap,ifname=tap0,script=no,downscript=no -cpu e5500 -M ppce500  -no-reboot -show-cursor -no-reboot -m 384 --append "root=/dev/nfs rw nfsroot=192.168.7.100:/home/vmprodev/rootfs,nfsvers=3 rw console=ttyS0 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=256M" -nographic -serial tcp::4444,server,telnet </P><P>     Boot log error</P><P>I</P><P>IP-Config: Complete:</P><P>     device=eth0, hwaddr=52:54:00:12:34:56, ipaddr=192.168.7.2, mask=255.255.255.0, gw=192.168.7.1</P><P>     host=192.168.7.2, domain=, nis-domain=(none)</P><P>     bootserver=255.255.255.255, rootserver=192.168.7.100, rootpath=</P><P><STRONG>VFS: Mounted root (nfs filesystem) on device 0:19.</STRONG></P><P><STRONG>devtmpfs: mounted</STRONG></P><P><STRONG>Freeing unused kernel memory: 284K (c0861000 - c08a8000)</STRONG></P><P><STRONG>klogd[631]: unhandled signal 11 at 00000046 nip 0fedaaec lr 0ffed064 code 30001</STRONG></P><P></P><P>So any thoughts where I am messing up with the things.</P><P></P><P>Thanks,</P><P>Abhinav</P></BODY></HTML> Tue, 06 Jan 2015 18:47:39 GMT https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386113#M1568 abhinavbipnesh 2015-01-06T18:47:39Z Re: QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386114#M1569 <HTML><HEAD></HEAD><BODY><P>You need to give the VM enough memory to comfortably fit the ramdisk.  Why are you giving the VM 384 MiB and then telling guest Linux to only use 256?</P><P></P><P>As for /dev/sda1, you need to tell QEMU to create that device and what to back it up with.  I recommend using a virtio block device instead: "-drive file=<image>,index=0,if=virtio" with guest Linux seeing /dev/vdaN.  Make sure virtio PCI and virtio block are enabled in the guest kernel.</P></BODY></HTML> Fri, 09 Jan 2015 00:30:26 GMT https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386114#M1569 scottwood 2015-01-09T00:30:26Z Re: QEMU-system-ppc64 ram disk give error as RAMDISK: incomplete write (22321 != 32768) https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386115#M1570 <HTML><HEAD></HEAD><BODY><P>Finally I am able to boot through NFS and skipped booting using ramfs.</P><P></P><P>Thanks for providing inputs.</P></BODY></HTML> Thu, 29 Jan 2015 17:51:16 GMT https://community.nxp.com/t5/QorIQ/QEMU-system-ppc64-ram-disk-give-error-as-RAMDISK-incomplete/m-p/386115#M1570 abhinavbipnesh 2015-01-29T17:51:16Z