-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vmcloak-install crashes with adobe9 #43
Comments
Oh, forgot to reply here, sorry. Did you already resolve this issue in the meantime? |
This issue always happens when i try to install adobe. I tried it several times and i always had this happen. But no i sadly did not resolve it in the meantime. I think i tried it with office. I am not sure on this tho. I can tell you more tomorrow. |
Okey so office produces the same kind of error. So i guess the other programs will too. After office I tried a different program and i got a different error this time
(I replaced parts of the path with dir but the rest is the actual path) If you then try to clone the VM with this error you get yet another different error:
|
Oh what I forgot to mention is that I try to install the programs on a winxp VM. Maybe that is the cause of the Problem. |
So one of the issues is that the VM already exists. So basically VMCloak creates a temporary VM (e.g., Windows XP and Windows 7 have both been tested plenty of times and should work mostly out of the box. |
In my experience, deleting the *.vbox in $HOME/.vmcloak/vms/[VM_NAME]/VM_NAME.vbox works. I did that a lot when my scripts failed and I have yet to see a problem caused by this. The VBoxManage unregistervm basically does that if you decide to keep the files if I am not mistaken. Jurriaan, would you see a potential problem with that ? |
Yeah, that should be fine :) |
Well i knew that i just have to delete and then reinstall the VM to get it accessable again. But that sadly doesn't fix the initial issue. |
is this still an issue ? AFAIK the main lock issues which cause random other issues should be resolved now with 3.12 |
What @razuz said - please re-open or create a new issue if you run into any other problems. |
The error:
The text was updated successfully, but these errors were encountered: