search

hatching / vmcloak

Automated Virtual Machine Generation and Cloaking for Cuckoo Sandbox.
483 stars 120 forks source link

Installing Cuckoo using VMCloak Error #108

Open justr00t opened 7 years ago

justr00t commented 7 years ago

Hello, I am using this repo to do an install of cuckoo https://github.com/benrau87/AutoCuckoo. After I am done doing the setup, it runs VMCloak. When I get to the step to install adobe9, wic, pillow, etc, it just hangs. What happens at that point is that the VM boots back up but does absolutely nothing. I was wondering why it's not actually installing. Separate question, as you can see, I named this "Cuckoo2" but I would really like it to be named cuckoo1. I tried and failed with cuckoo1 and when I tried again, it said the name was taken so I took Cuckoo2. Do you know a way to delete the old VMs so that I can still use the name cuckoo1? Thanks screenshot from 2017-05-19 15-02-22

Hullgj commented 7 years ago

What happens at that point is that the VM boots back up but does absolutely nothing. I was wondering why it's not actually installing.

  1. If you think the VM is hanging open VirtualBox, select the VM that is running; Cuckoo2, and click on Show. Then you should see the user interface and identify anything that prevents the installation. It could be a popup window, or Windows activation query.

Do you know a way to delete the old VMs so that I can still use the name cuckoo1?

  1. To delete old VMs you can unregister it with VirtualBox either through the CLI or GUI, and remove the files and directories of the relevant image under ~/.vmcloak/vms/[the image]/. Such as to remove cuckoo2 image:

$ VBoxManage unregistervm cuckoo2 $ rm -rf ~/.vmcloak/vms/cuckoo2/

anna-g-arbeiter commented 7 years ago

Hi, I had the same problem with a hanging vmcloak install with version 0.4.3, virtualbox 5.1, and fresh Ubuntu server 64 4.4.0-79. I figured out that the vboxnet0 interface wasn't up during the install, even if the vmcloak-vboxnet0 script was executed before.

Bringing up the interface manually during the hanging vmcloak install worked, and the install continued, but this workaround is a bit ugly. ip link set vboxnet0 up

jbremer commented 7 years ago

The VM hanging could sometimes mean invalid configuration and/or invalid serial key provided as well. Please take a look at the screen of the VM (either through the GUI or using vboxmanage controlvm vmname screenshotpng /tmp/1.png. @justr00t regarding AutoCuckoo, I imagine this script might now be outdated while Cuckoo & VMCloak are always evolving and - sometimes such as with our recent Cuckoo 2.0.0 release - not always in a backwards compatible way.