Add support for firecracker in addition to QEMU as a supported hypervisor in Kata.

[mcastelino]

Add support for firecracker in addition to QEMU as a supported hypervisor in Kata.

This will require a few changes and additions to Kata components

Runtime

• Making multiqueue optional for network interfaces network: Don't assume multiple queues support #1027
• Supporting gRPC based copy of files from host to VM - Copy files from host to guest #1041
• actual implementation of the hypervisor interface (fc.go) Firecracker VMM support #1044
• Adding support to boot from disk (vs nvdimm or initramfs)
• Adding support for virtio-mmio type devices Firecracker: virtio mmio support #1045
• Add hypervisor configuration table for Firecracker - Add firecracker as a supported hypervisor configuration #1042

Kernel

• Updating the Kata kernel configuration
  Firecracker support: Add support for virtio-mmio packaging#272

Packaging

• Packaging of the rootfs as a disk in a firecracker friendly format
  This is no longer needed. Add support for firecracker in addition to QEMU as a supported hypervisor in Kata. #1031 (comment)
• Supporting a debug console over vsock (to aid debugging)

Agent

• Adding support for virtio-mmio type devices in the runtime virtio-mmio: Add support for virtio-mmio blk devices agent#437
• Supporting gRPC based copy of files from host to VM
  protocols/grpc: implement function to copy files agent#433

[WeiZhang555]

+1 !

[Weichen81]

@mcastelino Would you consider to keep compatibility of aarch64 while you're adding the firecracker support? Or your first target is just to enable x86_64? @Pennyzct

[egernst]

@Weichen81 - this would be adding an additional hypervisor (firecracker) to Kata; we'd still keep and definitely maintain QEMU/NEMU support. So, we'd remain compatible, and depending on the type of workload and infrastructure you're running on, you'd pick the appropriate hypervisor.

[Weichen81]

@egernst Hi Eric, I meant should we have firecracker_amd64.go and firecracker_aarch64.go at the same time in this issue, or we just start from firecracker_amd64.go first : )

[mcastelino]

Firecracker currently supports Intel CPUs, with planned AMD and Arm support. Once we have support for other architectures we should add them. On Dec 17, 2018, at 8:58 PM, Wei Chen <notifications@github.com<mailto:notifications@github.com>> wrote: @egernst<https://github.com/egernst> Hi Eric, I meant should we have firecracker_amd64.go and firecracker_aarch64.go at the same time in this issue, or we just start from firecracker_amd64.go first : ) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#1031 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHC6WRZy4u8rvaqP2JnU2hF_Nff2xQZDks5u6HX7gaJpZM4ZUe99>.

[Pennyzct]

Very happy to offer any help when we have support for aarch64. ;)

[mcastelino]

Packaging of the rootfs as a disk in a firecracker friendly format

This work item is no longer needed. The rootfs can be added as a regular block device. The root can be explicitly specified vs implicitly added by firecracker itself.

https://github.com/mcastelino/fireclient/blob/noroot/instance.go#L126

https://github.com/mcastelino/fireclient/blob/noroot/instance.go#L92

This will allow us to use the same "partitioned" rootfs we use in the case of NVDIMM.

This means we can use the same image for both cases. All we need is the updated agent that supports virtio-mmio.

/cc @sboeuf @egernst