Comment 5 for bug 1885662
Revision history for this message
| Dimitri John Ledkov (xnox) wrote Re: bump the size of nvram VARS.fd | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
2MB builds no longer suitable for Secureboot, as the nvram space is now too small to remain secure. The next dbxupdate is larger than what fits in NVRAM of the 2MB firmware.
The 4MB and 2MB are incompatible with respect to VARS. The VM boots with 4MB code and "old" VARS, but the efivars state is all wrong. Instead of secureboot on, it's secureboot off.
We must add 4MB flavour, and add it to qemu. Going with similar names as SUSE i guess is helpful.
Ideally somehow order 4MB flavour "first" such that e.g. launching new VMs uses 4MB firmwares.
I wish we could drop 2MB firmwares somehow.