>-----Original Message-----
>From: Jan Kiszka <[email protected]>
>Sent: 28 July 2022 14:22
>To: pyla venkata(TSIP TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>tsip.com>; [email protected]
>Cc: dinesh kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@toshiba-
>tsip.com>; hayashi kazuhiro(林 和宏 □SWC◯ACT)
><[email protected]>
>Subject: Re: Want to understand why the num-config-parts is defaults to 2
>
>On 27.07.22 20:00, [email protected] wrote:
>> Hi,
>>
>> My name is venkata and I am working with ISAR and CIP projects.
>> I am using efibootguard for secure boot verification in QEMU,
>>
>> I have some questions on efibooguard compilation, please help me to
>understand,
>>
>> When I am using single EFI partition in my system image (not observed that
>efibootguard is compiled with default 2 config-partitions), the efibootguard is
>failed to load the configuration and doesn’t boot.
>>
>> After I recompile the efibootguard with "--with-num-config-parts=1" then it
>worked well.
>>
>> I just wanted to understand the reason for setting the "num-config-parts"
>defaults to 2 [1], does it expects minimum of two efi partitions for some 
>reason
>(swupdate?) that I should care about.
>>
>> Also, do I need to compile efibootguard always when I use it for different
>partitions (2 for swupdate, 1 for single efi partition) or can I configure 
>this on
>runtime?
>>
>> [1] https://github.com/siemens/efibootguard/blob/master/configure.ac#L153
>>
>
>The main purpose of EFI Boot Guard is providing a robust a/b boot path
>switching mechanism. Therefore, 2 config partitions is the most
>reasonable default. You could have more partitions, but we didn't hit a
>real use case for that yet. You may disable the switching feature and
>only use EFI Boot Guard as watchdog driver, but that is a special case.
>Therefore, 2 is default and will also be the setting in a pre-built
>distro package.
>
Hi Jan,

Thanks for the explanation, I think there is an issue in v0.11, 
when efibootugard is compiled with 2 config partitions and system has single 
efi partition then during boot it is failing to load the efi configuration,

here is the error during boot:
=====================================================
Loading configuration...
Config file found on volume 0.
1 config partitions detected.
Config filter:
Booting with environments from boot medium only.
WARNING: Too few config partitions: found: 1, but expected 2.
Config Revision: -1347440721:
 ustate: 175
 kernel: ?????????????????????????????????????????????????????????
 
[removed the junk characters]

 timeout: 44975 seconds
WARNING: Config is partially corrupted. Please check.
=====================================================

this issue is not observed in v0.10, so checked the history and found that it 
is because of the below patch. 
https://github.com/siemens/efibootguard/commit/77c44523eb6068ae1b4c80fb58e9d6cce58784b1

I fixed internally this problem and I will send the patch in another mail.

Thanks 

>Jan
>
>--
>Siemens AG, Technology
>Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups "EFI 
Boot Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/efibootguard-dev/OSYPR01MB5542E0DC6393E86B3DBDC8E8A4969%40OSYPR01MB5542.jpnprd01.prod.outlook.com.

Reply via email to