-
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::…
-
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
-
The CRI-O tests are not working with rust agent, here it is the example
```
not ok 2 ctr termination reason Completed
# (in test file ctr.bats, line 28)
# `[ "$status" -eq 0 ]' failed
# time="2…
-
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: zyfjeff
-
This will be added in [rust-vmm](https://github.com/rust-vmm/kvm-ioctls).
-
GitHub Username: stefano-garzarella
-
GitHub Username: bonzini
I would like to be able to close issues, assign them to myself etc.