Nikita Kalyazin

Thanks for the suggestion. Am I understand right, that you propose to solve this problem on a higher level, i.e., to map a sequence to a single key (using 3rd...

Ok, thanks.

Hi, I tried out autokey. It doesn't look like the way to go for me, since: - it doesn't support "key chaining" (https://code.google.com/p/autokey/issues/detail?id=138); - ctrl+alt and ctrl+g combinations (the crucial...

Hi @mmcclean-aws . Like discussed offline, an immediate obstacle for supporting Inferentia and Trainium instances is that they are virtualised (as opposed to bare metal), so Firecracker can't run on...

Hi @peterdelevoryas . What is your specific motivation for moving off Qemu? Is that merely because of the Rust safety features? Firecracker was developed with CPU workloads in mind, and...

Hi @sargun . Thanks for contacting us! We investigated running Firecracker using Core Scheduling on a host with SMT enabled. Our results show that the performance gains/degradations are very workload-dependent,...

Hi @dtouzeau . Thanks for the enquiry. Detaching from the controlling terminal is a part of the daemonization procedure, so it is expected that VM's serial console is not accessible....

Hi @majek. While considering support for vhost-net in Firecracker, we would like to gain confidence in the following areas. > over the years vhost-net matured, the implementation strengthened One of...

Hi @Noah-Kennedy . The path we would like to follow at the moment for the cases similar to this one is: - keep a single API endpoint for all devices...

Hi @Noah-Kennedy . There is a draft PR for adding a vhost-user block device: https://github.com/firecracker-microvm/firecracker/pull/4069 . Please let us know if a similar approach is not easily applicable to the...