On 06/05/2020, Roman Kagan wrote:
On Wed, May 06, 2020 at 07:49:29AM +0300, Jon Doron wrote:
Thanks Roman, I see your point, it's important for me to get the EDK2
working properly not sure why it's not working for me.
As I wrote a good deal of that code I hope I should be able to help (and
I'd be interested, too). How exactly does the "not working" look like?
Basically when I built the BIOS from the hv-scsi branch you pointed me
out to, the BIOS did not see the virtio-blk device to boot from, I
usually take the BIOS from (https://www.kraxel.org/repos/) but I will
try to build the latest EDK2 and see if it identifies the virtio-blk
device and boots from it, if that's the case perhaps i just need to
rebase your branch over the latest master of EDK2.
Also I'm a bit confused as to why UEFI is critical for the work you're
doing? Can't it be made to work with BIOS first?
The reason I want to have the UEFI option is because I need SecureBoot
to turn on VBS.
Do you know by any chance if the EDK2 hyperv patches were submitted and if
they were why they were not merged in?
I do, as I'm probably the only one who could have submitted them :)
No they were not submitted. Neither were the ones for SeaBIOS nor iPXE.
The reason was that I had found no way to use alternative firmware with
HyperV, so the only environment where that would be useful and testable
was QEMU with VMBus. Therefore I thought it made no sense to submit
them until VMBus landed in QEMU.
Thanks,
Roman.
Heh I see, well I'm really happy that you are here helping so we can try
and finally add VMBus to QEMU, I realize it's a big effort but I'm
willing to spend the time and do the required changes...
I'm working this only during my free time so things takes me longer than
usual (sorry for that..)
I will keep update on results once I get to test with latest EDK2 :)
Thanks,
-- Jon.
