One of the most requested features is now included. You can instruct the boot tester to simulate hardware failures:
qbt inject-fault --vm my_vm --type disk_latency --delay 500ms
This tests how your boot scripts behave when the root filesystem responds slowly.
The syntax for the main executable is:
./qbt-exec [options] --target <path_to_iso> qemu boot tester 4.0
Let’s run through a typical scenario: You have just patched the virtio-blk driver, and you need to ensure the kernel still boots on an ARM64 VM.
To test a new OS, you usually need a custom profile. The most critical step is identifying the Success String. One of the most requested features is now included
Step 1: Find the Success String
Boot the OS manually with --verbose and watch the serial output. Look for the very last unique line printed before the login prompt appears.
Step 2: Define Hardware If testing a heavy OS (like Windows), increase RAM. This tests how your boot scripts behave when
hardware:
ram_mb: 4096
cpus: 4
Step 3: Define Firmware If testing modern Linux or Windows, use UEFI.
hardware:
firmware: "uefi"
secure_boot: false # QBT 4.0 supports Secure Boot emulation testing