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 connectivity between hosts which is typically already given. Native Routing: Use of the regular routing table of the Linux host. The network is required to be capable to route the IP addresses of the application

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 connectivity between hosts which is typically already given. Native Routing: Use of the regular routing table of the Linux host. The network is required to be capable to route the IP addresses of the application

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 connectivity between hosts which is typically already given. Native Routing: Use of the regular routing table of the Linux host. The network is required to be capable to route the IP addresses of the application

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 connectivity between hosts which is typically already given. Native Routing: Use of the regular routing table of the Linux host. The network is required to be capable to route the IP addresses of the application

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 connectivity between hosts which is typically already given. Native Routing: Use of the regular routing table of the Linux host. The network is required to be capable to route the IP addresses of the application following command displays the set of available Kubernetes versions. az aks get-versions -l westus -o table Create an AKS Cluster You can use any method to create and deploy an AKS cluster with the exception

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 connectivity between hosts which is typically already given. Native Routing: Use of the regular routing table of the Linux host. The network is required to be capable to route the IP addresses of the application following command displays the set of available Kubernetes versions. az aks get-versions -l westus -o table Create an AKS Cluster You can use any method to create and deploy an AKS cluster with the exception

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 connec�vity between hosts which is typically already given. Na�ve Rou�ng: Use of the regular rou�ng table of the Linux host. The network is required to be capable to route the IP addresses of the applica�on tables. With Cassandra, each table belongs to a “keyspace”, allowing mul�ple groups to use a single cluster without conflic�ng. Cassandra queries specify the full table name qualified by the keyspace