blocks|key|5450804|text|在命令行上运行以下命令可解锁虚拟机：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5450805|vboxmanage+startvm+<vm-uuid>+--type+emergencystop|code-block|syntax|javascript|5450806|其中，<vm-uuid>是错误消息中的编号：Command:+["modifyvm",+"<vm-uuid>"+[...]。在那之后，我能够控制VM+(启动、停止等)。在Ubuntu上使用Virtualbox+4.1。|offset|length|style|CODE|5450807|entityMap^0|0|0|3|9|M|13|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Running this on the command line unlocked the VM:

<pre><code>vboxmanage startvm &lt;vm-uuid&gt; --type emergencystop
</code></pre>

Where <code>&lt;vm-uuid&gt;</code> is the number in the error message: <code>Command: ["modifyvm", "&lt;vm-uuid&gt;" [...]</code>. After that I was able to control the VM (start, halt, etc).
Using Virtualbox 4.1 on Ubuntu.

blocks|key|5450732|text|同样的问题，我发现有一个进程正在运行，实际上锁定了虚拟机：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5450733|501+79419+79323+++0++2:18PM+??+++++++++0:39.75+/Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless+--comment+default+--startvm+1d438a2e-68d7-4ba2-bef9-4ea162913c1b+--vrde+config|code-block|syntax|javascript|5450734|确保您的进程在尝试启动vm时不会卡住：|5450735|ps+-ef+%7C+grep+-i+"vbox"|5450736|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Having the same issue I found that there was a process running actually locking the vm:

<pre><code>501 79419 79323 0 2:18PM ?? 0:39.75 /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless --comment default --startvm 1d438a2e-68d7-4ba2-bef9-4ea162913c1b --vrde config
</code></pre>

Make sure you don't have a process stuck trying to start the vm:

<pre><code>ps -ef | grep -i "vbox"
</code></pre>

blocks|key|5450871|text|对我来说，我必须在任务管理器中终止VboxHeadless.exe进程。我还必须确保在管理模式下打开CMD提示符。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5450872|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me I had to kill the VboxHeadless.exe process in task manager. I also had to ensure CMD prompt was opened in Administrative mode.

blocks|key|4032563|text|我发现@Gonzalez的这个答案非常有趣。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4032564|vboxmanage+startvm+<vm-uuid>+--type+emergencystop|code-block|syntax|javascript|4032565|唯一的问题是它关闭了我的VM的当前实例，所以如果当前vm正在运行，您可以使用controlvm而不是modifyvm。|offset|length|style|CODE|4032566|例如：|4032567|+VBoxManage+modifyvm+<vm_name>+--natpf1+"guestssh,tcp,,22,,2222"
+VBoxManage+modifyvm+<vm_name>+--natpf1+delete+"guestssh"|4032568|成为：|4032569|VBoxManage+controlvm+<vm_name>+natpf1+"guestssh,tcp,,22,,2222"
VBoxManage+controlvm+<vm_name>+natpf1+delete+"guestssh"|4032570|完整文档请单击此处https://www.virtualbox.org/manual/ch08.html#vboxmanage-controlvm|4032571|entityMap|0|LINK|mutability|MUTABLE|url|https://www.virtualbox.org/manual/ch08.html#vboxmanage-controlvm^0|0|0|12|9|1E|8|0|0|0|0|0|9|1S|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@$I|17|J|18|K|L]|$I|19|J|1A|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1C|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|1F|8|@]|9|@$I|1G|J|1H|1|1I]]|A|$]]|$1|W|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

I found this answer from @Gonzalez very interesting. 

<pre><code>vboxmanage startvm &lt;vm-uuid&gt; --type emergencystop
</code></pre>

The only problem with that it shut down the current instance of my VM, so instead of using <code>modifyvm</code> you can use <code>controlvm</code> if the current vm is running.

For example:

<pre><code> VBoxManage modifyvm &lt;vm_name&gt; --natpf1 "guestssh,tcp,,22,,2222"
 VBoxManage modifyvm &lt;vm_name&gt; --natpf1 delete "guestssh"
</code></pre>

Become:

<pre><code>VBoxManage controlvm &lt;vm_name&gt; natpf1 "guestssh,tcp,,22,,2222"
VBoxManage controlvm &lt;vm_name&gt; natpf1 delete "guestssh"
</code></pre>

Full documentation Here
<a href="https://www.virtualbox.org/manual/ch08.html#vboxmanage-controlvm" rel="noreferrer">https://www.virtualbox.org/manual/ch08.html#vboxmanage-controlvm</a>

blocks|key|1921955|text|sudo+pkill+-9+VBox杀死所有与vbox相关的运行中的东西|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1921956|entityMap^0|0|I|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

<code>sudo pkill -9 VBox</code> kills everything running related to vbox

blocks|key|5450821|text|在Windows任务管理器中，我结束了所有与Virtual+Box相关的任务(你可以在任务管理器中看到它们以V开头，比如Vbox+Headless.exe等)。一旦我这样做了，我就能够让这个错误消失(上面的'vboxmanage+startvm+...etc...‘这里的解决方案对我不起作用)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5450822|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In Windows Task Manager, I ended any tasks related to Virtual Box (you can see they start with a V in Task Manager like Vbox Headless.exe, etc). Once I did that, I was able to get this error to go away (the above 'vboxmanage startvm ...etc...' solutions here did not work for me).

blocks|key|5450842|text|如果在VirtualBox图形用户界面中为该框打开了设置窗口，则可能会遇到此错误。只需关闭设置窗口，然后重试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5450843|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you have a settings window open for that box in the VirtualBox GUI, you may run into this error. Just close the settings window and try again.

blocks|key|4032451|text|我今天遇到了同样的错误消息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4032452|>me@myhost:~$+ps+-ef+%7C+grep+-i+"vbox"

me++3064+++++1++0+08:51+?++++++++00:00:00+/usr/lib/virtualbox/VBoxXPCOMIPCD

me++3089+++++1++0+08:51+?++++++++00:00:00+/usr/lib/virtualbox/VBoxSVC+--auto-shutdown

me++3126++3089+27+08:51+?++++++++00:00:39+/usr/lib/virtualbox/VBoxHeadless+--comment+RHEL5+64-bit+desktop+--startvm+e5c598d8-1234-4003-a7c1-b9d8af15dfe7+--vrde+config

me++3861++3415++0+08:53+pts/1++++00:00:00+grep+--color=auto+-i+vbox*|code-block|syntax|javascript|4032453|Gergely的回答完美地解决了这个问题。事实证明，我在重启时设置了一个crontab来引导虚拟机，它启动了上面显示的三个VBox进程|4032454|me@myhost:~$+crontab+-l

@reboot+me+/usr/bin/vboxmanage+startvm+"RHEL5+64-bit+desktop"+--type+headless|4032455|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I've encounter the same error message today:

<pre><code>&gt;me@myhost:~$ ps -ef | grep -i "vbox"

me 3064 1 0 08:51 ? 00:00:00 /usr/lib/virtualbox/VBoxXPCOMIPCD

me 3089 1 0 08:51 ? 00:00:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown

me 3126 3089 27 08:51 ? 00:00:39 /usr/lib/virtualbox/VBoxHeadless --comment RHEL5 64-bit desktop --startvm e5c598d8-1234-4003-a7c1-b9d8af15dfe7 --vrde config

me 3861 3415 0 08:53 pts/1 00:00:00 grep --color=auto -i vbox*
</code></pre>

Gergely's answer solves it perfectly. It turned out that I've a crontab set at reboot to boot the virtual machine, which initiated the three VBox process shown above

<pre><code>me@myhost:~$ crontab -l

@reboot me /usr/bin/vboxmanage startvm "RHEL5 64-bit desktop" --type headless
</code></pre>

blocks|key|1921858|text|对我来说唯一有效的选择是杀死所有匹配ps+axl%7Cgrep+-i+vbox的进程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1921859|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The only option that worked for me was to kill all the processes matching ps axl|grep -i vbox.

blocks|key|5450927|text|在我的例子中，明显的原因是USB以太网适配器在机器挂起后被移除。在我的情况下，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5450928|vboxmanage+startvm+<vm-uuid>+--type+emergencystop|code-block|syntax|javascript|5450929|无济于事。相反，我收到了令人困惑的消息|5450930|5450931|+VBoxManage:错误:计算机'xyzzy‘未被会话锁定|blockquote|5450932|5450933|5450934|运行以下命令即可发现真正的错误|5450935|vboxmanage+startvm+<vm-uuid>+--type+gui|5450936|返回的|5450937|5450938|+VBoxManage:错误:主机网络接口不存在，名称为'en9:+USBPlug‘(VERR_INTERNAL_ERROR)|5450939|5450940|5450941|将网络配置更改为另一个网络适配器解决了此问题。|5450942|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|15|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|17|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|V|3|W|5|L|7|1E|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1H|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|12|$]]

In my case, the apparent cause was a USB ethernet adapter that had been removed after suspending the machine. In my case,

<pre><code>vboxmanage startvm &lt;vm-uuid&gt; --type emergencystop
</code></pre>

did not help. Instead, I received the confusing message that

<blockquote>
<pre><code>VBoxManage: error: The machine 'xyzzy' is not locked by a session
</code></pre>
</blockquote>

The true error was revealed by running

<pre><code>vboxmanage startvm &lt;vm-uuid&gt; --type gui
</code></pre>

which returned

<blockquote>
<pre><code>VBoxManage: error: Nonexistent host networking interface, name 'en9: USBPlug' (VERR_INTERNAL_ERROR)
</code></pre>
</blockquote>

Changing the network configuration to a different network adapter solved the issue.

My VM in virtualbox can not start due to this error, I don't want to destroy it and reinstall it again, anyway to recover it ?

There was an error while executing <code>VBoxManage</code>, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

<pre><code>Command: ["modifyvm", "319fcce3-e8ff-4b6f-a641-3aee1df6543f", "--natpf1", "delete", "ssh"]

Stderr: VBoxManage: error: The machine 'centos64_c6402_1454036461345_59755' is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LockMachine(a-&gt;session, LockType_Write)" at line 493 of file VBoxManageModifyVM.cpp
</code></pre>

VM in virtualbox is already locked for a session (or being unlocked)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我的虚拟机在virtualbox中无法启动，因为这个错误，我不想销毁它并重新安装它，无论如何都要恢复它？执行Vagrant用于控制VirtualBox的VBoxManage时出错。命令和stderr如下所示。Command: ["modifyvm", "319fcce3-e8ff-4b6f-a641-3aee1df6543f", "--natpf1", "delete", "ssh"]Stderr

问virtualbox中的VM已为会话锁定(或正在解锁)
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问virtualbox中的VM已为会话锁定(或正在解锁)EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问virtualbox中的VM已为会话锁定(或正在解锁)
EN