openembedded-core.git/meta/classes/image-vm.bbclass, branch thud

image: Convert vmdk/vdi/qcow2 to strict CONVERSION_CMD types

2017-07-30T07:45:13+00:00

The vmdk/vdi/qcow2 IMAGE_FSTYPEs predate wic.  As such, they provide
some similar underlying functionality in order to produce a "disk" image
that in turn can be converted into different formats that various
hypervisor types work with.  They do not however provide the ability for
other disk image types to be converted into these same output types.
Furthermore, they are less flexible than what wic does provide.  This
drops the old style vmdk/vdi/qcow2 types and re-introduces them under
the CONVERSION_CMD framework.  The equivalent of vmdk is now wic.vmdk
and so forth for the other types.

Signed-off-by: Tom Rini 
Signed-off-by: Richard Purdie

live-vm-common: add MKDOSFS_EXTRAOPTS variable

2017-07-17T12:48:53+00:00

Sometimes it's needed to create FAT filesystem with specific
sector or cluster size, FAT size or to use one of other useful
mkdosfs options.

Introduced MKDOSFS_EXTRAOPTS variable to set options for mkdosfs.

[YOCTO #11709]

Signed-off-by: Ed Bartosh 
Signed-off-by: Ross Burton

image-vm: Avoid use of fold, tac and paste commands for DISK_SIGNATURE

2017-06-12T14:04:08+00:00

These commands are not whitelisted by the HOSTTOOLS variable which
silently prevents the MBR disk signature from being written to the
image.

Reported-by: Michael Davis 
Signed-off-by: Jonathan Liu 
Signed-off-by: Ross Burton

meta: remove True option to getVar calls

2016-12-16T08:30:03+00:00

getVar() now defaults to expanding by default, thus remove the True
option from getVar() calls with a regex search and replace.

Search made with the following regex: getVar ?\(( ?[^,()]*), True\)

Signed-off-by: Joshua Lock 
Signed-off-by: Ross Burton

Remove RM_OLD_IMAGE, it's no longer useful

2016-10-15T08:48:28+00:00

Since the move to put image deployment under sstate control in
d54339d4b1a7e884de636f6325ca60409ebd95ff old images are automatically
removed before a new image is deployed (the default behaviour of the
sstate logic).

RM_OLD_IMAGE is therefore no longer required to provide this
behaviour, remove the variable and its users.

Signed-off-by: Joshua Lock 
Signed-off-by: Ross Burton

image: Deploy images to IMGDEPLOYDIR

2016-09-03T23:05:12+00:00

Changed deployment directory from DEPLOY_DIR_IMAGE to
IMGDEPLOYDIR to make sstate machinery to do final deployment and
generate manifest.

Renamed variable deploy_dir to deploy_dir_image in selftest code
to avoid confusion with DEPLOYDIR variable.

Updated the code of rootfs.py:Rootfs class to use IMGDEPLOYDIR variable
as it's now used as a new deployment destination.

Signed-off-by: Ed Bartosh 
Signed-off-by: Richard Purdie

image-vm.bbclass: remove old images if RM_OLD_IMAGE is enabled

2016-08-20T15:05:28+00:00

[YOCTO #10164]

Signed-off-by: Jonathan Liu 
Signed-off-by: Richard Purdie

image-live, image-vm, wic: Remove fs size workaround

2016-06-03T12:12:14+00:00

Since mtools has been patched to live with filesystems with sizes
not divisible by sectors-per-track, we no longer need to try to
set the size based on our guess of the sectors-per-track dosfstools is
going to use.

Signed-off-by: Jussi Kukkonen 
Signed-off-by: Richard Purdie

classes/image_vm: allow different filesystems to be used for VM images.

2016-05-09T07:03:58+00:00

This allows for things like btrfs to be used vs just ext4.
The default value of ext4 is kept so there is no functional
change unless VM_ROOTFS_TYPE is set in the inherting recipe.

Signed-off-by: Ian Reinhart Geiser 
Signed-off-by: Ross Burton

image-vm.bbclass/image_types.bbclass: IMAGE_NAME -> IMAGE_LINK_NAME

2016-04-09T06:53:19+00:00

If we create hdddirect in the first time, and run bitbake to create
vmimg in the second time, then the previouse created
${IMAGE_LINK_NAME}.hdddirect may can not be found since it contains the
data string which are different. Use IMAGE_LINK_NAME to fix the problem.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie