xxx-native packages should not depend on ${DISTRO} settings. Doing
so feels inherently wrong and limits the usefulness of sstate-cache.
This patch changes how this package is installed, in particular
removing the dependency on the ${DISTRO_FEATURES} variable in
glib-2.0-native. This will
On Sat, 2017-01-21 at 00:16 +, Burton, Ross wrote:
> On 21 January 2017 at 00:12, Burton, Ross wrote:
>
> > Computing transaction...warning: Can't install
> > alsa-lib-dev-1.1.3-r0.0@core2_32: Can't install
> > alsa-lib-dev-1.1.3-r0.0@core2_32: no package provides
On 21 January 2017 at 00:12, Burton, Ross wrote:
> Computing transaction...warning: Can't install
> alsa-lib-dev-1.1.3-r0.0@core2_32: Can't install
> alsa-lib-dev-1.1.3-r0.0@core2_32: no package provides alsa-lib =
> 1.1.3-r0.0
>
Had a ten second look at 1.1.2, there's an
For some reason the autobuilder is having a meltdown with this error
message:
Computing transaction...warning: Can't install
alsa-lib-dev-1.1.3-r0.0@core2_32: Can't install
alsa-lib-dev-1.1.3-r0.0@core2_32: no package provides alsa-lib = 1.1.3-r0.0
I'm guessing a new file sneaked into the build
Minor upgrade contains fixes from 2.7.0.
Removed patches (already in upstream):
- 0001-pci-assign-sync-MSI-MSI-X-cap-and-table-with-PCIDevi.patch
- 0001-virtio-zero-vq-inuse-in-virtio_reset.patch
- 0002-fix-CVE-2016-7423.patch
Signed-off-by: Aníbal Limón
---
To enable glamor, we need to also enable both dri3 and xshmfence as
dependencies.
Signed-off-by: Saul Wold
---
meta/recipes-graphics/xorg-xserver/xserver-xorg.inc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
When using the modesetting with glamor and MUSL, the glamoregl
library needs to be pre-loaded, so add it to the list here.
Signed-off-by: Saul Wold
---
.../xorg-xserver/xserver-xf86-config/10-preload-modules.conf | 1 +
1 file changed, 1 insertion(+)
diff
On Fri, Jan 20, 2017 at 7:24 PM, Patchwork
wrote:
> == Series Details ==
>
> Series: "Switch to Recipe Specific Sysr..." and 2 more
> Revision: 1
> URL : https://patchwork.openembedded.org/series/4877/
> State : failure
>
> == Summary ==
>
>
> Thank you for
On Fri, 2017-01-20 at 12:12 -0600, Aníbal Limón wrote:
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -9,12 +9,11 @@ require qemu-targets.inc
> inherit autotools ptest
> BBCLASSEXTEND = "native nativesdk"
>
> -PR = "r1"
> -
> # QEMU_TARGETS is
This test checks to make sure only the files expected exist in a
container image. Currently only ROOTFS_BOOTSTRAP_INSTALL, gets added to
all images without the user specifying it.
But this test should help if a developer in the future ever silently
adds more than just ROOTFS_BOOTSTRAP_INSTALL,
== Series Details ==
Series: "Switch to Recipe Specific Sysr..." and 2 more
Revision: 1
URL : https://patchwork.openembedded.org/series/4877/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
Minor upgrade contains fixes from 2.7.0.
Removed patches (already in upstream):
- 0001-pci-assign-sync-MSI-MSI-X-cap-and-table-with-PCIDevi.patch
- 0001-virtio-zero-vq-inuse-in-virtio_reset.patch
- 0002-fix-CVE-2016-7423.patch
Signed-off-by: Aníbal Limón
---
From: Ed Bartosh
Fixed isoimage-isohybrid plulgin and correspondent wic tet case:
- used wic-tools target when getting varlue of STAGING_LIBDIR variable
- ensured that image is built with efi and hddimg enabled
Signed-off-by: Ed Bartosh
From: Ed Bartosh
This meta recipe is for building tools used by wic.
It allows wic to find tools in recipe specific sysroot as
all tools will be present in wic-tools sysroot.
NOTE: task do_build_sysroot is created to ensure that
sysroot is re-populated when package
From: Ed Bartosh
Added dependency do_image_wic -> wic-tools:do_build to ensure
that all required tools are ready to use by wic.
Signed-off-by: Ed Bartosh
---
meta/classes/image_types.bbclass | 1 +
1 file changed, 1 insertion(+)
diff
From: Ed Bartosh
Setting WKS_FILE variable should be done only when
wic image is expected to be built by bitbake.
If it's set for all images it breaks image building in
some cases.
Signed-off-by: Ed Bartosh
---
From: Ed Bartosh
wic used native sysroot to get path to pseudo utility.
This approach doesn't work with recipe specific sysroots.
Using FAKEROOTCMD should fix the issue.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/partition.py | 2 +-
From: Ed Bartosh
As STAGING_DIR_TARGET started to point to a recipe specific
sysroot wic is not able to add .env files when .wks file refers
to multiple rootfs recipes.
Used STAGING_DIR instead of STAGING_DIR_TARGET to make the
directory with .env files the same for
From: Ed Bartosh
Built wic-tools recipe instead of set of tools recipes
to ensure that all tools are available from one recipe sysroot.
Signed-off-by: Ed Bartosh
---
meta/lib/oeqa/selftest/wic.py | 3 +--
1 file changed, 1 insertion(+),
From: Ed Bartosh
Used wic-tools target to get location of syslinux.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/plugins/source/bootimg-pcbios.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Ed Bartosh
This parameter will be used to allow or prevent variable caching.
For example, we don't want to cache value of RECIPE_SYSROOT_NATIVE
wic-tools variable as we may decide to rebuild wic-tools.
Signed-off-by: Ed Bartosh
---
From: Ed Bartosh
Added RECIPE_SYSROOT_NATIVE to the WICVARS for wic
to be able to access it when run from bitbake.
Signed-off-by: Ed Bartosh
---
meta/classes/image_types.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Ed Bartosh
Renamed grub-efi-native -> grub-efi in NATIVE_RECIPES
dictionary as '-native' suffix is added to the recipe name in
the code.
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/utils/oe/misc.py | 2 +-
1 file changed, 1
From: Ed Bartosh
Rebuild wic-tools if its native sysroot doesn't exist to ensure
that all required tools are available.
Signed-off-by: Ed Bartosh
---
scripts/wic | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff
From: Ed Bartosh
wic used STAGING_DIR_NATIVE variable as a path to native sysroot.
This doesn't work with recipe specific sysroots as STAGING_DIR_NATIVE
points to the native sysroot of the current recipe.
Used RECIPE_SYSROOT_NATIVE variable of wic-tools recipe
to fix
From: Ed Bartosh
Fixed test_systemd_bootdisk, test_wic_image_type and test_qemu
test cases by building core-image-minimal with correct configuration.
Signed-off-by: Ed Bartosh
---
meta/lib/oeqa/selftest/wic.py | 12
1 file
There is no common sysroot any more so add the libusb dependency using DEPENDS
and check for the output in the sysroot output directory so the tests
work with recipe specific sysroots.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/devtool.py | 9
The extend_recipe_sysroot itself is excluded from the task hashes. This is
because it only ever acts upon the contents of the task dependencies and hence
those checksums accurately relfect what its doing. It does mean sysroots don't
repopulate if this function changes but there are other easy ways
This patch is comparatively large and invasive. It does only do one thing,
switching the
system to build using recipe specific sysroots and where changes could be
isolated from it,
that has been done.
With the current single sysroot approach, its possible for software to find
things which
== Series Details ==
Series: OEQA Framework Refactor & Improvements (rev4)
Revision: 4
URL : https://patchwork.openembedded.org/series/4272/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/runtime/context.py | 22 --
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oeqa/runtime/context.py b/meta/lib/oeqa/runtime/context.py
index 10a8872..e692bc0 100644
---
From: Mariano Lopez
This adapt the current runtime selftest to use the new runtime
framework.
Signed-off-by: Mariano Lopez
---
.../lib/oeqa/runtime/{ => cases}/selftest.json | 0
.../lib/oeqa/runtime/{ => cases}/selftest.py
From: Mariano Lopez
This adds default values to OERuntimeTestContextExecutor class in
order to make easier the execution of exported test that were
generated with testexport class.
[YOCTO #10686]
Signed-off-by: Mariano Lopez
---
From: Mariano Lopez
testimage support the installation of packages without a package
manager in the target. This adds support for package extraction
required to support the installation feature.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
From: Mariano Lopez
This migrates current testexport implmentation to use the
new OEQA framework.
[YOCTO #10686]
Signed-off-by: Mariano Lopez
---
meta/classes/testexport.bbclass | 215 +---
From: Mariano Lopez
This allows to use the package install feature with
the new OEQA framework.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/classes/testimage.bbclass | 27
From: Mariano Lopez
This will add functions to get module file path from a test
case or a complete suite.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/utils/test.py | 13 +
1 file changed, 13
From: Mariano Lopez
This migrates testimage class to use the new framework. Most of
the code added here is to get rid off the data store dependency.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/classes/testimage.bbclass |
From: Mariano Lopez
This migrates current runtime test suite to be used with the new framework.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
.../{runtime_cases => runtime/cases}/_ptest.py | 0
.../{runtime_cases =>
From: Mariano Lopez
This migrates the smart test from the old framework to
the new one. This has its own commit because smart
test was using bb and oe libraries that are available
when exporting the test cases to run in a different host.
Because of the removal of
From: Mariano Lopez
This adds qemu target to be used in testimage.
It uses the current QemuRunner class in order
to boot and control qemu.
[YOCTO #10231]
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/target/qemu.py | 45
From: Mariano Lopez
Current targets (ssh and qemu) require a logger in their
constructors, so in order to get a new target we need
to provide the logger.
[YOCTO #10686]
Signed-off-by: Mariano Lopez
---
This commit will prepare context to use qemu and not just
simpleremote.
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/runtime/context.py | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/meta/lib/oeqa/runtime/context.py
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/runtime/context.py | 56 ++--
1 file changed, 36 insertions(+), 20 deletions(-)
diff --git a/meta/lib/oeqa/runtime/context.py b/meta/lib/oeqa/runtime/context.py
index e692bc0..ec378bb
To avoid getVar calls inside a utils module, also moves
get_host_dumper import inside testexport isn't needed.
[YOCTO #10231]
Signed-off-by: Aníbal Limón
---
meta/classes/testexport.bbclass | 1 -
meta/classes/testimage.bbclass | 5 +++--
From: Mariano Lopez
As part of the refactor we require to move the files used
in runtime testing to the new directory. This also adds
the path to the runtime test context.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
From: Mariano Lopez
skipIfNotDataVar will skip a test if a variable doesn't have certain value.
skipIfNotInDataVar will skip a test if a value is not in a certain variable.
Signed-off-by: Mariano Lopez
---
From: Mariano Lopez
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/runtime/utils/targetbuildproject.py | 29 +--
1 file changed, 16 insertions(+), 13 deletions(-)
diff --git
From: Mariano Lopez
This add the option to select what tests to run in the
[.[.]] format.
Currently it just support modules
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/context.py | 6 ++
1 file changed, 6 insertions(+)
From: Mariano Lopez
This new decorator will be used to skip the test
if the image under test doesn't have the required
packages installed.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/runtime/decorator/package.py
From: Mariano Lopez
This adds a new decorator to check if image under tests has
certain DISTRO_FEATURE or IMAGE_FEATURE.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/decorator/data.py | 28
From: Mariano Lopez
With this commit now it is possible to add targets with SSH for testing.
Most of it was imported for existing code, with improvements in log
handling.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
From: Mariano Lopez
This adds OERuntimeTestCase, OERuntimeTestContext, and OERuntimeTestLoader
to be used for runtime testing.
As expected there are some changes in runtime context:
- Adds the target to be used for runtime testing, the default
is a SSH connection
TargetBuildProject was refactored to avoid bitbake dependency so
the instance don't allow to pass data store anymore.
classes/testimage: Export proxies before run tests
The TargetBuildProject based tests download archives from network.
Signed-off-by: Aníbal Limón
Common files was move to oeqa/files from oeqa/runtime/files
because the same files are used across Runtime,SDK,eSDK tests.
Signed-off-by: Aníbal Limón
---
meta/classes/testexport.bbclass | 5 +
meta/lib/oeqa/oetest.py | 1 +
meta/lib/oeqa/runtime/gcc.py
The new oeqa core framework will modify the structure of the runtime
folder the new runtime folder will have python code inside to support
runtime test cases.
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/{runtime => runtime_cases}/_ptest.py | 0
Summary,
- Changes base case class to OESDKExtTest.
- Changes decorator classes to new ones.
- Chnages variable names sdktestdir -> sdk_dir.
- Added missing license to MIT.
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/sdk/cases/buildgalculator.py | 2 +-
Signed-off-by: Aníbal Limón
---
meta/classes/testsdk.bbclass | 98
1 file changed, 45 insertions(+), 53 deletions(-)
diff --git a/meta/classes/testsdk.bbclass b/meta/classes/testsdk.bbclass
index 176dafd..69689a1 100644
For match with the new structure of the OEQA framework.
In the new framework Test component base directory in this case
sdk module will contain case and context implementations.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/sdkext/__init__.py
The extensible sdk context and case modules extends the sdk ones,
this means that the tests from sdk are run also the sdkext tests.
Enables support in context for use oe-test esdk command for run
the test suites, the same options of sdk are required for run esdk tests.
Removes old related to
The new buildproject module will contain only BuildProject class
a helper class for build source code.
The remaining classes TargetBuildProject and SDKBuildProject was
move to runtime and sdk respectively.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by:
The TEST_LOG_DIR was used for store sdk_target_log this log
contains the output of the run of build commands now that information
could be found also on log.do_testsdk under WORKDIR.
The log will continue to store into SDK_DIR instead of TEST_LOG_DIR.
Signed-off-by: Aníbal Limón
For match with the new structure of the OEQA framework.
In the new framework Test component base directory in this case
sdk module will contain case and context implementations.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
The functionality provided is the same with imporvements on code
reuse and better interfaces.
Signed-off-by: Aníbal Limón
---
meta/classes/testsdk.bbclass | 75 +++-
1 file changed, 60 insertions(+), 15 deletions(-)
diff
It doesn't make sense to have files related to sdk module into runtime
module.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/{runtime => sdk}/files/testsdkmakefile | 0
1 file changed, 0
Summary of the changes:
- Remove auto extend_path using pkgutil at __init__, is not needed.
- Change base class to OESDKTestCase.
- Add td_vars attr to set dependencies of certain variables in test
data.
- Change skips from module level to class level because Test context
(tc)
now isn't at
Don't use bitbake references inside utils modules, in order todo
that changes getVar calls for arguments in the __init__ method like
dl_dir for all the classes and testlogdir, builddatetime in
SDKBUildProject.
Also don't export proxies inside _download_archive method, a good
practice is to setup
Adds case and context modules for SDK based on oetest.py old code.
Enables SDK Test component usage with oe-test, the SDK Test component
adds command line options for specify sdk installed dir, sdk environment
and target/hosts maniftest.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
From: Mariano Lopez
The bitbake logger changes the way debug is logged and adds
different levels within debug, this is passed as argument
to the function and breaks compatibility with vanilla loggers.
This implements a way to handle this adding a new function for
Those files are used by runtime and sdk test cases, so move to
base directory of oeqa module.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/{runtime => }/files/test.c | 0
This function will generates testdata.json per SDK type.
[YOCTO #10231]
Signed-off-by: Aníbal Limón
---
meta/classes/populate_sdk_base.bbclass | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/meta/classes/populate_sdk_base.bbclass
The README has an introduction and explains how to run the test suite
and creates a new Test component.
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/README | 38
This function will generates testdata.json by image type.
[YOCTO #10231]
Signed-off-by: Aníbal Limón
---
meta/classes/rootfs-postcommands.bbclass | 18 ++
1 file changed, 18 insertions(+)
diff --git a/meta/classes/rootfs-postcommands.bbclass
The export2json function export the variables contained in
the data store to JSON format, the main usage for now will be
to provide test data to QA framework.
Signed-off-by: Aníbal Limón
---
meta/lib/oe/data.py | 28
1 file changed, 28
Serves as an first input of how to the OEQA framework works.
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/cases/__init__.py | 0
meta/lib/oeqa/core/cases/example/data.json | 1 +
The OETestContextExecutor class supports to use oe-test for run core
test component also is a base class for the other test components
(runtime, sdk, selftest).
Te principal functionality is to support cmdline parsing and execution
of OETestContext, the test components could extend the common
The OETestDataDepends decorator skips a test case if a variable
isn't into test data (d).
The skipIfDataVar decorator skips a test case if a variable
has certain value.
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
From: Mariano Lopez
The OETimeout provides support for specify certain timeout
in seconds for a test case, if the timeout is reach the SIGALRM
is sent and an exception is raised to notify the timeout.
[YOCTO #10235]
Signed-off-by: Mariano Lopez
The new oe-test script will be use to run test components with
one single script.
The oe-test script search for test components inside meta/lib/oeqa,
the test components needs to implement OETestContextExecutor inside
context module in order to be supported by oe-test.
[YOCTO #10230]
From: Mariano Lopez
This test suite covers the current functionality for the OEQA
framework.
For run certain test suite,
$ cd meta/lib/oeqa/core/tests
$ ./test_data.py
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
From: Mariano Lopez
These two decorators stores certain TAG or ID for the test case
also provides support for filtering in loading step.
[YOCTO #10236]
Signed-off-by: Mariano Lopez
Signed-off-by: Aníbal Limón
loader: Implements OETestLoader handling OETestDecorator
and filtering support when load tests. The OETestLoader is
responsible to set custom methods, attrs of the OEQA
frameowork.
[YOCTO #10231]
[YOCTO #10317]
[YOCTO #10353]
decorator: Add base class OETestDecorator to provide a common
way to
case: Defines OETestCase base class that provides custom
methods/attrs defined by the framework.
Every OETestCase instance contains a reference to the test
data (d), the test context (tc) and the logger.
Also implements _oe{SetUp,TearDown}Class for make special
handling of OEQA
The OETestDepends decorator could be used over test cases to
define some dependency between them.
At loading time sorting the tests to grauntee that a test case
executes before also raise an exception if found a circular
dependency between test cases.
At before test case run reviews if the
From: Mariano Lopez
misc: Functions for transform object to other types.
path: Functions for path handling.
test: Functions for operations related to test cases and suites.
[YOCTO #10232]
Signed-off-by: Mariano Lopez
Signed-off-by:
This patchset is related to OEQA Framework for details read the RFC send to the
Openembedded architecture ML.
http://lists.openembedded.org/pipermail/openembedded-architecture/2016-December/000351.html
Also adds the migration of the runtime testing leaving only selftest remains
to migrate.
The
Hi,
Some comments inline below (with oe-list this time),
Regards,
2017-01-20 17:23 GMT+01:00 Yannick GICQUEL :
> 2017-01-19 20:02 GMT+01:00 Andre McCurdy :
>> On Thu, Jan 19, 2017 at 7:01 AM, Yannick Gicquel
>> wrote:
>>>
On 01/20/2017 04:34 AM, Max Krummenacher wrote:
Hi
Can we backport the following commit to morty?
got it.
Thanks,
Armin
http://cgit.openembedded.org/openembedded-core/commit/?id=cb4f5ecf32006192baaf41218a3d7b43ca1c2951
It fixes pkgconfig to no longer report an old version.
Currently this
On Fri, 2017-01-20 at 15:12 +0100, Patrick Ohly wrote:
> Without this patch, linking fails with a missing implementation of
> yy_scan_string. This looks like a regression in flex, because 2.6.0 generated
> different code that called PrParser_scan_string
> resp. DtParser_scan_string.
>
> Working
On Fri, Jan 20, 2017 at 3:52 AM, Robert P. J. Day
wrote:
>
> the earlier note from ross i had totally forgotten about ...
>
> On Tue, 20 Dec 2016, Burton, Ross wrote:
>
> > FWIW I had a quick look at this. I'm certainly no perl guru and can
> > barely understand it, but
This code is already used in two places and we need it in others so
turn it into its own function.
Signed-off-by: Richard Purdie
---
meta/classes/utils.bbclass | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git
Currently the recipe depends on the mulitlib libcs all being built
but the dependencies don't account for this. Fix the DEPENDS so
that the requires pieces are all built first rather than relying on
luck.
Signed-off-by: Richard Purdie
---
== Series Details ==
Series: UEFI + Secure Boot + qemu (rev5)
Revision: 5
URL : https://patchwork.openembedded.org/series/4506/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
From: meta-luv
This is an unmodified copy of
github.com/01org/luv-yocto/meta-luv/recipes-core/ovmf revision
4be4329.
Signed-off-by: Patrick Ohly
---
meta/recipes-core/ovmf/ovmf/0001-BaseTools-Force-tools-variables-to-host-toolchain.patch
| 48
The magic detection of the rootfs parameter only worked for image
recipes which embedd the "image" string in the middle, as in
"core-image-minimal".
Sometimes it is more natural to call an image "something-image". To
get such an image detected by runqemu, "-image" at the end of a
parameter must
When booting a qemu virtual machine with ovmf.secboot, it comes up
with no keys installed and thus Secure Boot disabled. To lock down
the machine like a typical PC, one has to enroll the same keys
that PC vendors normally install, i.e. the ones from Microsoft.
This can be done manually (see
This patch was added to meta-luv for kernel testing purposes and
probably is not relevant for OE-core.
Signed-off-by: Patrick Ohly
---
meta/recipes-core/ovmf/ovmf/0001-OvmfPkg-Enable-BGRT-in-OVMF.patch | 110
In the simplest case, "runqemu qemux86 qcow2 ovmf" for an
EFI-enabled image in the qcow2 format will locate the ovmf.qcow2
firmware file deployed by the ovmf recipe in the image deploy
directory, override the graphics hardware with "-vga std" because that
is all that OVMF supports, and boot with
From: Fathi Boudra
qemu support for UEFI in OE-core depends on OVMF, which needs the iasl
tools provided by this recipe. There's also an iasl recipe in
meta-luv, but than can and will be replaced by this one, thus reducing
overall maintenance work.
Copied from
When used with '-drive if=pflash', qemu will store UEFI variables
inside the firmware image file. That is unexpected for a file located in
the sysroot, which should be read-only, while it is normal for image
files in the deploy/images directory. Therefore that directory is a
better place for use
1 - 100 of 142 matches
Mail list logo