[Bug 2022312] Re: Adding IA32 to X64 pkg, because secure boot is not working on Focal

[Seyeong Kim]

I updated description as with simple test result.

** Description changed:

  [Impact]
  
  In Focal, secureboot is not working ( black screen right after instance
  is started )
  
  [Test Case]
  0. create custom image with cirros
  - openstack image create --container-format bare --disk-format qcow2 --file cirros-0.5.1-x86_64-disk.img cirros
  1. set image properties.
  - $ openstack image set --property hw_machine_type=q35 --property hw_firmware_type=uefi --property os_secure_boot=required cirros
  2. In focal, create instance, and enable secureboot
  3. start instance.
  4. you just can see only blackscreen.
  
  [Where problems could occur]
  Secureboot may have issue.
  
  [Others]
  For Jammy, it is ok
  
  instance xml
  - https://pastebin.ubuntu.com/p/MnK6nx3vwy/
+ 
+ 
+ #ADDED
+ Testing
+ 1. Prepared cirros and cirros2 image
+ 2. only set secure boot parameters to cirros image
+ 3. launch instances 
+ - instance with cirros image
+ - instance with cirros2 image
+ 4. test result
+ - booting cirros instance doesn't work(black screen) with original OVMF_CODE_4M.secboot.fd
+ - booting cirros instance does work(shows uefi prompt) with patched OVMF_CODE_4M.secboot.fd
+ - booting cirros2 instance either cases.

** Description changed:

  [Impact]
  
  In Focal, secureboot is not working ( black screen right after instance
  is started )
  
  [Test Case]
- 0. create custom image with cirros
+ 0. juju bundle for focal-yoga openstack env
+ - https://pastebin.ubuntu.com/p/G38JwXMX5G/
+ 1. create custom image with cirros
  - openstack image create --container-format bare --disk-format qcow2 --file cirros-0.5.1-x86_64-disk.img cirros
- 1. set image properties.
+ 2. set image properties.
  - $ openstack image set --property hw_machine_type=q35 --property hw_firmware_type=uefi --property os_secure_boot=required cirros
- 2. In focal, create instance, and enable secureboot
- 3. start instance.
- 4. you just can see only blackscreen.
+ 3. In focal, create instance, and enable secureboot
+ 4. start instance.
+ 5. you just can see only blackscreen.
  
  [Where problems could occur]
  Secureboot may have issue.
  
  [Others]
  For Jammy, it is ok
  
  instance xml
  - https://pastebin.ubuntu.com/p/MnK6nx3vwy/
  
- 
  #ADDED
  Testing
  1. Prepared cirros and cirros2 image
  2. only set secure boot parameters to cirros image
- 3. launch instances 
+ 3. launch instances
  - instance with cirros image
  - instance with cirros2 image
  4. test result
  - booting cirros instance doesn't work(black screen) with original OVMF_CODE_4M.secboot.fd
  - booting cirros instance does work(shows uefi prompt) with patched OVMF_CODE_4M.secboot.fd
  - booting cirros2 instance either cases.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/2022312

Title:
  Adding IA32 to X64 pkg, because secure boot is not working on Focal

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive yoga series:
  New
Status in edk2 package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Invalid
Status in edk2 source package in Focal:
  Won't Fix
Status in nova source package in Focal:
  Invalid
Status in edk2 source package in Jammy:
  Fix Released
Status in nova source package in Jammy:
  Invalid

Bug description:
  [Impact]

  In Focal, secureboot is not working ( black screen right after
  instance is started )

  [Test Case]
  0. juju bundle for focal-yoga openstack env
  - https://pastebin.ubuntu.com/p/G38JwXMX5G/
  1. create custom image with cirros
  - openstack image create --container-format bare --disk-format qcow2 --file cirros-0.5.1-x86_64-disk.img cirros
  2. set image properties.
  - $ openstack image set --property hw_machine_type=q35 --property hw_firmware_type=uefi --property os_secure_boot=required cirros
  3. In focal, create instance, and enable secureboot
  4. start instance.
  5. you just can see only blackscreen.

  [Where problems could occur]
  Secureboot may have issue.

  [Others]
  For Jammy, it is ok

  instance xml
  - https://pastebin.ubuntu.com/p/MnK6nx3vwy/

  #ADDED
  Testing
  1. Prepared cirros and cirros2 image
  2. only set secure boot parameters to cirros image
  3. launch instances
  - instance with cirros image
  - instance with cirros2 image
  4. test result
  - booting cirros instance doesn't work(black screen) with original OVMF_CODE_4M.secboot.fd
  - booting cirros instance does work(shows uefi prompt) with patched OVMF_CODE_4M.secboot.fd
  - booting cirros2 instance either cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2022312/+subscriptions