wsl2下如何配置vtd仿真环境！

已经安装了 wsl2 与 vtd，但是运行期间报错打不开端口，已经检查了权限和防火墙已经占用，束手无策了。有没有人在 wsl 上配置过 vtd 呀！不想弄两台电脑了。


```bash
vtdStop.sh: working in VTD_ROOT=/root/VTD.2.2/bin/..
vtdStop.sh: stopping VTD ...
vtdStop.sh: VTD is stopped.
(base) root@DESKTOP-3ECV44J:~/VTD.2.2/bin# sudo ./vtdStart_test.sh 
调试信息：开始执行脚本
调试信息：VTD_ROOT设置为 /root/VTD.2.2/bin/..
working in VTD_ROOT=/root/VTD.2.2
调试信息：主机设置为 DESKTOP-3ECV44J
现在在主机 DESKTOP-3ECV44J 上启动SimServer和GUI...

============================================================
             [
            [
           [
          [
 [       [  [  [[[[[   [[[[[   [[[
  [     [  [  [    [  [      [
   [   [  [  [[[[[   [[[[    [[[
    [ [  [  [  [    [          [
     [  [  [   [   [[[[[   [[[

 Copyright (C) VIRES Simulationstechnologie GmbH
============================================================

 

 Version 1.3.1  -  17:50:49 Jul 20 2017

 Author:   VIRES

 Revision: 143
============================================================


INFO  Mon 2024-06-17 21:41:17 processCmdLine:     Run as a Master
INFO  Mon 2024-06-17 21:41:17 SetupBase::initialize: Resolved VTD_ROOT </root/VTD.2.2>
INFO  Mon 2024-06-17 21:41:17 SetupBase::initialize: -- Default setting --
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: ---- Settings info ----
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Config name = Standard
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Idle rate = 20
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Work rate = 33
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: log dir = /tmp
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: log name = taskRec_SimServer.txt
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: notify level = INFO
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: username = root
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: vtdRoot = /root/VTD.2.2
INFO  Mon 2024-06-17 21:41:17 Master::initialize: unblock signals  SIGCHLD SIGINT SIGTERM
INFO  Mon 2024-06-17 21:41:17 Master::initialize: Preparing for redirecting </root/VTD.2.2/Data/Setups/Current/Config/SimServer/simServer.xml> [configName = Standard] base on VTD_ROOT...
INFO  Mon 2024-06-17 21:41:17 Master::initialize: Config file absolute path </root/VTD.2.2/Data/Setups/Current/Config/SimServer>
INFO  Mon 2024-06-17 21:41:17 Master::initialize: VTD_ROOT absolute path </root/VTD.2.2>
INFO  Mon 2024-06-17 21:41:17 Master::initialize: Config file relative path to VTD_ROOT <Data/Setups/Standard/Config/SimServer>
INFO  Mon 2024-06-17 21:41:17 Master::initialize: Reset config file's path to <Data/Setups/Standard/Config/SimServer/simServer.xml>
INFO  Mon 2024-06-17 21:41:17 Master::initialize: Change working directory to </root/VTD.2.2>
INFO  Mon 2024-06-17 21:41:17 Master::initialize: Verify working directory </root/VTD.2.2>
INFO  Mon 2024-06-17 21:41:17 MasterSetup::normalize: normalizing <Data/Setups/Standard/Config/SimServer/simServer.xml> [setupName = Standard] ...
INFO  Mon 2024-06-17 21:41:17 MasterSetup::normalize: normalizing slave <desktop-3ecv44j> ...
INFO  Mon 2024-06-17 21:41:17 MasterSetup::normalize: predefined envvar [PORT_SIMSERVER = 32512]
INFO  Mon 2024-06-17 21:41:17 Master::initialize: Run as a Master, host <desktop-3ecv44j> [tuple = 127.0.1.1:32512], 
INFO  Mon 2024-06-17 21:41:17 vtd::SocketTcpMultipleServerChannel::open: open: success open port 32512 on channel Master.
INFO  Mon 2024-06-17 21:41:17 Master::initialize: Set envvar PORT_SIMSERVER to <32512>
INFO  Mon 2024-06-17 21:41:17 Master::initialize: going to cbInit ... 
INFO  Mon 2024-06-17 21:41:17 Master::cbInit:     going to cbRun
INFO  Mon 2024-06-17 21:41:17 SetupBase::initialize: Resolved VTD_ROOT </root/VTD.2.2>
INFO  Mon 2024-06-17 21:41:17 SetupBase::initialize: -- Default setting --
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: ---- Settings info ----
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Config name = Standard
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Idle rate = 20
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Work rate = 33
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: log dir = /tmp
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: log name = taskRec_SimServer.txt
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: notify level = INFO
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: username = root
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: vtdRoot = /root/VTD.2.2
INFO  Mon 2024-06-17 21:41:17 vtd::SocketTcpServerChannel::open: open: success open port 32513 on channel desktop-3ecv44j.
INFO  Mon 2024-06-17 21:41:17 Master::cbInit:     Starting a slave <desktop-3ecv44j> by command '${VTD_ROOT}/Runtime/Core/SimServer/startSlave.sh desktop-3ecv44j 32512 /root/VTD.2.2 desktop-3ecv44j root /tmp/taskRec_SimServerSlave.txt'
Master host = desktop-3ecv44j
Master port = 32512
Slave host = desktop-3ecv44j
Slave user = root
Slave VTD_ROOT = /root/VTD.2.2
Slave log name = /tmp/taskRec_SimServerSlave.txt
INFO  Mon 2024-06-17 21:41:17 Master::cbInit:     system(): 0
teeLimit: limiting size of output file </tmp/taskRec_SimServerSlave.txt> to 5000000 bytes.

============================================================
             [
            [
           [
          [
 [       [  [  [[[[[   [[[[[   [[[
  [     [  [  [    [  [      [
   [   [  [  [[[[[   [[[[    [[[
    [ [  [  [  [    [          [
     [  [  [   [   [[[[[   [[[

 Copyright (C) VIRES Simulationstechnologie GmbH
============================================================

 

 Version 1.3.1  -  17:50:49 Jul 20 2017

 Author:   VIRES

 Revision: 143
============================================================


INFO  Mon 2024-06-17 21:41:17 processCmdLine:     Run as a Slave
INFO  Mon 2024-06-17 21:41:17 SetupBase::initialize: Resolved VTD_ROOT </root/VTD.2.2>
INFO  Mon 2024-06-17 21:41:17 SetupBase::initialize: -- Default setting --
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: ---- Settings info ----
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Config name = Standard
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Idle rate = 20
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: Work rate = 33
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: log dir = /tmp
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: log name = taskRec_SimServer.txt
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: notify level = INFO
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: username = root
INFO  Mon 2024-06-17 21:41:17 SetupBase::showInfo: vtdRoot = /root/VTD.2.2
INFO  Mon 2024-06-17 21:41:17 Slave::initialize:  Change working dir to /root/VTD.2.2
INFO  Mon 2024-06-17 21:41:17 Slave::initialize:  Run as a Slave host <desktop-3ecv44j>, [master host:port = localhost:32512]
INFO  Mon 2024-06-17 21:41:17 vtd::SocketTcpClientChannel::open: open: channel <SSDP> sucess [port = 32512, addr = 127.0.0.1]
INFO  Mon 2024-06-17 21:41:17 Slave::initialize:  Connected to channel <SSDP> [host:port = localhost:32512].
NOTICE (PortTCPServer): "PortTCPServer::checkForClient: client connected on port 32512, desc 6 from address (127.0.0.1)"
INFO  Mon 2024-06-17 21:41:17 Slave::cbInit:      claim slave <desktop-3ecv44j> to the Master
INFO  Mon 2024-06-17 21:41:17 Master::operator:   welcome <desktop-3ecv44j> [port = 32513]
INFO  Mon 2024-06-17 21:41:17 Slave::cbInit:      claim slave <desktop-3ecv44j> to the Master
INFO  Mon 2024-06-17 21:41:17 Master::operator:   welcome <desktop-3ecv44j> [port = 32513]
INFO  Mon 2024-06-17 21:41:17 Slave::operator:    Master opens private port <32513> [master host = localhost]
INFO  Mon 2024-06-17 21:41:17 Slave::operator:    close channel <SSDP> [localhost:32512]
INFO  Mon 2024-06-17 21:41:17 vtd::SocketTcpClientChannel::open: open: channel <desktop-3ecv44j> sucess [port = 32513, addr = 127.0.0.1]
INFO  Mon 2024-06-17 21:41:17 Slave::operator:    go to stage <Service>
WARN  Mon 2024-06-17 21:41:17 vtd::SocketChannelBase::writeChannel: writeChannel: no connection on channel <SSDP> yet.
INFO  Mon 2024-06-17 21:41:17 Slave::cbInit:      claim slave <desktop-3ecv44j> to the Master
NOTICE (PortTCPServer): "PortTCPServer::checkForClient: client connected on port 32513, desc 7 from address (127.0.0.1)"
WARNING (PortTCPServer): "PortTCP::read: connection <6> lost on port #32512. "
NOTICE (PortTCPServer): "PortTCPServer::disconnect: disconnecting parent socket 6."
INFO  Mon 2024-06-17 21:41:17 SlaveStub::operator: return from <desktop-3ecv44j> calling method <configure> [pass = true] 
INFO  Mon 2024-06-17 21:41:17 SlaveStub::operator: host <desktop-3ecv44j> success [isConfigured = true]
INFO  Mon 2024-06-17 21:41:17 Master::transit:    <Config> ==> <Ready>
INFO  Mon 2024-06-17 21:41:17 SlaveBase::startExplicitTask: <ParamServer>. [Go]
INFO  Mon 2024-06-17 21:41:17 vtdev::Process::ProcessImpl::start: Process: ParamServer          [0] starting to run ... 
INFO  Mon 2024-06-17 21:41:17 vtdev::ProcessManager::start: thread for monitoring child processes is running ...
INFO  Mon 2024-06-17 21:41:17 vtdev::Process::ProcessImpl::startProcess: Process: ParamServer          [0] is at STARTING state, NOTRUNNING => STARTING
INFO  Mon 2024-06-17 21:41:17 vtdev::ProcessManager::run: waiting for children to die
INFO  Mon 2024-06-17 21:41:17 vtdev::Process::ProcessImpl::execChild: Process: Calling exec() ...
INFO  Mon 2024-06-17 21:41:17 vtdev::Process::ProcessImpl::waitForStarted: Process: ParamServer          [15547] is running ... STATING => RUNNING
INFO  Mon 2024-06-17 21:41:17 VtdLocalTask::startWithTerminal: ParamServer [15547] is started
INFO  Mon 2024-06-17 21:41:17 SlaveStub::operator: return from <desktop-3ecv44j> calling method <load> [pass = true] 
INFO  Mon 2024-06-17 21:41:17 SlaveBase::startExplicitTask: <ParamServer>. [Go]
INFO  Mon 2024-06-17 21:41:17 SlaveStub::operator: task <ParamServer> success [task running = true]
INFO  Mon 2024-06-17 21:41:18 SlaveBase::startExplicitTask: <TaskControl>. [Go]
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::start: Process: TaskControl          [0] starting to run ... 
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::startProcess: Process: TaskControl          [0] is at STARTING state, NOTRUNNING => STARTING
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::execChild: Process: Calling exec() ...
INFO  Mon 2024-06-17 21:41:18 vtdev::ProcessManager::run: waiting for children to die
INFO  Mon 2024-06-17 21:41:18 SlaveStub::operator: return from <desktop-3ecv44j> calling method <load> [pass = false] 
INFO  Mon 2024-06-17 21:41:18 SlaveStub::operator: failed calling method <load> [host = desktop-3ecv44j]
INFO  Mon 2024-06-17 21:41:18 SlaveBase::startExplicitTask: <VtGui>. [Go]
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::start: Process: VtGui                [0] starting to run ... 
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::startProcess: Process: VtGui                [0] is at STARTING state, NOTRUNNING => STARTING
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::start: Process: viTee                [0] starting to run ... 
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::startProcess: Process: viTee                [0] is at STARTING state, NOTRUNNING => STARTING
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::execChild: Priority must be 0 in normal schedule policy
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::execChild: Process: Calling exec() ...
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::waitForStarted: Process: VtGui                [15552] is running ... STATING => RUNNING
INFO  Mon 2024-06-17 21:41:18 VtdLocalTask::startWithoutTerminal: Vtgui is started
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::waitForStarted: Process: viTee                [15553] is running ... STATING => RUNNING
INFO  Mon 2024-06-17 21:41:18 VtdLocalTask::startWithoutTerminal: tee is started
teeLimit: limiting size of output file </tmp/taskRec_VtGui.txt> to 50000000 bytes.
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::execChild: Priority must be 0 in normal schedule policy
INFO  Mon 2024-06-17 21:41:18 vtdev::Process::ProcessImpl::execChild: Process: Calling exec() ...

=============================================
             [
            [
           [
          [
 [       [  [  [[[[[   [[[[[   [[[
  [     [  [  [    [  [      [
   [   [  [  [[[[[   [[[[    [[[
    [ [  [  [  [    [          [
     [  [  [   [   [[[[[   [[[

 (c) VIRES GmbH         2010-2014
=============================================
 VtGui IOS - Version 2.2.0

 created: Dec 20 2018, 13:28:22
=============================================

INFO  Mon 2024-06-17 21:41:18 vtdev::ProcessManager::run: waiting for children to die
INFO  Mon 2024-06-17 21:41:18 vtdev::ProcessManager::run: waiting for children to die
INFO  Mon 2024-06-17 21:41:18 SlaveStub::operator: return from <desktop-3ecv44j> calling method <load> [pass = true] 
INFO  Mon 2024-06-17 21:41:18 SlaveBase::startExplicitTask: <VtGui>. [Go]
INFO  Mon 2024-06-17 21:41:18 SlaveStub::operator: task <VtGui> success [task running = true]
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
调试信息：SimServer已启动
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 48179 to <localhost>"
WARNING (ParamGuiWidget): "ComHandler::createClientPort: could not open client port 54345 to <PARAM_SCP_CHNL>"

希望有真正研究过安装 vtd 的答者给出解决方案，目前通过研究解决了一部分问题，但是还是有部分进程无法启动。不需要 ai，我自己有 gpt4。

写回答
好问题 0 提建议
追加酬金
关注问题
分享
邀请回答
编辑收藏删除结题
收藏举报

3条回答默认最新

关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
专家-赤兔[在线] 全栈领域优质创作者 2024-06-17 23:11
关注
引自免费微信小程序：皆我百晓生

面对在WSL2环境下配置VTD(车辆工具开发)仿真环境遇到的问题，特别是关于端口冲突的情况，可以采取以下步骤进行排查和解决：

步骤1：确认端口是否被占用

首先，确保目标端口（比如默认的VTD端口）没有被其他进程占用。在WSL2中，可以通过以下命令检查端口状态：

sudo lsof -i :<port>

例如，如果你要检查8080端口是否被占用：

sudo lsof -i :8080

如果发现端口被占用，可以尝试找出具体是哪个进程并结束它：

sudo fuser -k <port>/tcp

例如：

sudo fuser -k 8080/tcp

步骤2：检查防火墙设置

即使端口未被占用，防火墙也可能阻止VTD访问该端口。在WSL2中，防火墙规则通常由宿主机（即Windows系统）管理。可以通过以下命令查看Windows防火墙规则：

Get-NetFirewallRule | Where-Object { $_.DisplayName -like "*VTD*" }

如果发现有相关规则阻止VTD的端口，可以尝试修改或删除这些规则。这通常需要管理员权限。

步骤3：配置WSL2网络

确保WSL2的网络设置允许VTD正确地监听和绑定端口。WSL2默认使用虚拟网络适配器与宿主机通信，可能需要在Windows的网络设置中检查或调整此适配器的属性。

步骤4：修改VTD配置文件

如果上述步骤未能解决问题，考虑修改VTD的配置文件，指定一个不同的、未被占用的端口。VTD的配置文件通常位于安装目录下的config.xml文件中。找到<port>标签，并将其更改为未使用的端口号。

例如：

<port>9090</port>

步骤5：重启VTD服务

更改配置后，务必重启VTD服务，确保新的端口设置生效。

进阶步骤：跨平台调试

如果VTD需要与宿主机上的应用程序交互，确保WSL2和Windows之间的网络通信正常。可以通过在VTD中使用宿主机的IP地址（通常是192.168.1.1或172.20.10.1等，取决于你的网络设置）来测试这一点。

如果以上步骤都无法解决问题，可能需要深入检查WSL2的网络栈或VTD软件本身是否存在已知的兼容性问题。

希望这些步骤能帮助你成功在WSL2环境下配置VTD仿真环境。如果还有其他技术障碍，进一步的细节或错误信息将有助于更精确的诊断和解决策略。
解决
无用 1
评论打赏
分享
举报编辑记录

评论

按下Enter换行，Ctrl+Enter发表内容

报告相同问题？

关注问题

wsl2原有配置在从c盘迁移到d盘后丢失 linux ubuntu
2022-01-08 22:24

回答 1 已采纳如果文件备份及导入正常的话，linux中已有的配置和文件是不会丢失的。需要看一下重新导入后的内容，相较于备份前文件是否齐全，另外导入导出前后，指定的linux用户是否相同。
wsl2 wslg ubuntu18.04 配置搜狗输入法 linux
2021-08-08 18:13

回答 3 已采纳我也是上面教程，在fictx配置中将pinyin放在第一个后成功
wsl2安装后无法下载包 ubuntu
2022-04-26 21:41

回答 1 已采纳改个源看看https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/
WSL2下配置ESP-IDF开发环境
2023-05-24 15:14

Missrainbows的博客本文主要介绍wsl2&esp-idf环境搭建，以及wsl2下的串口如何使用。
goland运行wsl环境错误 golang
2023-02-03 13:53

回答 2 已采纳 “该回答引用ChatGPT”请参考下面的方法，如果可行还望采纳,感谢！这个问题可能是因为 Windows SDK 和 WSL 项目使用了不同的编译器或编译工具链。WSL 环境是 Linux 环境，需要
如何在Windows WSL 22.04ubuntu子系统上配置深度学习环境 linux ubuntu 服务器
2022-08-23 06:44

回答 5 已采纳 liburcu6 库没有安装，外网限制没有下载，可以手动下载，安装安装anaconda虚拟环境，安装深度学习环境，参考https://blog.csdn.net/qq122716072/article
clion使用wsl不能导入环境变量 ide
2023-03-26 16:22

回答 11 已采纳 #添加环境变量TEMPORARY echo 'export TEMPORARY = /usr/local'>>/.bashrc#添加WSL和Windows进程之间共享环境变量 echo '
超详细 WSL2安装+深度学习环境配置
2023-03-09 19:24

ww_khun的博客简要介绍了 Windows 下 WSL 的优势和 WSL 的发展，给出了 WSL 2 的详细安装过程，以及如何在 WSL Ubuntu下搭建深度学习环境，其余则是对 WSL 的一些可玩性的探索。
Wsl1 升级为Wsl2 r语言开发语言
2023-04-03 00:54

回答 1 已采纳你可以看下这个问题的回答https://ask.csdn.net/questions/7626830这篇博客你也可以参考下：WSL / WSL2 问题大全及解决方案
Ubuntu WSL2 GUI 安装xfce4出现的异常错误。该如何处理？ ubuntu
2022-05-04 14:16

回答 3 已采纳遇到这种报错我一般分几个步骤做：查看大致的报错问题，就拿你这报错中大量出现Connect IP什么的，首先可以排除网络是通的因为没网怎么可能有外网IP，然后就是怀疑是不是没有适配的包的问题，导致长时间
win10通过WSL2安装docker docker
2022-03-01 18:30

回答 1 已采纳 docker linux内核7会出现以上问题,直接升级内核或者采用如下配置创建 C:\Users(用户名).wslconfig，里面写入[wsl2]kernelCommandLine = vsysca
Windows家庭版 WSL2非C盘详细安装配置与WSL代理设置+WSL基础环境CUDA安装
2024-06-04 19:38

PLUS_WAVE的博客功能开启后，管理员运行 PowerShell ，直接运行下面命令即可（默认WSL2），然后重启。Linux 生成的所有文件都默认存储在之前自定义的路径下的这个镜像文件中。WSL2 显卡驱动直接用的 windows 的，只需要安装CUDA ...
Windows11开启wsl2运行Linux操作系统失败 linux ubuntu windows
2022-12-19 14:01

回答 1 已采纳 1、无法访问国外的github2、你本机没有安装wsl分发版，也就是没有安装Linux子系统你可以从别人安装好的wsl导出一个压缩包，然后在自己本地导入，也可以安装。
WSL2网络配置
2023-06-01 20:41

皛心的博客 WSL2越来越好用了，但是在windows下使用clash时，配置WSL2的网络很麻烦，通常使用设置环境变量的方式有很大的弊端，例如pip和conda就不会走代理。经过我亲身体验，最好的解决方案还是配置虚拟交换机。
WSL环境配置Node编译环境，在WSL中编译node.js
2023-02-09 23:03

WSL环境配置Node编译环境，在WSL中编译node.js，解决node.js编译时Windows环境不支持的问题，方便运行sh脚本
使用WSL2配置深度学习环境（详细版）
2024-06-03 16:40

htzckk的博客使用WSL2配置深度学习环境
WSL2环境下Debian12的Docker安装与配置
2023-11-18 19:15

晨曦蜗牛的博客【代码】WSL2环境下Debian 12的Docker安装与配置。
在WSL2下配置Pytorch(Linux+Anaconda+PyTorch-GPU)
2024-06-10 21:27

Whatever222222的博客 1.用户：以前没有注意过，默认用户root，还有一个自己取名的用户，可以配置默认打开的用户，要注意anaconda环境配置在哪个用户下，我就是在这里卡了很久，明明安装了anaconda居然找不到。最方便的方法就是通过官网的...
没有解决我的问题, 去提问

问题事件

关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
修改了问题 6月19日
关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
修改了问题 6月18日
关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
创建了问题 6月17日

悬赏问题

¥15 静电纺丝煅烧后如何得到柔性纤维
¥15 (标签-react native|关键词-镜像源)
¥100 照片生成3D人脸视频
¥15 伪装视频时长问题修改MP4的时长问题，
¥15 JETSON NANO
¥15 VS开发qt时如何在paintgl函数中用pushbutton控制切换纹理
¥20 关于 openpyxl 处理excel文件地问题
¥15 MS中不知道高分子的构型怎么构建模型
¥60 QQOP数据，什么是op数据号，怎么提取op数据！能不能大量提取(语言-c语言)
¥15 matlab代码关于微分方程和嵌套的分段函数。

wsl2下如何配置vtd仿真环境！

3条回答 默认 最新

步骤1：确认端口是否被占用

步骤2：检查防火墙设置

步骤3：配置WSL2网络

步骤4：修改VTD配置文件

步骤5：重启VTD服务

进阶步骤：跨平台调试

问题事件

悬赏问题

3条回答默认最新