Oh yes!! Good point!!!
```
--- a/libvirt/tests/src/virsh_cmd/domain/virsh_domfstrim.py
+++ b/libvirt/tests/src/virsh_cmd/domain/virsh_domfstrim.py
@@ -153,9 +153,17 @@ def run_virsh_domfstrim(test, params, env):
             if is_fulltrim == "yes":
                 return empty_limit == ori_limit
             else:
-                return empty_limit <= full_limit
+                # Verify the result after timeout if it is not full trim.
+                return False
 
         if not utils_misc.wait_for(_trim_completed, timeout=30):
+            if not is_fulltrim == "yes":
+                # Verify the result here.
+                empty_diskmap = commands.getoutput(map_cmd).strip('\n\x00')
+                empty_limit = int(empty_diskmap.split(",")[-1].split("-")[-1])
+                if empty_limit <= full_limit:
+                   # Test pass if empty <= full after a timeout of triming
+                   return 
             raise error.TestFail("error message.")
 
     finally:
```
This patch will cover this scenario. About this timeout, what do you think we need to set it? I have not very much practise about it.
And about the 7130316, could you give us some comment for it?? why is 7130316? and does it means that ignore the all blocks in guest. So can I say that when I use domfstrim with --minimum 7130316, the empty_limit will be equal with full_limit??