Closed bootrino closed 2 years ago
This happened because I had not run:
sudo setfacl -m u:${USER}:rw /dev/kvm
Suggestion to project - a good error message suggesting this might be the cause instead of crashing.
More detail in the associated pull request. The TL;DR is the issue was easily reproducible. Instead of terminating the FC process, FC will log a more precise log message if the InstanceStart
API call fails to bootstrap the KVM device. The process will be left running to try the API call again after the /dev/kvm
ACL has been updated.
I'm following this tutorial but I am also trying to do networking: https://aws.amazon.com/blogs/aws/firecracker-lightweight-virtualization-for-serverless-computing/
To do networking, I added the script below: 3_config_guest_network.sh
When I follow the tutorial without script 3_config_guest_network.sh the virtual machine starts OK.
When I run the script below 4_start_guest_machine.sh firecracker crashes with:
1_set_guest_kernel.sh
2_set_root_guestfs.sh
3_config_guest_network.sh
4_start_guest_machine.sh
### This is my network configuration:
/etc/systemd/network/31-tap1.netdev
/etc/systemd/network/31-tap1.network
/etc/systemd/network/br0.netdev
/etc/systemd/network/br0.network
/etc/systemd/network/eth0.network
andrewstuart@homecloud:~$ networkctl status -a