Debugging the BPF Virtual Machine Lorenzo Fontana October 28, 2020 ● Debugging is useful to understand how things work ● Sometimes, eBPF programs can’t even load ● I couldn’t find good resources on this this, so, here I am ● I break lots of eBPF programs ● The BPF Virtual machine is not easy to understand Why ? The BPF subsystem lives in the kernel AND The kernel can be debugged using gdb The

well-equipped to handle modern containerized workloads as well as more traditional workloads such as virtual machines and standard Linux processes. The development of modern datacenter applications has shifted hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts. Currently VXLAN and Geneve are baked in but all encapsulation formats combination with aws-cni. In this hybrid mode, the aws-cni plugin is responsible for setting up the virtual network devices as well as address allocation (IPAM) via ENI. After the initial networking is setup

well-equipped to handle modern containerized workloads as well as more traditional workloads such as virtual machines and standard Linux processes. The development of modern datacenter applications has shifted hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts. Currently VXLAN and Geneve are baked in but all encapsulation formats combination with aws-cni. In this hybrid mode, the aws-cni plugin is responsible for setting up the virtual network devices as well as address allocation (IPAM) via ENI. After the initial networking is setup

well-equipped to handle modern containerized workloads as well as more traditional workloads such as virtual machines and standard Linux processes. The development of modern datacenter applications has shifted hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts. Currently VXLAN and Geneve are baked in but all encapsulation formats AWS VPC CNI plugin. In this hybrid mode, the AWS VPC CNI plugin is responsible for setting up the virtual network devices as well as for IP address management (IPAM) via ENIs. After the initial networking

well-equipped to handle modern containerized workloads as well as more traditional workloads such as virtual machines and standard Linux processes. The development of modern datacenter applications has shifted hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts. Currently VXLAN and Geneve are baked in but all encapsulation formats AWS VPC CNI plugin. In this hybrid mode, the AWS VPC CNI plugin is responsible for setting up the virtual network devices as well as for IP address management (IPAM) via ENIs. After the initial networking

hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts. Currently VXLAN and Geneve are baked in but all encapsulation formats combination with aws-cni. In this hybrid mode, the aws-cni plugin is responsible for setting up the virtual network devices as well as address allocation (IPAM) via ENI. After the initial networking is setup combination with Azure CNI. In this hybrid mode, the Azure CNI plugin is responsible for setting up the virtual network devices as well as address allocation (IPAM). After the initial networking is setup, the

hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts. Currently VXLAN and Geneve are baked in but all encapsulation formats combination with aws-cni. In this hybrid mode, the aws-cni plugin is responsible for setting up the virtual network devices as well as address allocation (IPAM) via ENI. After the initial networking is setup combination with Azure CNI. In this hybrid mode, the Azure CNI plugin is responsible for setting up the virtual network devices as well as address allocation (IPAM). After the initial networking is setup, the

between hosts. The following mul� node networking models are supported: Overlay: Encapsula�on based virtual network spawning all hosts. Currently VXLAN and Geneve are baked in but all encapsula�on formats pre-defined naming schema {clustername}.mesh.cilium.io . In order for DNS resolu�on to work on these virtual host name, the names are sta�cally mapped to the service IP via the /etc/hosts file. The following llvm.org/] and passes them to the Linux kernel to run for all packets in / out of the container’s virtual ethernet device(s). Cilium CLI Client The Cilium CLI Client (cilium) is a command-line tool that