diff --git a/docs/en/guide/oneclickvirt/images/iofailed.png b/docs/en/guide/oneclickvirt/images/iofailed.png
new file mode 100644
index 0000000000..768338d7b9
Binary files /dev/null and b/docs/en/guide/oneclickvirt/images/iofailed.png differ
diff --git a/docs/en/guide/oneclickvirt/oneclickvirt_qa.md b/docs/en/guide/oneclickvirt/oneclickvirt_qa.md
index 5000f51a14..9a0d99d3ba 100644
--- a/docs/en/guide/oneclickvirt/oneclickvirt_qa.md
+++ b/docs/en/guide/oneclickvirt/oneclickvirt_qa.md
@@ -68,4 +68,27 @@ Execute
 docker volume rm oneclickvirt-data oneclickvirt-storage oneclickvirt-config
 ```
 
-to delete
\ No newline at end of file
+to delete
+
+## Excessive Instance Creation Causes Node Abnormalities
+
+A prominent symptom is extremely slow operation execution, with commands taking several minutes to complete.
+
+This commonly occurs when a node has poor I/O performance and is over-allocated with SWAP memory.
+For example, in an LXD environment, executing ```lxc list``` may result in an error:
+
+```shell
+internal error, please report: running “lxd.lxc” failed: cannot create transient scope: DBus error “org.freedesktop.DBus.Error.TimedOut”: [Failed to activate service ‘org.freedesktop.systemd1’: timed out (service_start_timeout=25000ms)]
+```
+
+The root cause is setting too many instances while the provider imposes strict I/O restrictions.
+
+![](./images/iofailed.png)
+
+At this point, only one solution remains: force-reboot the node server.
+
+Immediately after reboot, log into SSH and use the corresponding script to clear swap usage, then delete some instances to free resources.
+
+Since containers take time to restart individually after reboot, this window may not delete many instances, but each reboot clears some.
+
+Ultimately, when limiting instance counts, carefully assess node performance. Avoid overloading weaker nodes or those with strict constraints.
\ No newline at end of file
diff --git a/docs/guide/oneclickvirt/images/iofailed.png b/docs/guide/oneclickvirt/images/iofailed.png
new file mode 100644
index 0000000000..768338d7b9
Binary files /dev/null and b/docs/guide/oneclickvirt/images/iofailed.png differ
diff --git a/docs/guide/oneclickvirt/oneclickvirt_install.md b/docs/guide/oneclickvirt/oneclickvirt_install.md
index 19ec557281..29e64a3fa4 100644
--- a/docs/guide/oneclickvirt/oneclickvirt_install.md
+++ b/docs/guide/oneclickvirt/oneclickvirt_install.md
@@ -58,7 +58,7 @@ https://github.com/oneclickvirt/oneclickvirt/pkgs/container/oneclickvirt
 
 所有镜像均支持 `linux/amd64` 和 `linux/arm64` 架构。
 
-##### 全新环境下部署
+##### 全新部署
 
 使用已构建好的```amd64```或```arm64```镜像，会自动根据当前系统架构下载对应版本：
 
@@ -91,7 +91,7 @@ docker run -d \
 
 以上的方式仅限于新安装
 
-##### 旧有环境下仅升级前后端
+##### 旧环境下仅升级
 
 先备份配置文件到当前路径下：
 
@@ -125,7 +125,7 @@ docker pull spiritlhl/oneclickvirt:latest
 docker cp config.yaml oneclickvirt:/app/config.yaml
 ```
 
-##### 旧有环境下重新部署
+##### 旧环境下新部署
 
 这将完全删除原有数据再部署，不仅需要删除容器还得删除对应的挂载点：
 
diff --git a/docs/guide/oneclickvirt/oneclickvirt_qa.md b/docs/guide/oneclickvirt/oneclickvirt_qa.md
index 098d50a256..ad532535ae 100644
--- a/docs/guide/oneclickvirt/oneclickvirt_qa.md
+++ b/docs/guide/oneclickvirt/oneclickvirt_qa.md
@@ -69,3 +69,27 @@ docker volume rm oneclickvirt-data oneclickvirt-storage oneclickvirt-config
 ```
 
 进行删除
+
+## 开设实例过多导致节点异常
+
+一个显著的现象是执行操作极其缓慢，甚至几分钟都执行不完毕一个命令
+
+一般常见于节点的IO比较差，此时又开了很多SWAP超配内存
+
+比如lxd环境下，执行```lxc list```会报错
+
+```shell
+internal error, please report: running “lxd.lxc” failed: cannot create transient scope: DBus error “org.freedesktop.DBus.Error.TimedOut”: [Failed to activate service ‘org.freedesktop.systemd1’: timed out (service_start_timeout=25000ms)]
+```
+
+原因就是设置的实例数量太多了，商家又高度限制IO
+
+![](./images/iofailed.png)
+
+此时只有一种方法，重启节点服务器，强制重启
+
+重启后立即登录SSH，使用对应的脚本删除swap的使用，然后删除一些实例释放资源
+
+由于重启后容器虚拟机需要一段时间一个个自动重启，打这个时间差可能删不了多少，但每次重启都能删一些
+
+最终还是需要在限制实例数量的时候，慎重考虑节点的性能，较弱或者限制较多的节点，建议不要开设过多实例
\ No newline at end of file