From 49694b79b866560d7534e8dcc95b79f5c087efed Mon Sep 17 00:00:00 2001
From: Beket <Beket@web>
Date: Tue, 12 May 2009 00:47:08 -0700
Subject: [PATCH] Mention -n1 option in vkernel

---
 docs/howtos/HowToDebugVKernels/index.mdwn | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/howtos/HowToDebugVKernels/index.mdwn b/docs/howtos/HowToDebugVKernels/index.mdwn
index a03e004e..08b6853e 100644
--- 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.
+
-- 
2.41.0