==> virtualbox-iso: Error configuring VirtualBox to suppress messages: VBoxManage error: VBoxManage.exe: error: Failed to create the VirtualBox object!==> virtualbox-iso: VBoxManage.exe: error: The object is not ready==> virtualbox-iso: VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient==> virtualbox-iso: Deleting output directory...Build 'virtualbox-iso' errored: Error configuring VirtualBox to suppress messages: VBoxManage error: VBoxManage.exe: error: Failed to create the VirtualBox object!VBoxManage.exe: error: The object is not readyVBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient==> vmware-iso: Error starting VM: VMware error: Error: There was an error in communication==> vmware-iso: Deleting output directory...Build 'vmware-iso' errored: Error starting VM: VMware error: Error: There was an error in communication
==> Some builds didn't complete successfully and had errors:--> virtualbox-iso: Error configuring VirtualBox to suppress messages: VBoxManage error: VBoxManage.exe: error: Failed to create the VirtualBox object!VBoxManage.exe: error: The object is not readyVBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient--> vmware-iso: Error starting VM: VMware error: Error: There was an error in communication
==> virtualbox-iso: Error configuring VirtualBox to suppress messages: VBoxManage error: VBoxManage.exe: error: Failed to create the VirtualBox object!==> virtualbox-iso: VBoxManage.exe: error: The object is not ready==> virtualbox-iso: VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient==> virtualbox-iso: Deleting output directory...Build 'virtualbox-iso' errored: Error configuring VirtualBox to suppress messages: VBoxManage error: VBoxManage.exe: error: Failed to create the VirtualBox object!VBoxManage.exe: error: The object is not readyVBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient==> vmware-iso: Error starting VM: VMware error: Error: Unknown error==> vmware-iso: ==> vmware-iso: Packer detected a VMware 'Unknown Error'. Unfortunately VMware==> vmware-iso: often has extremely vague error messages such as this and Packer==> vmware-iso: itself can't do much about that. Please check the vmware.log files==> vmware-iso: created by VMware when a VM is started (in the directory of the==> vmware-iso: vmx file), which often contains more detailed error information.==> vmware-iso: Deleting output directory...Build 'vmware-iso' errored: Error starting VM: VMware error: Error: Unknown error
Packer detected a VMware 'Unknown Error'. Unfortunately VMwareoften has extremely vague error messages such as this and Packeritself can't do much about that. Please check the vmware.log filescreated by VMware when a VM is started (in the directory of thevmx file), which often contains more detailed error information.
==> Some builds didn't complete successfully and had errors:--> virtualbox-iso: Error configuring VirtualBox to suppress messages: VBoxManage error: VBoxManage.exe: error: Failed to create the VirtualBox object!VBoxManage.exe: error: The object is not readyVBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient--> vmware-iso: Error starting VM: VMware error: Error: Unknown error
Packer detected a VMware 'Unknown Error'. Unfortunately VMwareoften has extremely vague error messages such as this and Packeritself can't do much about that. Please check the vmware.log filescreated by VMware when a VM is started (in the directory of thevmx file), which often contains more detailed error information.
--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/0ab765e5-b65a-4a4d-9516-bef9fa5293c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/0ab765e5-b65a-4a4d-9516-bef9fa5293c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Alvaro
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/0ab765e5-b65a-4a4d-9516-bef9fa5293c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Alvaro
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/17e86fd0-f110-4447-9a2a-20735ee72c85%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/17e86fd0-f110-4447-9a2a-20735ee72c85%40googlegroups.com.
--Alvaro
mkdir c:\packertestcd c:\packertestcd ubuntunotepad ubuntu1604.json
"iso_checksum": "f3532991e031cae75bcf5e695afb844dd278fff9", "iso_name": "ubuntu-16.04.3-server-amd64.iso",
packer build -var-file="ubuntu1604.json" -only=virtualbox-iso -only=vmware-iso ubuntu.json
nssm install aaaPackerTest packer build -var-file="c:\packertest\ubuntu\ubuntu1604.json" -only=virtualbox-iso -only=vmware-iso c:\packertest\ubuntu\ubuntu.jsonnssm set aaaPackerTest AppDirectory c:\packertest\ubuntunssm set aaaPackerTest Start SERVICE_DEMAND_START
$pwd = ConvertTo-SecureString "P@ssW0rD!" -AsPlainText -ForceNew-LocalUser "packerTest" -Password $pwd
nssm set aaaPackerTest ObjectName .\packerTest "P@ssW0rD!"nssm set aaaPackerTest AppExit Default Exitnssm set aaaPackerTest AppStdout c:\packertest\log-out.txtnssm set aaaPackerTest AppStderr c:\packertest\log-err.txtnssm set aaaPackerTest AppStdoutCreationDisposition 2nssm set aaaPackerTest AppStderrCreationDisposition 2nssm set aaaPackerTest AppEnvironmentExtra PACKER_LOG=1 PACKER_LOG_PATH=c:\packertest\packer.log
Start-Service aaaPackerTest
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/17e86fd0-f110-4447-9a2a-20735ee72c85%40googlegroups.com.
--Alvaro
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/310426c8-f070-43bd-bfcc-446d8a0c9f52%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
I edited the Launch permissions and added the Account to the list. That allowed the Virtualbox part to work.
I was not that fortunate with VMWare. I do not believe it's possible in principle with it. I was able to find some VIX log files that identified that vmrun was not able to connect to vmware-auth daemon. I'm suspecting that in headless mode it might not be possible at all (the unprivileged account works in headed mode if not in a service but that, does not help much with headed mode, that is connected differently).
The last straw was somewhat unrelated happening: when I ran `vagrant up` for a vmware machine I got this nice message:
"When using Vagrant with VMware Workstation on Windows, Vagrant must
run with administrative privileges. I realize this is not ideal,
but this is the only way to make network modifications with VMware.
Please run Vagrant in a console with Windows administrative privileges."
That convinced me me that vmware internal workings in entirely FUBAR, and I was exhausted after 2 days of investigation and experiments, so I gave up.
I accept, that this is something that can be solved only by someone who developed VmWare suite, which is not very likely.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/310426c8-f070-43bd-bfcc-446d8a0c9f52%40googlegroups.com.
--Alvaro