topic Re: Error on Topaz/fs-core-image/LXC/Libvirt in QorIQ

topic Re: Error on Topaz/fs-core-image/LXC/Libvirt in QorIQ https://community.nxp.com/t5/QorIQ/Error-on-Topaz-fs-core-image-LXC-Libvirt/m-p/393460#M1640 <HTML><HEAD></HEAD><BODY><P>Hello <SPAN class="replyToName">Juan Rodrigo,</SPAN></P><P></P><P><SPAN class="replyToName">In the Hypervisor environment, you need to use the ramdisk filesystem less than 32M.</SPAN></P><P><SPAN class="replyToName">Actually it's not recommended to modify the source code too much.</SPAN></P><P><SPAN class="replyToName">I suggest you build a "fsl-image-virt" filesystem image less then 32M, which includes libvirt and LXC support.</SPAN></P><P></P><P><SPAN class="replyToName">You could build <SPAN class="replyToName">fsl-image-virt image based on fsl-image-minimal.bb, and the size of the filesystem will be reduced a lot.</SPAN></SPAN></P><P><SPAN class="replyToName">Please modify the first line of the recipe meta-fsl-networking/images/fsl-image-virt.bb as the following.</SPAN></P><P><STRONG><SPAN class="replyToName">require images/fsl-image-minimal.bb</SPAN></STRONG></P><P></P><P><SPAN class="replyToName"><SPAN class="replyToName">If you need some other specific packages support, please add them in the variable "IMAGE_INSTALL".</SPAN><BR /></SPAN></P><P><SPAN class="replyToName"><SPAN class="replyToName"></SPAN></SPAN></P><P><SPAN class="replyToName"><SPAN class="replyToName"><SPAN class="replyToName">Then rebuild the filesystem with the command "bitbake <SPAN class="replyToName">fsl-image-virt". </SPAN></SPAN></SPAN></SPAN></P><P><BR />Have a great day,<BR />Yiping</P><P></P><P>-----------------------------------------------------------------------------------------------------------------------<BR />Note: If this post answers your question, please click the Correct Answer button. Thank you!<BR />-----------------------------------------------------------------------------------------------------------------------</P></BODY></HTML> Thu, 24 Sep 2015 11:09:27 GMT yipingwang 2015-09-24T11:09:27Z Error on Topaz/fs-core-image/LXC/Libvirt https://community.nxp.com/t5/QorIQ/Error-on-Topaz-fs-core-image-LXC-Libvirt/m-p/393459#M1639 <HTML><HEAD></HEAD><BODY><P>We would like to load a modified version of the fsl-image-core with LXC and libvirt using Topaz.</P><P>We have modified the file hypervisor configuration tree. The changes have been the followings:</P><P></P><TABLE><TBODY><TR><TD>    </TD><TD>images_pma {</TD></TR><TR><TD>            </TD><TD>compatible = "phys-mem-area";</TD></TR><TR><TD>            </TD><TD>addr = <0x0 0x78000000>;</TD></TR><TR><TD>            </TD><TD>size = <0x0 0x6000000>;</TD></TR><TR><TD>    </TD><TD>};</TD></TR></TBODY></TABLE><P></P><TABLE><TBODY><TR><TD>    </TD><TD>pma15 {</TD></TR><TR><TD>            </TD><TD>compatible = "phys-mem-area";</TD></TR><TR><TD>            </TD><TD>addr = <0x0 0x7e000000>;</TD></TR><TR><TD>            </TD><TD>size = <0x0 0x1000000>;</TD></TR><TR><TD>            </TD><TD>linux,phandle = <0x6>;</TD></TR><TR><TD>            </TD><TD>phandle = <0x6>;</TD></TR><TR><TD>    </TD><TD>};</TD></TR></TBODY></TABLE><P></P><TABLE><TBODY><TR><TD>    </TD><TD>hv_pma {</TD></TR><TR><TD>            </TD><TD>compatible = "phys-mem-area";</TD></TR><TR><TD>            </TD><TD>addr = <0x0 0x80000000>;</TD></TR><TR><TD>            </TD><TD>size = <0x0 0x1000000>;</TD></TR><TR><TD>            </TD><TD>linux,phandle = <0x2>;</TD></TR><TR><TD>            </TD><TD>phandle = <0x2>;</TD></TR><TR><TD>    </TD><TD>};</TD></TR></TBODY></TABLE><P></P><TABLE><TBODY><TR><TD>    </TD><TD>part1 {</TD></TR><TR><TD>            </TD><TD>compatible = "partition";</TD></TR><TR><TD>            </TD><TD>label = "p1-linux";</TD></TR><TR><TD>            </TD><TD>cpus = <0x0 0x3>;</TD></TR><TR><TD>            </TD><TD>guest-image = <0x0 0x78020000 0x0 0x0 0x0 0x700000>;</TD></TR><TR><TD>            </TD><TD>linux-rootfs = <0x0 0x79300000 0x0 0x5000000 0x0 0x4000000>;</TD></TR><TR><TD>            </TD><TD>dtb-window = <0x0 0x1000000 0x0 0x20000>;</TD></TR><TR><TD>            </TD><TD>no-dma-disable;</TD></TR></TBODY></TABLE><P></P><TABLE><TBODY><TR><TD>    </TD><TD>part2 {</TD></TR><TR><TD>            </TD><TD>compatible = "partition";</TD></TR><TR><TD>            </TD><TD>label = "p2-linux";</TD></TR><TR><TD>            </TD><TD>cpus = <0x3 0x1>;</TD></TR><TR><TD>            </TD><TD>guest-image = <0x0 0x78020000 0x0 0x0 0x0 0x700000>;</TD></TR><TR><TD>            </TD><TD>linux-rootfs = <0x0 0x79300000 0x0 0x5000000 0x0 0x4000000>;</TD></TR><TR><TD>            </TD><TD>dtb-window = <0x0 0x1000000 0x0 0x20000>;</TD></TR><TR><TD>            </TD><TD>no-dma-disable;</TD></TR></TBODY></TABLE><P></P><P>The sizes of the binaries are:</P><P></P><P>-rw-r--r-- 1 t1040 t1040  48M sep 17 15:11 fsl-image-core-t1040rdb-20150917130600.rootfs.ext2.gz.u-boot</P><P>-rw-r--r-- 1 t1040 t1040 4,6M sep 16 12:36 uImage--3.12-r0-t1040rdb-20150916102323.bin</P><P>-rw-r--r-- 1 t1040 t1040  36K sep 17 15:41 uImage--3.12-r0-t1040rdb-usdpaa-20150916102323.dtb</P><P></P><P>The uboot commands to start form the RAM are:</P><P></P><P>tftp 78020000 uImage--3.12-r0-t1040rdb-20150916102323.bin</P><P>tftp 79300000 fsl-image-core-t1040rdb-20150917130600.rootfs.ext2.gz.u-boot</P><P>tftp 78700000 hv.uImage</P><P>tftp 0x78800000 uImage--3.12-r0-t1040rdb-usdpaa-20150916102323.dtb</P><P>tftp 0x78900000 hv.dtb</P><P></P><P>On booting the system we got the error below:</P><P></P><P>RAMDISK: gzip image found at block 0</P><P><STRONG>2RAMDISK: incomplete write (9290 != 32768)</STRONG></P><P>write error</P><P>VFS: Mounted root (ext2 filesystem) readonly on device 1:0.</P><P>devtmpfs: mounted</P><P>Freeing unused kernel memory: 284K (c0923000 - c096a000)</P><P>INIT: version 2.88 booting</P><P>Starting udev</P><P>udevd[619]: starting version 182</P><P>1RAMDISK: incomplete write (9290 != 32768)</P><P>write error</P><P>VFS: Mounted root (ext2 filesystem) readonly on device 1:0.</P><P>devtmpfs: mounted</P><P>Freeing unused kernel memory: 284K (c0923000 - c096a000)</P><P>INIT: version 2.88 booting</P><P>Starting udev</P><P>udevd[969]: starting version 182</P><P>seville ffe800000.l2switch: Found Seville Switch, UIO device - IRQ 293, id 0x099530e9.</P><P>seville MAC address not found</P><P>2Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory</P><P>bootlogd.</P><P>EXT2-fs (ram0): error: read_inode_bitmap: Cannot read inode bitmap - block_group = 17, inode_bitmap = 139266</P><P>urandom start: failed.</P><P>Populating dev cache</P><P>EXT2-fs (ram0): error: read_inode_bitmap: Cannot read inode bitmap - block_group = 16, inode_bitmap = 131074</P><P>tar: can't open '/etc/dev.tar': Input/output error</P><P>EXT2-fs (ram0): error: read_inode_bitmap: Cannot read inode bitmap - block_group = 16, inode_bitmap = 131074</P><P>/etc/rcS.d/S37populate-volatile.sh: line 56: /etc/volatile.cache.build: Input/output error</P><P>EXT2-fs (ram0): error: read_inode_bitmap: Cannot read inode bitmap - block_group = 16, inode_bitmap = 131074</P><P>/etc/rcS.d/S37populate-volatile.sh: line 56: /etc/volatile.cache.build: Input/output error</P><P>EXT2-fs (ram0): error: read_inode_bitmap: Cannot read inode bitmap - block_group = 16, inode_bitmap = 131074</P><P>/etc/rcS.d/S37populate-volatile.sh: line 56: /etc/volatile.cache.build: Input/output error</P><P>EXT2-fs (ram0): error: read_inode_bitmap: Cannot read inode bitmap - block_group = 16, inode_bitmap = 131074</P><P>/etc/rcS.d/S37populate-volatile.sh: line 84: /etc/volatile.cache.build: Input/output error</P><P>EXT2-fs (ram0): error: read_inode_bitmap: Cannot read inode bitmap - block_group = 16, inode_bitmap = 131074</P><P>/etc/rcS.d/S37populate-volatile.sh: line 84: /etc/volatile.cache.build: Input/output error</P><P>EXT2-fs (ram0): error: read_inode_bitmap: Cannot read inode bitmap - block_group = 16, inode_bitmap = 131074</P><P>/etc/rcS.d/S37populate-volatile.sh: line 84: /etc/volatile.cache.build: Input/output error</P><P></P><P></P><P>Any suggestion to fix the problem will be appreciated.</P><P></P><P>Thanks in advance,</P><P></P><P>Juan.</P></BODY></HTML> Fri, 18 Sep 2015 13:42:34 GMT https://community.nxp.com/t5/QorIQ/Error-on-Topaz-fs-core-image-LXC-Libvirt/m-p/393459#M1639 jrodrigo 2015-09-18T13:42:34Z Re: Error on Topaz/fs-core-image/LXC/Libvirt https://community.nxp.com/t5/QorIQ/Error-on-Topaz-fs-core-image-LXC-Libvirt/m-p/393460#M1640 <HTML><HEAD></HEAD><BODY><P>Hello <SPAN class="replyToName">Juan Rodrigo,</SPAN></P><P></P><P><SPAN class="replyToName">In the Hypervisor environment, you need to use the ramdisk filesystem less than 32M.</SPAN></P><P><SPAN class="replyToName">Actually it's not recommended to modify the source code too much.</SPAN></P><P><SPAN class="replyToName">I suggest you build a "fsl-image-virt" filesystem image less then 32M, which includes libvirt and LXC support.</SPAN></P><P></P><P><SPAN class="replyToName">You could build <SPAN class="replyToName">fsl-image-virt image based on fsl-image-minimal.bb, and the size of the filesystem will be reduced a lot.</SPAN></SPAN></P><P><SPAN class="replyToName">Please modify the first line of the recipe meta-fsl-networking/images/fsl-image-virt.bb as the following.</SPAN></P><P><STRONG><SPAN class="replyToName">require images/fsl-image-minimal.bb</SPAN></STRONG></P><P></P><P><SPAN class="replyToName"><SPAN class="replyToName">If you need some other specific packages support, please add them in the variable "IMAGE_INSTALL".</SPAN><BR /></SPAN></P><P><SPAN class="replyToName"><SPAN class="replyToName"></SPAN></SPAN></P><P><SPAN class="replyToName"><SPAN class="replyToName"><SPAN class="replyToName">Then rebuild the filesystem with the command "bitbake <SPAN class="replyToName">fsl-image-virt". </SPAN></SPAN></SPAN></SPAN></P><P><BR />Have a great day,<BR />Yiping</P><P></P><P>-----------------------------------------------------------------------------------------------------------------------<BR />Note: If this post answers your question, please click the Correct Answer button. Thank you!<BR />-----------------------------------------------------------------------------------------------------------------------</P></BODY></HTML> Thu, 24 Sep 2015 11:09:27 GMT https://community.nxp.com/t5/QorIQ/Error-on-Topaz-fs-core-image-LXC-Libvirt/m-p/393460#M1640 yipingwang 2015-09-24T11:09:27Z Re: Error on Topaz/fs-core-image/LXC/Libvirt https://community.nxp.com/t5/QorIQ/Error-on-Topaz-fs-core-image-LXC-Libvirt/m-p/393461#M1641 <HTML><HEAD></HEAD><BODY><P>Why do you say that the ramdisk needs to be less than 32 MiB?  I know of no such limitation in Topaz.</P><P></P><P>While it's hard to diagnose the problem without seeing hypervisor console output, full kernel output, and the full config tree, my first guess is that the kernel command line is missing the ramdisk_size parameter, so the kernel defaults to a size that is not large enough for your ramdisk.  If this is the cause, you'd have the same problem running without Topaz.</P></BODY></HTML> Mon, 28 Sep 2015 21:52:15 GMT https://community.nxp.com/t5/QorIQ/Error-on-Topaz-fs-core-image-LXC-Libvirt/m-p/393461#M1641 scottwood 2015-09-28T21:52:15Z