Mention -n1 option in vkernel

diff --git a/docs/howtos/HowToDebugVKernels/index.mdwn b/docs/howtos/HowToDebugVKernels/index.mdwn
index a03e004..08b6853 100644 (file)
--- a/docs/howtos/HowToDebugVKernels/index.mdwn
+++ b/docs/howtos/HowToDebugVKernels/index.mdwn
@@ -225,3 +225,6 @@ a state where the vkernel is in state "stop" and the vkernel is in "wait", and n
 The only help is to kill gdb, which either makes the vkernel run again, or kills it as well.
 
 See also [this bug report](http://bugs.dragonflybsd.org/issue1301).
+
+Experience has shown that running vkernel with -n1, that is telling it to emulate only 1 CPU, alleviates thes issue.
+