Long-Term Supported Versions

    Innovation Versions

      Usage

      NIC Configuration

      # Change the MTU of the NIC.
      ifconfig ens33  mtu 4200
      
      # Add an RXE interface to ens33 for the IB function.
      rdma link add rxe_0 type rxe netdev ens33
      

      Application Development

      Use relevant APIs to develop a scenario-specific application. Build the application as a binary ELF file based on the eBPF instruction set. Take vm_migrate of the provided ebpf_example for example. vm_migrate calls the CTinspector framework and can migrate package VMs between nodes in a resumable manner.

      # Compose the Makefile and set the eBPF instruction set.
      
      CFLAGS=-O2 -fno-inline -emit-llvm -I/usr/include/ctinspector/
      LINKFLAGS=-march=bpf -filetype=obj
      
      all: vm_migrate.o 
      
      vm_migrate.o:
          clang $(CFLAGS) -c migrate.c -o - | llc $(LINKFLAGS) -o vm_migrate.o
      
      clean:
          rm -f vm_migrate.o
      
      # Run make to build the application.
      make
      clang -O2 -fno-inline -emit-llvm -I/usr/include/ctinspector/ -c migrate.c -o - | llc -march=bpf -filetype=obj -o vm_migrate.o
      

      Application Running

      Running vm_migrate on node 1.

      Running the CTinspector main program on node 2.

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.

      PR

      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.

      Usability

      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.

      Correctness

      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Submit
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份