Comment 6 for bug 1821729

@Dann: thanks for checking that, I did some tests and, even if I can't reproduce the kernel panic anymore, I'm seeing another issue that was also happening before with virtio, the vm is not booting on ipxe.

This is the correct output on bionic using virtio + ovmf from xenial:
http://logs.openstack.org/87/647687/5/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/a16650a/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-03-27-14:18:35_log.txt.gz

This is a test done with virtio and the new package on bionic:
http://logs.openstack.org/07/645507/7/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/2660087/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-04-01-09:57:23_log.txt.gz

This is the output changing the driver to e1000 and using the default rom on bionic:
http://logs.openstack.org/38/648938/1/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/c943520/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-04-01-11:01:55_log.txt.gz

This is the output using e1000 driver using the rom from ipxe-qemu on bionic:
http://logs.openstack.org/38/648938/2/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/1c53407/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-04-01-13:15:39_log.txt.gz

I reproduced all the tests locally to confirm, also changing ipxe-qemu from bionic to xenial to understand if it was a regression in that package, but it didn't work, so I think this is another problem in recent versions of ovmf.