blocks|key|4556501|text|我通过使用vboxmanage获取虚拟机的ID来解决此问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4556502|$+vboxmanage+list+vms
"my-vm"+{c700b8b6-b766-4638-871b-736b44b7db18}|code-block|syntax|javascript|4556503|将所需VM的ID+(+c700…db18字符串)复制到~/.vagrant/machines/default/virtualbox/id的内容中。保存该文件，然后运行vagrant+up，使vm正常工作，而不必销毁它。|4556504|entityMap^0|5|A|0|0|B|9|R|15|2B|A|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

I solved by using <code>vboxmanage</code> to get the ID of the VM.

<pre><code>$ vboxmanage list vms
"my-vm" {c700b8b6-b766-4638-871b-736b44b7db18}
</code></pre>

Copy the ID of the desired VM (the <code>c700…db18</code> string) into the contents of <code>~/.vagrant/machines/default/virtualbox/id</code>. Save the file then run <code>vagrant up</code> to get the vm working without having to destroy it.

blocks|key|4556464|text|对我来说，这台机器没有在VirtualBox应用程序中显示为活动VM。为了解决这个问题，我不得不这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4556465|vagrant+global-status|offset|length|style|CODE|4556466|这给了我需要销毁的机器的ID。使用ID，运行：|4556467|vagrant+destroy+{VM+ID}|4556468|我必须在sudo中运行它才能真正销毁机器。在这一点上，我能够运行|4556469|vagrant+up|4556470|entityMap^0|0|0|L|0|0|0|N|0|0|0|A|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|Q|$]]

For me, the machine was not showing up as an active VM in the VirtualBox application. To fix I had to do this:

<code>vagrant global-status</code>

This gave me the ID of the machine that I needed to destroy. With the ID, run:

<code>vagrant destroy {VM ID}</code>

I had to run that in sudo to actually destroy the machine. At that point, I was able to run 

<code>vagrant up</code>

blocks|key|4556333|text|您可能正在运行一个virtualbox！打开程序virtualbox并关闭另一个virtualbox+;)+http://smallbusiness.chron.com/shut-down-virtualbox-43657.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4556334|如果这不起作用，那么您可能想要删除旧的homestead文件夹，并将所有项目放在新文件夹中;)|4556335|entityMap|0|LINK|mutability|MUTABLE|url|http://smallbusiness.chron.com/shut-down-virtualbox-43657.html^0|1I|1Q|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You probably have a virtualbox running! Open the programme virtualbox and shut down the other virtualbox ;)
<a href="http://smallbusiness.chron.com/shut-down-virtualbox-43657.html">http://smallbusiness.chron.com/shut-down-virtualbox-43657.html</a>

If this isn't working then you might want to delete the old homestead folder and place all your projects in the new folder ;)

blocks|key|50378|text|我编辑了Homestead.yaml并为它添加了新名称|type|unstyled|depth|inlineStyleRanges|entityRanges|data|50379|ip:+"192.168.10.10"
memory:+2048
cpus:+4
provider:+virtualbox
name:+my-new-homestead-box-name|code-block|syntax|javascript|50380|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I edited Homestead.yaml and add new name for it

<pre><code>ip: "192.168.10.10"
memory: 2048
cpus: 4
provider: virtualbox
name: my-new-homestead-box-name
</code></pre>

blocks|key|49770|text|我的项目中有一个旧的.vagrant目录，它导致了这个错误:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|49771|如果这不能解决你的问题，我建议打开VirtualBox，删除所有VirtualBoxes，然后再试一次。|49772|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had an old .vagrant directory in my project which was causing the error :)

If this doesn't fix it for you i would suggest opening VirtualBox and removing all VirtualBoxes and trying again.

blocks|key|49980|text|我今天也有同样的问题。花几个小时找出解决方案。如果由于任何原因你找不到正在退出的虚拟机列表，请输入终端|type|unstyled|depth|inlineStyleRanges|entityRanges|data|49981|sudo+virtualbox|code-block|syntax|javascript|49982|这将在GUI中运行Virtual+Box。您应该会看到虚拟机的完整列表，然后就可以对它们进行管理了。输入"virtualbox“不会显示任何内容。您需要是root用户(管理员)。|49983|感谢mightyspaj的提示。|49984|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|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had same issue today. Spend few hours to find the solution. 
If by any reason you can't find the list of exiting virtual machines then type in terminal 

<pre><code>sudo virtualbox
</code></pre>

This will run Virtual Box in GUI. You should see the the full list of VMs and from there you'd be able to manage them. 
Typing "virtualbox" only won't show anything. You need to be root (administrator). 

Thanks to mightyspaj for the tip.

blocks|key|50483|text|您只需将密钥name添加到您的homestead.yaml文件的提供者后面，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|50484|name:+name_of_you_machine|code-block|syntax|javascript|50485|这对我很有效。|50486|entityMap^0|6|4|F|E|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

You just have to add the key <code>name</code> to your <code>homestead.yaml</code> file right after the provider like this:
<pre><code>name: name_of_you_machine
</code></pre>
That works for me.

