Skip to content
This repository has been archived by the owner on Oct 4, 2019. It is now read-only.

Works perfectly on OS X but fails on windows with access denied errors on .vmem #61

Closed
charandas opened this issue May 15, 2014 · 4 comments

Comments

@charandas
Copy link

This happens after almost all steps of installation are done, and chef script is run.

'vmware-iso' errored: remove output-vmware-iso\564dfbe7-d762-be2a-1600-9b769835764e.vmem: Access is denied

Tried powershell, but the result remains the same. Any clues?

I am using a fork with my own JSON for windows embedded 8.1, which is practically windows 8.1.

@joefitzgerald
Copy link
Owner

That looks like a Packer / VMware Workstation issue. I haven't see it before, but Access Is Denied is often something that occurs in one of the following scenarios:

  • You run into UAC privilege issues
  • A file is still in use

@StefanScherer
Copy link
Collaborator

I run into the same issue and start to investigate what's going wrong. With a set PACKER_LOG=1 before calling packer I have found out that packer assumes that the vm is clean, but this is done only with some sleeps. Propably this is not enough to wait for all other VMware processes to exit and release all file handles.

The code to be improved in packer is about here: https://github.com/mitchellh/packer/blob/master/builder/vmware/common/step_shutdown.go#L134

I'll try to fix this.

@StefanScherer
Copy link
Collaborator

You may follow the progress in hashicorp/packer#1267

@charandas
Copy link
Author

Thanks for the link. Closing this for now.

dreamflash pushed a commit to dreamflash/packer-windows that referenced this issue Feb 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants