I am facing an issue when I try to run the cuckoo sandbox after all the installation.
Host Machine: macOS machine with VMware Fusion running. Guest : Windows VM
I installed the Cuckoo Sandbox in a virtual environment within macOS. I did edit the vmware.conf, memorey.conf, cuckoo.conf & processing.conf files.
When i do run the "cuckoo" command to start; it says it doesnt have permisssion to access the .vmx file I mentioned in the "vmware.conf" file.
I have given 777 permission to the entire folder. Not sure why the system gives me such an error.
If you have created a user in the system for the cuckoo sandbox, kindly assign appropriate privileges to the cuckoo sandbox user.
Related
I m trying to cross-compiling a simple HelloWorld app in C++ on Win 10 for raspberry pi3. I installed toolchain to configure it out. But till now by creating new ssh connection i got always an Error such as "Access denied" or "No connection could be made bcz the target maschine actively refused it".
I checked many tutorials to cross-compiling but no success till now
I think you are mixing different stuff here.
Cross compiling means compiling (and linking) the software for the embedded target on the host computer (in your case Win10). You don't need to SSH on the target for this. You'll likely need to run your configure your build like this:
./configure --host=arm-linux --build=amd64-pc-linux-gnu
The host argument is where the binary should run, and the build argument is where the binary is built.
However, I suspect that you've successfully built the software on your Win10 computer, and then you're trying to copy it on the embedded device. In that case, you must make sure that:
The embedded device is connected to the network
It's running a SSH daemon (likely opensshd)
It's allowing your user to connect to (typically, on default installation, root is not allowed to connect, you'll need to modify /etc/ssh/sshd_config to PermitRootLogin to yes)
(Optionally) You generate a key pair on the host (via ssh-keygen and copy the public key on your embedded user's .ssh/authorized_keys folder) to allow password-less login
Please refer to SSH man page.
With all the above in place, you can then scp build/mySoftware root#myDevice:/usr/local/bin without the Access Denied message.
I have been following this guide: https://www.virtualbox.org/manual/ch04.html#sf_mount_auto
I am running ubuntu 16 with a Windows 2016 VM guest, the VM name is "WindowsServer2016". I need to create a shared folder that is in my home: /home/heatdeath/For_Virtual (is the name of the folder in Ubuntu that I want to share)
In virtualbox I have added the folder to the shared folder, and enabled auto-mount. Yet when I go into the Windows VM, and look under networks, there is no shared folder.
So instead of auto-mounting, I try manually by using
net use x: \\vboxsvr\For_Virtual
And I get the error:
System error 53 had occured
The network path was not found
I also tried vboxsrv.
Kinda at my wits end with this, done alot of research and nothing new turns up. Any help appreciated
Indeed difficult & frustrating to solve, if you don't know.
My Linux distro didn't include VBoxAdditions.iso
I finally found it at http://download.virtualbox.org/virtualbox/
under the version of virtualbox installed.
First, make sure that you belong to the vboxsf and vboxusers groups, and usb if you want to use usb access. (It might be a bit different on your distro)
Just download the iso to a convenient location
(I use the same folder for all the msw sources),
and select it via the cd/dvd option in virtualbox.
Then start the guest session, and in the menu at the bottom of the guest window, make sure that the iso is selected, and start it from the guest file manager.
When finished installing, select reboot.
After, all the defined shared folders appear automatically as virtual optical disks just after the virtual hard disk and the virtual optical installation disk.
BTW, I tried to get help on the virtualbox forum, just getting a rude response.
I finally found the answer with an internet search.
I am trying to create folders and file in Virtualbox shared folder from Host to guest.
But i get this error mkdir: cannot create directory : Protocol error.
Below are steps i performed to share folder
1:My host OS is Ubuntu and my guest is Ubuntu.
2:I attached a share folder to virtualBox VM
Folder Path:/DR/vault/config
Folder:config selected automount and make permanent.
3:In Guest OS i installed virtualbox guest additions
4:I am trying to mount folder on /mount/config path
I added entry in guest's /etc/fstab as
/config /mount/config vboxsf rw,uid=1000,gid=1000 0 0
Path gets successfully mounted after Guest reboot also i can see the files created in /DR/vault/config(Guest) to /mount/config(Guest) but i cant create folder or file in /mount/config (Guest)
Please suggest if anything is missing or if there is any other way.
In my case, I had the drive full, clearing some space on the drive solved the issue.
I have found this is a problem with filename lengths on DOS hosts.
I have been using VirtualBox VMs as a form of containerised environment for deploying to a JBoss server, having experienced far too many problems with Windows environments for said technology.
I was using a shared-directory with my host machine as I was trying to keep the virtual machine lightweight (i.e. keeping IDEs in the host machine), then checking code into the shared directory for deployment with Maven. However, maven was giving some odd errors when the directory length grew to over 255 characters. Try looking at your file absolute path (type "pwd") and seeing if it's longer than 255.
I've resolved this problem with the following:
On the guest machine, add your user to vboxsf group: sudo adduser username vboxsf
Restart the host machine.
My host OS is Windows, my guest OS Ubuntu.
This might be an indication that the folder does not have the correct permissions on the Virtualbox host.
E.g. my headless Virtualbox server is running as "vbox" user, so I had to give that user write permissions on the host folder.
I had a similar issue, turns out that for me it was the number of folders or length of path name involved in mkdir.
typically I had :
mkdir -p /projects/bot/node_modules/webpack/node_modules/uglifyjs-webpack-plugin/node_modules/uglify-js/node_modules/yargs/node_modules/cliui/node_modules/center-align/node_modules/align-text/node_modules/kind-of/node_modules/is-buffer
Manually I could create up to the last part of the path but not the 'is-buffer' folder
I am working in vagrant and my projects folder is a shared VM folder, maybe/probably windows' max path length is the reason.
I'm planning to install Visual Studio (for editing .aspx files) in a guest VM.
If I'm working in the Host computer, is there a way to open a file on that Host with a program in the Guest VM?
You could use the Shared folder feature for access to files on a host machine from Guest VM. To use this feature you should install the VMware tools on Guest VM. After setting up the Shared folder, you can access files on the host in a path like “\.host\Shared Folders\Test files”.
To send a command to open file on Guest OS from the host you could use vmrun utility, which helps you manage virtual machines from command line (for more detail see this official manual and examples in “Running Guest Applications”). On the other hand, you could just open a VM console and run script manually :)
In addition, I don't recommend to install Visual Studio on Guest VM. The Visual Studio will always execute faster on the host. Moreover, you will be more convenient to work with snapshots and few VMs. In this case, you could use remote debugging tools for debug and automatically deploy your application on Guest VM after build.
Ok, here's a very short and to the point question. When trying to import a virtual PC 2004 Windows 2003 Server VM in VM Workstation 6.0.2 I'm getting an error 'unable to determine guest operating system'. Soo how to fix?
From here:
Make sure that that the VM is not currently running in VMware Server.
Make sure that VMware Server does not have a lock on the VM’s files. You have have to stop all VMware Server Services and/or reboot the (VMWare) server.
Make sure you have appropriate permissions to the VM’s files.
This is a fairly generic error from VMware Converter so I would try the following:
Step 1. Make sure you are running the latest version of VMware Converter. Updates seem to come pretty often for this tool.
Step 2. Check the VMware Converter log file. More often than not you will find the source of your problem here.