blocks|key|4556912|text|要执行的命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4556913|vagrant+box+list
vagrant+box+remove+laravel/homestead
vagrant+global-status
vagrant+destroy+nameOfYourBox|code-block|syntax|javascript|4556914|打开你的VirtualBox并删除你的宅基地的所有倾斜|4556915|vagrant+up|4556916|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|$]]

Commands to execute:
<pre><code>vagrant box list
vagrant box remove laravel/homestead
vagrant global-status
vagrant destroy nameOfYourBox
</code></pre>
Open your VirtualBox and delete all itens of your homestead
<pre><code>vagrant up
</code></pre>

blocks|key|4556399|text|我打开了virtualBox，然后删除了之前创建的homestead+vm。这很有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4556400|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|$]]

I opened the virtualBox and then deleted homestead vm that was created earlier. It helped.

blocks|key|50254|text|打开VirtualBox图形用户界面。请参见您的虚拟机并将其删除。它解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|50255|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|$]]

Open VirtualBox GUI. See for your VM and remove it.
It solved my problem.

blocks|key|4556672|text|有时，您可能不想删除旧的框。昨天，旧的Vagrant坏了，我已经更新了Vagrant和Virtualbox，但是文件夹映射不起作用。我想运行新的box，但遇到了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4556673|我不想删除旧的机器(因为我想运行一些备份)，但我想运行新的机器。解决方案正在运行VirtualBox，右键单击Homestead计算机，选择设置，然后将名称从homestead更改为homestead_old。|offset|length|style|CODE|4556674|在那之后，我可以安装homestead，但我有这台旧机器，还可以运行它来创建我需要的任何备份。|4556675|​|4556676|📷|atomic|4556677|4556678|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/ff8fceb348505eaf081aa4e0660ac740.jpeg|imageAlt^0|0|27|9|2J|D|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|16|8|@]|9|@$D|17|E|18|1|19]]|A|$]]|$1|O|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]]]

Sometimes you might not want to delete old box. Yesterday may old Vagrant has broken, I've updated Vagrant and Virtualbox but folders mapping didn't work. I wanted to run new box and had this error.

I didn't want to remove old box (because I wanted to run some backups) but I wanted to run new box. The solution was running VirtualBox, right click on Homestead machine and choose Settings and then changing name from <code>homestead</code> to <code>homestead_old</code>.

After that I was able to install homestead but had this old machine and could also run this to make any backups I needed.

<a href="https://i.stack.imgur.com/DfdMe.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DfdMe.jpg" alt="Homestead change name in Virtualbox"></a>

blocks|key|4556711|text|如果您是Windows用户，请确保删除C:\Users\<Username>\VirtualBox+VMs\homestead文件夹。因为如果仍然存在名为homestead的文件夹，则vagrant+up的操作将无法完成|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4556712|entityMap^0|J|18|2K|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

If you are a Windows User, make sure you delete <code>C:\Users\&lt;Username&gt;\VirtualBox VMs\homestead</code>folder. Because if there is still a folder named homestead, the action of <code>vagrant up</code> will not be completed

blocks|key|50284|text|您可以打开VirtualBox图形用户界面并删除冲突的虚拟机。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|50285|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|$]]

You can open the VirtualBox GUI and remove the conflicting virtual machine.

blocks|key|4556949|text|在方框之后和你指定的名字之前添加--force。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4556950|entityMap^0|G|7|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|$]]

Add <code>--force</code> after box, and before your given name.

blocks|key|4557003|text|我的id文件出现在下面提到的位置。D:\drupalvm.vagrant\machines\drupalvm\virtualbox|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4557004|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 id file was present in the below-mentioned location.
D:\drupalvm.vagrant\machines\drupalvm\virtualbox

blocks|key|49950|text|经过几个小时的故障排除后，其他任何东西对我来说都不起作用，因为没有人提到这个小细节。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|49951|根据安装时的权限，您可能需要以管理员身份运行virtualbox。只有当我这样做的时候，我才在虚拟机列表中看到我的流浪汉盒子。|49952|然后，我从virtualbox中删除了名为homestead的虚拟机，问题就解决了。|offset|length|style|CODE|49953|entityMap^0|0|0|L|9|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

After a few hours of troubleshooting, nothing else worked for me, as no one mentioned this little detail.

Depending on your privileges at the time of installation, you may need to run virtualbox as an administrator. It was only when I did this that I saw my vagrant boxes in the list of virtual machines.

I then proceeded to remove my virtual machine named <code>homestead</code> from virtualbox, and the problem was solved.

blocks|key|50012|text|如果您在Windows中使用homestead，只需打开您的Oracle并删除homestead+VM。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|50013|entityMap^0|13|9|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|$]]

If you're using homestead in Windows, just open up your Oracle VM VirtualBox and delete the <code>homestead</code> VM.

