-
Notifications
You must be signed in to change notification settings - Fork 124
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
Request: Improve VMCloak logging #55
Comments
I have personally not really tested the 32-bit Windows 7 stuff yet. |
Could you, please? |
I'll take a run with that latest tomorrow ... lets see if I can reproduce that |
just tested and it works fine on 32bit. |
one thing you can try is to click "Ctrl+C" on the python window if that makes any difference |
Ctrl+C just closes python.exe window. |
are you running on latest code from master ? |
Latest at the day of creating this issue. |
sort of running out of ideas :) can vboxnet0 interface and vm see each other ? maybe some iptables rules are killing the comms ? |
How to check it (ping is working)? |
ping is one thing but you can also try to telnet to port 8000 against vm IP from mint side |
But when installing Windows, it installs Python, so it works, doesn't it? |
yes it should ... I'm quite impressed that it cannot install packages there and gets stuck |
Could you make some log system for vmcloak, so we may find step, when it stucks? |
we could do that ... but not this week |
I got the same problem. I've created a win7 (x64) virtual machine with vmcloak (not fully automatically, I still need to manually click). When I ran "vmcloak install seven0 adobe9", I can see the virtual machine seven0 is running, but doing nothing. |
are you running latest version ? BR,
|
Yes, I am running the latest version. The problem seems solved after I changed another window ISO file. It will be great if you can improve the logging. Anyway, vmcloack is and will be a great tool. |
cool :) apart from couple other things I'm working to improve logging ... PR should be upcoming soon |
it's just a wild guess, but I think this issue can be closed :) --debug flag has become quite verbose and points out possible issues nicely |
Trying to install
adobe9
: just python.exe empty window is visible in VirtualBox window.There is no any Adobe processes created in VM, there is no something non-standard processes too.
The text was updated successfully, but these errors were encountered: