If I add that line, (
IMAGE_FSTYPES = "vmdk"
), to my local.conf, I get:
rich@burgess> time bitbake core-image-minimal
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable
the checker (see sanity.conf).
Following is the list of potential problems / advisories:
Error, IMAGE_FSTYPES vmdk and live can't be built together
Summary: There was 1 ERROR message shown, returning a non-zero exit
code.
Building yocto-2.0 for genericx86-64. What am I doing wrong?
--rich
On 3/13/16 23:09 , Khem Raj wrote:
just use IMAGE_FSTYPES = "vmdk" if you plan to use virtualbox and need
a raw image.
On Sun, Mar 13, 2016 at 10:16 PM, Gary Thomas <g...@mlbassoc.com> wrote:
I'd like to to some testing that qemu just doesn't seem up to
so I attempted to build a live ISO per the documentation. I
added these lines to local.conf:
IMAGE_FSTYPES_genericx86 += "live"
NOISO_genericx86 = "0"
When I try to build core-image-base I get this error:
ERROR: INITRD_IMAGE_LIVE core-image-minimal-initramfs cannot use image
live, hddimg or iso.
ERROR: Check IMAGE_FSTYPES and INITRAMFS_FSTYPES settings.
ERROR: Failed to parse recipe:
/local/poky-cutting-edge/meta/recipes-core/images/core-image-minimal-initramfs.bb
I'm using a recent Poky checkout (d53413d3a8444c38a83ea37867c8af7754d8e702)
Am I just doing something wrong here? I was following this section of the
mega-manual:
26.56. image-live.bbclass¶
The image-live class supports building "live" images.
Normally, you do not use this class directly. Instead, you add "live" to
IMAGE_FSTYPES.
For example, if you were building an ISO image, you would add "live" to
IMAGE_FSTYPES,
set the NOISO variable to "0" and the build system would use the
image-live class to
build the ISO image.
I don't have any available hardware for this testing, so I thought
I'd use VirtualBox. Is this a reasonable approach? I want to use
a live ISO so I get a writable file system. I tried just using the
.hddimage but that doesn't boot with VirtualBox :-(
To be clear, along with the additions above in local.conf, I tried:
$ MACHINE=genericx86 bitbake core-image-base
Thanks for any ideas
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
