>>because per logs packer runs fines, is vmware/virtualbox that fails to
the their job
Well, yes, but since the intimate relationships between packer and
vmware/virtualbox are not in the plain sight it's not immediately obvious.
So I had to run sysinternals procmon to be able to capture
can you create VMs using Virtualbox or vmware?
because per logs packer runs fines, is vmware/virtualbox that fails to the
their job
you can use VBOXMange to do lots of things
try create an empty VM and boot
or deploy a VM from OVA and boot
Also note that as soon as you add `packerTest` user to the admin group,
suddenly it works.
On Thursday, 10 August 2017 08:17:03 UTC+12, andr...@gmail.com wrote:
>
> Here is how one can reproduce this behaviour.
>
> Make sure you are running Windows 10 or Windows Server 2016 with:
> - Virtualbox
Here is how one can reproduce this behaviour.
Make sure you are running Windows 10 or Windows Server 2016 with:
- Virtualbox
- Vmware Workstation
- Windows Management Framework 5.1
- nssm
All commands are run from elevated powershell prompt.
Run:
mkdir c:\packertest
cd c:\packertest
git clone
No there is no Antivirus.
>> I can login, open VMWARE/Virtualbox and ofcourse packer runs fine.
Well If I login it also runs fine. It does not run fine from within service.
>>Is anything that impedes you to run into a nomal user, or directly from
TC agent run packer?
I'm not sure what you
Hello
So is there any Antivirus? can you disable it?
It seems realted to the processes in this case virtualbox and vmware not
being able to create COM objects.
I have TeamCity at home, and I use the agent to run under a normal user, so
I can login, open VMWARE/Virtualbox and ofcourse packer
Here is the verbose
log https://gist.github.com/AndrewSav/670622133d5b24e00b6d85308254fd34
I used this https://nssm.cc/ to create a windows service that points to a
command file that starts packer (with the same command line that works
interactively, and also as runas). The logs produced are
Thank you for your reply! Yes, it's windows.
runas works without error - as long as it's run interactively, that is not
from a windows service it works.
I set the variable and I examined the more verbose log. No additional clues
found. :(
Andrew
On Wednesday, 9 August 2017 21:15:49 UTC+12,
Hello
is this windows?
you can use runas to manually run the tools and see where it fails. perhaps
to a user without admin first.
you can set a variable PACKER_LOG=1 to get more verbose messages.
