-
This problem was hidden because we weren't checking the result of `device_fd.set_device_attr(&dist_attr)`.
Output:
```
---- ioctls::device::tests::test_create_device stdout ----
thread 'ioctls::…
-
I've observed a few times that when starting CH with --console off and --serial off (and console hvc0 as only console related kernel parameter) CH cpu load goes to 100 % and the boot process is stuck …
-
This issue depends on https://github.com/rust-vmm/kvm-ioctls/issues/7.
Check status on [rust-vmm/kvm-ioctls](https://github.com/rust-vmm/kvm-ioctls)
-
If for any reason *other than stack overflow* Firecracker gets a `SIGSEGV` or `SIGBUS`, the signal handler [installed by Rust](https://github.com/rust-lang/rust/blob/1.32.0/src/libstd/sys/unix/stack_o…
-
GitHub Username: ChrisMacNaughton
-
Currently Firecracker doesn't run on the RPi3 with KVM enabled.
Here are the details, when I’m starting Firecracker (did used the binary from GitHub releases) on arm64 I did get the following error…
-
GitHub Username: zyfjeff
-
This will be added in [rust-vmm](https://github.com/rust-vmm/kvm-ioctls).
-
So I am running the SDK for Firecracker in Docker and noticed that Firecracker exits with 148 and with the error message `Shutting down VM after intercepting a bad syscall (288)`. Which is confusing t…
-
GitHub Username: stefano-garzarella