Hi, > For microvm that's simply not worth it. Fiddling with the command line > achieves the same result without any significant drawbacks, Assuming you actually can fiddle with the command line, which is only the case with direct kernel boot. > > To fix that the firmware must be able to find the virtio-mmio devices. > > No FW supports modern virtio-mmio transports anyway. Well, we change that if we want ... > And, from microvm's perspective, there's little incentive to change > this situation, given that it's main use cases (serverless computing > and VM-isolated containers) will run with an external kernel. If direct kernel boot is the only use case microvm ever wants support, then there is little reason to go the extra mile for optional seabios support. cheers, Gerd
