- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
谁能帮我解决这个错误!!!
以下是我的机器上安装的版本:
Chef 开发套件版本:2.0.28
PS C:\nginx\html\cereved\dev-environment> vagrant up
==> frontend: Box 'mvbcoding/awslinux' could not be found. Attempting to find and install...
frontend: Box Provider: virtualbox
frontend: Box Version: >= 0
==> frontend: Loading metadata for box 'mvbcoding/awslinux'
frontend: URL: https://vagrantcloud.com/mvbcoding/awslinux
==> frontend: Adding box 'mvbcoding/awslinux' (v2017.03.0.20170401) for provider: virtualbox
frontend: Downloading: https://vagrantcloud.com/mvbcoding/boxes/awslinux/versions/2017.03.0.20170401/providers/virtualbox.box
frontend: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
frontend:
==> frontend: Successfully added box 'mvbcoding/awslinux' (v2017.03.0.20170401) for 'virtualbox'!
frontend: The Berkshelf shelf is at "C:/Users/*******/.berkshelf/vagrant-berkshelf/shelves/berkshelf20190103-12584-svd029-frontend"
==> frontend: Sharing cookbooks with VM
==> frontend: Importing base box 'mvbcoding/awslinux'...
Progress: 90%There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["import", "\\\\?\\C:\\Users\\*******\\.vagrant.d\\boxes\\mvbcoding-VAGRANTSLASH-awslinux\\2017.03.0.20170401\\virtualbox\\box.ovf", "--vsys", "0", "--vmname", "amzn-ami-hvm-2017030201
70401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546506401977_30636", "--vsys", "0", "--unit", "7", "--disk", "C:\\Users\\*******\\VirtualBox VMs\\amzn-ami-hvm-201
703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546506401977_30636\\box-disk001.vmdk"]
Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting \\?\C:\Users\*******\.vagrant.d\boxes\mvbcoding-VAGRANTSLASH-awslinux\2017.03.0.20170401\virtualbox\box.ovf...
OK.
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Appliance import failed
VBoxManage.exe: error: Could not create the imported medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670
_1546506401977_30636\box-disk001.vmdk'.
VBoxManage.exe: error: VMDK: could not create new file 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546
506401977_30636/box-disk001.vmdk' (VERR_ALREADY_EXISTS)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)" at line 877 of file VBoxManageAppliance.cpp
我重新安装了 Oracle VirtualBox 和 Vagrant 软件。我尝试在删除“.vagrant.d”和“VirtualBox VM”后运行“vagrant up”命令,但问题仍然存在。
我不确定它从哪里抛出错误。任何建议都会有帮助!
另外,我附上 VirtualBox 的日志
00:00:00.616136 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670'}, preserve=false aResultDetail=0
00:00:00.617136 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not find file for the medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670\box-disk001.vmdk' (VERR_PATH_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:00.716925 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670'}, preserve=false aResultDetail=0
00:00:00.717926 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not find file for the medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670\box-disk001.vmdk' (VERR_PATH_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:23.975604 ApplImp ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={MachineWrap} aText={Could not create the settings file 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227.vbox' (VERR_PATH_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:23.976605 ApplImp ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227\box-disk001.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:25.142254 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670'}, preserve=false aResultDetail=0
00:00:25.144256 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not find file for the medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670\box-disk001.vmdk' (VERR_PATH_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:25.161267 Medium::Task ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not create the imported medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227\box-disk001.vmdk'.
00:00:25.161267 Medium::Task VMDK: could not create new file 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227/box-disk001.vmdk' (VERR_ALREADY_EXISTS)}, preserve=false aResultDetail=0
00:00:25.162269 ApplImp ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={8398f026-4add-4474-5bc3-2f9f2140b23e} aComponent={ApplianceWrap} aText={Could not create the imported medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227\box-disk001.vmdk'.
00:00:25.162269 ApplImp VMDK: could not create new file 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227/box-disk001.vmdk' (VERR_ALREADY_EXISTS)}, preserve=false aResultDetail=0
00:00:26.324906 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670'}, preserve=false aResultDetail=0
00:00:26.325907 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not find file for the medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670\box-disk001.vmdk' (VERR_PATH_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:26.340679 Medium::Task ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not create the imported medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227\box-disk001.vmdk'.
00:00:26.340679 Medium::Task VMDK: could not create new file 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227/box-disk001.vmdk' (VERR_ALREADY_EXISTS)}, preserve=false aResultDetail=0
00:00:26.341179 ApplImp ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={8398f026-4add-4474-5bc3-2f9f2140b23e} aComponent={ApplianceWrap} aText={Could not create the imported medium 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227\box-disk001.vmdk'.
00:00:26.341179 ApplImp VMDK: could not create new file 'C:\Users\*******\VirtualBox VMs\amzn-ami-hvm-201703020170401-x86_64-gp2-201704051103-guest-72463CQOefdxv_default_1491390639577_72670_1546520279927_40227/box-disk001.vmdk' (VERR_ALREADY_EXISTS)}, preserve=false aResultDetail=0
00:00:31.353526 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
最佳答案
在打开此问题的同时,我也开始遇到类似的错误。
我找到了一个临时解决方法:
vagrant up
,这将因 VERR_ALREADY_EXISTS
错误而停止company-base_default_1546511806177_12809
和 my-dev-vm
。.vmdk
磁盘镜像文件从目标文件夹移回基本 Box 文件夹,该文件夹仍应包含 .vbox
和 .vbox- prev
里面的文件。vagrant up
。我认为这一定是由于 Vagrant 与 VirtualBox 6 不兼容,或者重命名 API 的问题造成的。
关于vagrant - VBoxManage.exe : error: VMDK: could not create new file : box-disk001. vmdk' (VERR_ALREADY_EXISTS),我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/54019619/
我有 zsh-completions安装在arch linux上。完成VBoxManage命令似乎工作正常,但是 vboxmanage没有(即只是简单地完成本地目录中的文件)。两个VBoxManage
我在物理 Windows7 上的 VirtualBox 中运行 CentOS。现在在 centOS 我有 Docker,我需要运行 docker-machine create --driver vir
运行时出现以下错误 vagrant up 执行 Vagrant 使用的 CLI“VBoxManage”时出错 用于控制 VirtualBox。命令和标准错误如下所示。 命令:["hostonlyif"
我在Windows 7上使用VirtualBox 4.2.18和Vagrant 1.3.3。 Vagrant 的盒子添加MyBox http://ergonlogic.com/files/boxes/
我在 Virtualbox 中使用 Vagrant。我正在我的 Vagrant 文件中配置一个共享文件夹。但是,如果已创建共享文件夹,则尝试 vagrant up VM 时出现错误。 config.v
我想遍历正在运行的虚拟机并只返回引号之间的内容。 所以这个命令: VBoxManage list runningvms 返回: "UbuntuServer" {7ef01f8d-a7d5-4405-a
我需要在 vagrant/virtualbox 虚拟机上选择性地禁用主机时间同步。我可以像这样在主机上毫无问题地做到这一点: $ VBoxManage setextradata \ > "VBoxI
当我尝试向我的 VirtualBox 添加/删除共享文件夹时出现此错误: ~$ VBoxManage sharedfolder add dev --name srv --hostpath "/my/
VBoxManage.exe 是 Oracle VirtualBox 配套实用程序,它允许通过命令行控制 VM。它可以执行多种操作,包括开始/停止和屏幕捕获。 我感兴趣,它使用哪个 API? 如果没有
当我尝试向我的 VirtualBox 添加/删除共享文件夹时出现此错误: ~$ VBoxManage sharedfolder add dev --name srv --hostpath "/my/
我想删除安装在 VirtualBox 上的给定虚拟机(本身安装在 Windows XP 上)。当我从 CMD 运行命令时,删除如我所料。但是当我运行这段代码时: import subprocess m
我有一个名为“mongo”的 VirtualBox 图像。 当我启动 Windows 并尝试从 cygwin 启动虚拟机时,VBoxManage 说它找不到机器: /cygdrive/c/Progra
我刚刚在我的 Windows 7 机器上安装了 Docker Toolbox。安装后,我运行 Docker Quickstart 终端,显示以下消息: 看起来在步骤 nLooking for vbox
我在命令行中遵循 Data Science 的安装教程,其中包括以下步骤: $ mkdir MyDataScienceToolbox $ cd MyDataScienceToolbox $ vagra
关闭。这个问题不满足Stack Overflow guidelines .它目前不接受答案。 想改善这个问题吗?更新问题,使其成为 on-topic对于堆栈溢出。 7年前关闭。 Improve thi
我在尝试初始化 Vagrant 时遇到了问题。安装了一个带有 Vagrantfile 的文件夹,并安装了 VirtualBox 和 Vagrant。使用 hashicorp/precise32 框,在
尝试在 Android-Studio 中启动 Genymotion 时出现以下错误:我已经找到了这个 genymotion-invalid-path-vboxmanage-and-initialize
在我的 homestead 目录中第一次运行 vagrant up 后,我的电脑蓝屏了,因为启用了 Hyper-V。现在,在禁用 Hyper-V 并运行 vagrant up 后,我收到此错误: Th
这是cmd错误,我不明白错误在哪里,我一次又一次地碰到它,无法解决它。 $ vagrant up Bringing machine 'default' up with 'virtualbox' pro
我刚刚使用Powershell让Laravel宅基地昨天运行。现在,它甚至无法运行。我只是暂停了 Vagrant 并关闭了我的电脑。现在,这只是给我这个错误: Bringing machine 'de
我是一名优秀的程序员,十分优秀!