| Summary: | qemu image free space too small | ||
|---|---|---|---|
| Product: | [Runtime] General Runtime | Reporter: | Ning Zhang <ning.zhang> |
| Component: | General Runtime | Assignee: | Chen Qi <Qi.Chen> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | hongxu.jia, kai.kang, liezhi.yang, Qi.Chen, richard.purdie, sen.zhang, sgw, yi.zhao |
| Version: | 1.4 | ||
| Target Milestone: | 1.4 M6 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Ning Zhang
2013-03-26 08:34:14 UTC
The image size is determined by the initial IMAGE_ROOTFS size and the IMAGE_OVERHEAD_FACTOR which defaults to 1.3. meta/conf/bitbake.conf:IMAGE_OVERHEAD_FACTOR ?= "1.3" Two solutions to solve this problem. 1. Resize the ext3 file locally For example, if we want to add 100M to core-image-sato.ext3 image, we could use the following commands. dd if=/dev/zero of=core-image-sato.ext3 bs=1M count=100 oflag=append conv=notrunc e2fsck -f core-image-sato.ext3 resize2fs core-image-sato.ext3 2. override IMAGE_OVERHEAD_FACTOR in core-image-sato.bb file IMAGE_OVERHEAD_FACTOR = "2.0" I'll send out a patch using solution 2. This problem will obviously occur to all sato images and block automatic testing, so these's enough reason to do so. Any comment or suggestion is welcome. //Chen Qi I understand what you are trying to do here, do the tests clean-up after they run? I am a little hesitant to add so much additional space, we have 2 conflicting goals with the size of the image. 1) Show a compact example with graphical interface (not bloat-ware or full desktop). 2) Use it for automated testing with enough space for running the tests. Now We use a small smart repository. Now the index file reduce to a small size. The test can pass. |