On Saturday, January 5, 2019 at 2:58:14 AM UTC-5, Pekka Enberg wrote: > > > > On Sat, Jan 5, 2019 at 9:43 AM Waldek Kozaczuk <[email protected] > <javascript:>> wrote: > >> Indeed I have come across some incompatibility issues. Mostly around >> configuration but nothing very fundamental. You can see in some of my >> comments. >> > > Right, I missed the comments because the diff is somewhat large. ;-) > > I would suggest to do Firecracker support in the following (largely > independent) steps: > > - Add support for modern virtio interfaces. Linux has a split driver base > model here, which we could also follow. I.e., have separate VirtioModern > and VirtioLegacy base classes that encapsulate the differences. > > - Add support for VirtIO MMIO. Most of this is restructuring the drivers > to use transport-independent interfaces and then have VirtioPCI and > VirtioMMIO classes that implement transport-specific logic. > > - Add Intel mptable (used by Firecracker) support as an alternative to > ACPI hardware discovery. > > - Add any misc Firecraker related things that are still needed to make OSv > boot and run. > > - Pekka >
I like your suggestion. The extra thing would be adjusting OSv to support Linux boot protocol which would be also handy to run it on hyperkit or bhyve. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