blocks|key|50171|text|在我的例子中，除了这条错误消息之外，没有任何东西表明VM“已经存在”。VirtualBox+UI上没有任何内容，“vboxmanage+list+vms”没有返回任何内容，“vagrant+global-status”没有返回任何内容，“.vagrant.d\boxes”中也没有返回任何内容，等等。我通过在VM+VirtualBox管理器中手动创建一个新的同名VM解决了这个问题(使用“新建”按钮%2B接受所有默认值)，然后删除它(右键单击>删除)。在那之后，“流浪汉up”就像预期的那样工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|50172|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 my case, nothing was indicating that the VM "already exists" besides that error message. Nothing on VirtualBox UI, nothing returned by “vboxmanage list vms”, nothing through “vagrant global-status”, it didn’t exist in “.vagrant.d\boxes” and so on. I resolved it by manually creating a new same-name VM in the VM VirtualBox Manager (using the “new” button + accepting all the defaults), and then removing it (right-click > remove). After that, the “vagrant up” worked as expected.

blocks|key|50235|text|我今天也遇到了同样的问题。Windows10。我最近更新了Homestead，所以这个错误可能是因为这个原因。我都试过了，destroy，up，删除文件夹，什么都行。每当我尝试运行vagrant+up时，它都会显示这种错误。解决方案是什么？更新后，我注意到Homestead现在根据项目文件夹名称来命名这些盒子，而Homestead.yaml拥有所有这些信息。我只需运行Homestead+Windows配置vendor\\bin\\homestead+make，然后运行vagrant+up+(在确保一切正常之前)，瞧，看起来机器现在已经启动了。=)如果你需要的话，试一试。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|50236|entityMap^0|1P|7|1X|2|2I|A|5O|R|6K|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|G|$]]

I had the same issue today. Windows 10. I recently had updated Homestead, so the error was probably because of that. I tried it all, <code>destroy</code>, <code>up</code>, delete folders, whatever. Whenever I tried to run <code>vagrant up</code>, it was showing this kind of errors. The solution? After updating, I noticed that Homestead is now naming the boxes by the project folder name, and Homestead.yaml has all that infos. I just run that Homestead Windows configuration <code>vendor\\bin\\homestead make</code> and later them a <code>vagrant up</code> (before making sure it was all clean) and voilá, looks like the machine is booting now. =) Try that if you need it.

blocks|key|4557143|text|VBoxManage:错误:无法将目录'/Users/xxxx/VirtualBox+VMs/ubuntu-20.04-amd64_xxxxxxx‘重命名为'/Users/xxxx/VirtualBox+VMs/homestead’以保存设置文件(VERR_ALREADY_EXISTS)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4557144|Removing+/Users/xxxx/VirtualBox+VM/homestead在mac中手动为我排序|4557145|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

VBoxManage: error: Could not rename the directory '/Users/xxxx/VirtualBox VMs/ubuntu-20.04-amd64_xxxxxxx' to '/Users/xxxx/VirtualBox VMs/homestead' to save the settings file (VERR_ALREADY_EXISTS)
Removing /Users/xxxx/VirtualBox VMs/homestead manually sort this out for me in mac

blocks|key|4556439|text|以上这些都不适合我。我的最终解决方案是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4556440|cd+~/.composer/vendor/laravel/homestead/.vagrant/machines;
rm+-R+default;
cd+/var/www/path/to/project;
homestead+up;|code-block|syntax|javascript|4556441|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

None of the above ended up working for me. My final solution was to:

<pre><code>cd ~/.composer/vendor/laravel/homestead/.vagrant/machines;
rm -R default;
cd /var/www/path/to/project;
homestead up;
</code></pre>

Since homestead 2.0 homestead laravel has not been working 

I don't know why 'homestead init' creates a Homestead.yaml file in mydirectory/.homestead 
and not in the project directory. Homestead up OR Vagrant up create the following message 

A VirtualBox machine with the name 'homestead' already exists.

<pre><code>Bringing machine 'default' up with 'virtualbox' provider...
==&gt; default: Importing base box 'laravel/homestead'...
==&gt; default: Matching MAC address for NAT networking...
==&gt; default: Checking if box 'laravel/homestead' is up to date...
A VirtualBox machine with the name 'homestead' already exists.
Please use another name or delete the machine with the existing
name, and try again.
</code></pre>

A VirtualBox machine with the name 'homestead' already exists

5位重磅专家聚焦 AI 时代开发者核心成长需求，带你深入解锁全栈进化、人机协作关键路径！点击报名到场：<a href="https://cloud.tencent.com/developer/salon/salon-2403/signup" target="_blank">https://cloud.tencent.com/developer/salon/salon-2403/signup</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/487c82639d2338df3ef66dfb1450601a.png"/>

腾讯技术创作特训营「年度论坛」正在报名中！

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

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

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

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

社区新版编辑器体验调研

自从homestead 2.0以来，homestead laravel一直没有运行我不知道为什么'homestead init‘会在mydirectory/.homestead中创建一个Homestead.yaml文件，而不是在项目目录中。Homestead up或Vagrant up创建以下消息名为“homestead”的VirtualBox计算机已存在。Bringing machine 'de

问名为“homestead”的VirtualBox计算机已存在
EN

回答 21

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问名为“homestead”的VirtualBox计算机已存在EN

回答 21

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问名为“homestead”的VirtualBox计算机已存在
EN