| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Refactor the efi-secure-boot feature (in order for it to be
disabled for certain targets)
* Add support for emag8180 compilation target (used as Enea NFV Access host)
* Add emag8180 support in ostree
* Add support for qemuarm64 compilation target (used as Enea NFV Access VNF)
Note:
The aarch64 family does not support the secure-boot feature yet, so the
"efi-secure-boot" has been disabled.
Change-Id: I32336761d322102a07d065c9ab02ea5051854609
Signed-off-by: Adrian Stratulat <adrian.stratulat@enea.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The block device name(sda,sdb,vda,..) from guest/VNF is dependent on
the way of how qemu mounts the qcow2: HDD, virtio,...
In order to avoid mount issues in guest/VNF the partition UUID
must be used whenever is possible.
Explicitly set the partition type according to doc:
https://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
| |
|
|
|
| |
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
Signed-off-by: Martin Borg <martin.borg@enea.com>
|
|
|
image-vm/qcow2 bbclass was removed from poky and replaced
with wic.qcow2. For this solution we need a customer wks file.
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
