diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
index 9e4551be1c..e5aeffcffb 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
@@ -856,6 +856,56 @@
+ BB_TASK_IONICE_LEVEL
+
+
+ Allows adjustment of a task's Input/Output priority.
+ During Autobuilder testing, random failures can occur
+ for tasks due to I/O starvation.
+ These failures occur during various QEMU runtime timeouts.
+ You can use the BB_TASK_IONICE_LEVEL
+ variable to adjust the I/O priority of these tasks.
+
+ This variable works similarly to the
+ BB_TASK_NICE_LEVEL
+ variable except with a task's I/O priorities.
+
+
+
+
+ Set the variable as follows:
+
+ BB_TASK_IONICE_LEVEL = "class.prio"
+
+ For class, the default value is
+ "2", which is a best effort.
+ You can use "1" for realtime and "3" for idle.
+ If you want to use realtime, you must have superuser
+ privileges.
+
+
+
+ For prio, you can use any
+ value from "0", which is the highest priority, to "7",
+ which is the lowest.
+ The default value is "4".
+ You do not need any special privileges to use this range
+ of priority values.
+
+ In order for your I/O priority settings to take effect,
+ you need the Completely Fair Queuing (CFQ) Scheduler
+ selected for the backing block device.
+ To select the scheduler, use the following command form
+ where device is the device
+ (e.g. sda, sdb, and so forth):
+
+ $ sudo sh -c “echo cfq > /sys/block/device/queu/scheduler
+
+
+
+
+
+
BB_TASK_NICE_LEVEL