#vmdk #hddimg #iso with #dunfell #vmdk #hddimg #iso


Some more information:

Build Configuration:

BB_VERSION= "1.46.0"
BUILD_SYS= "x86_64-linux"

TARGET_SYS= "x86_64-poky-linux"
MACHINE= "virtualbox"
DISTRO= "my-gnu-linux"


Without any ajustments in my .conf file I get the missing WKS_FILE/S warning:

ERROR: my-image-1.0-r0 do_image_wic: No kickstart files from WKS_FILES were found: my-image.virtualbox.wks my-image.wks. Please set WKS_FILE or WKS_FILES appropriately.


*** hddimg/vdmk ***

IMAGE_FSTYPES = "hddimg"

Convert the generated hddimg to vdmk :

$ vboxmanage convertfromraw image-virtualbox.hddimg image-virtualbox.vdmk

Starting image-virtualbox.vdmk with VirtualBox:


Starting image-virtualbox.hdd with VirtualBox shows the same behaviour as for vdmk

Opening the vdmk file as an archive the files show strange creation dates:


*** iso ***

Setting IMAGE_FSTYPES = "iso"
Starting image-virtualbox.iso with VirtualBox:
Linux is booting until it hangs after "Load/Save Random Seed". What stands out is the failure message in the beginning "Failed to start Remount Root and Kernel File Systems"... But how to fix it?





I switched from warrior to dunfell and want to build an image for Oracles VirtualBox VM.
On warrior there was 'automatically' a hddimg generated on dunfell this is no longer the case. The IMAGE_FSTYPES has to by specified, I use:
WKS_FILE = "virtualbox.wks"
IMAGE_FSTYPES += "wic.vmdk"

This requires me to write an wks file for which I use:
part /boot --source bootimg-pcbios --ondisk sda --label boot --active --align 1024
part / --source rootfs --ondisk sda --fstype=ext4 --label platform --align 1024
bootloader --ptable gpt  --timeout=5  --append="rootfstype=ext4 video=vesafb vga=current console=tty0"

With these settings I get an vmdk image but it fails to boot. I get a "VFS Unable to mount root fs on unknown block(0,0)" dump.

Any ideas?