I've configured Cuckoo on my host machine, now trying to setup the guest machine where the malware suppose to be executed. The guest machine will be Ubuntu not Windows, but I don't know what should be done on the Ubuntu machine to mkae it Cuckoo guest machine. Where the guidance of Cuckoo shows the steps for configuring Windows 7 machine as guest machine, but nothing mentioned about Ubuntu, though Cuckoo supports linux malware analysis.
Related
So I have this work computer that I'd like to play fortnite on, but it doesn't have the latest version of directX installed in it so I can't just install fortnite to my flashdrive and play.
So I've been researching on getting a portable Windows 10 Virtual Machine on my flashdrive, which has fortnite installed in the VM. However, apparently Virtual Machines don't utilize the host's GPU by default. I'm trying to find out a way to let the Virtual Machine use the native GPU. I've seen that it's completely doable on a Linux host, but I can't find anything about GPU passthrough on a windows10 host.
Note: my work computer does support VT-d, and it is locked down so I can't do anything to it that requires elevated privileges like installing stuff, changing the BIOS, or booting off an external harddrive.
I have CentOS7 installed on Vmware, and I'm able to access it through SSH from my computer where Vmware is installed. I need to access my virtual machine from another computer. Is this possible? and what are the steps to complete this?
It is possible. You need to bridge your network adapter with the one on the VM, and then it will be accessible the same way your PC is.
I am running a virtual machine in Bluemix and want to open the OS's desktop GUI. How do I do this? Thanks for your help.
I've edited your question to what I think you're asking: How can I open the desktop GUI on my virtual machine in Bluemix?
Assuming I understand the question correctly:
To open the desktop GUI on a remote virtual machine, use Virtual Network Computing (VNC). This solution is not specific to Bluemix; it'll work with a VM running on any platform, as long as the VM is running an OS that supports VNC.
To use VNC, you need to have a VNC server running in your VM's OS. You will then run a VNC client (a.k.a. viewer) on your computer to display the VM's desktop. The specific instructions depend on the OS running in the VM and on your computer.
For example, assuming your VM is running Ubuntu v14.04, these resources explain what to do (and a search will find other resources):
"How to Install and Configure VNC on Ubuntu 14.04" -- Installs XFCE4 as the VNC server
"How To Install And Configure VNC On Ubuntu 14.04" -- Also installs XFCE4.
"How to Install VNC Server on Ubuntu 14.04 LTS" -- Installs TightVNC as the VNC server
For a VNC client, I actually connect to remote VMs via a local VM running Ubutu 14.04, so I use Vinagre (a.k.a. the Remote Desktop Viewer app). Options listed by other authors include TightVNC, RealVNC, or UltraVNC.
Good luck and thanks for using Bluemix.
From what I understand, you need some remote desktop tool to get to the UI of the OS of your virtual machine. Some tools available: http://www.techradar.com/us/news/software/applications/7-of-the-best-linux-remote-desktop-clients-716346
Currently trying to setup the mininet virtual machine. I did all according to the instructions. Before proceeding following is my setup details.
My host platform - Windows 8.1
My guest OS : Ubuntu 14.04, 32-bit with mininet. I downloaded the
ovf this one - mininet-2.2.0-141209-ubuntu-14.04-server-i386. Running on VirtualBox
I installed the required packages on the mininet-ubuntu-server (xserver-xorg-core,xserver-xorg,xorg,xorg openbox,ubuntu-desktop). One package fxlrg, I could not install as it was saying "unable to locate package"
Then I used the command "startx" on virtualbox console, it started the ubuntu desktop but very slow and with poping up 4 to 5 errors.
I have already setup the network for host-only adapter, I am able to ping from host machine to guest machine, I am able to ssh from host machine to guest machine using PuTTy. I am able to login with no problems.
But I don't know to see the x11 window from PuTTy. I have already enabled the X11 forwarding on PuTTy and I have already installed the Xming on windows. Please suggest how to debug and how to fix this. I have no idea how to proceed now.
You may need to enable X11 SSH Forwarding in the /etc/ssh/ssh_config file.
I have Windows 7. Installed VirtualBox and Ubuntu 11.04 as guest OS.
Networking is done by NAT.
Everything is fine: I have internet on Ubuntu.
I can access Windows from Ubuntu by its ip.
But i can't access Ubuntu by it's ip which is shown by ifconfig.
I run rails on Ubuntu.
How can I solve this problem: connect to Ubuntu/Rails server on ort 3000 from my Windows?
By default, VirtualBox's NAT allows the virtual machine to access the Internet ; but doesn't allow the physical machine to access the Virtual one.
The simplest solution would be to use another networking setting than NAT, for your Virtual Machine -- for instance, bridge should work fine (your VM would be visible on your network, though).
Another solution would be to use port forwarding ; about that, this article might help : Howto Access via ssh a Virtualbox Guest machine.
I used to struggle with configuring a similar setup until I found Vagrant. Vagrant makes it very simple to setup, connect to and work with a Linux virtual machine. After Vagrant is configured you can just type vagrant ssh to enter the virtual machine and your account has automatic sudo rights and everything works as expected - you don't even have to deal with logging into the vm. The initial setup for ssh does look to be a little more work under Windows though as you need to configure Putty before you can connect.
There is a simple configuration file in Vagrant that you use to specify which ports from the VM you want forwarded to your machine using a syntax like:
config.vm.forward_port("rails", 80, 3000)
config.vm.forward_port("tomcat", 8000, 8080)
and everything is taken care of. Details are here
If, for example, you are using Rails and you start vagrant with the command vagrant up in your Rails project directory than that directory is available on the VM. Since it is the same shared directory between machines, any changes you make in your Rails project directory on your machine using your regular editor is seen on the VM also. This makes testing in other environments very easy.
Instructions for setting Vagrant up with Windows are here and a RailsCast about it is here. Note that Vagrant has nothing to do directly with Rails - you can use it for setup of any virtual machine environment you need.
In short, you can't.
It is a local host not a public domain therefore not publicly accessible outside of your virtualbox environment.
Maybe someone has a clever hack for this but why would you want to do this in the first place?
Your solution is to either use firefox to browse to your localhost within your virtualbox linux session or develop on windows.
Personally I work the other way round I run Ubuntu 11.04 and I have virtualbox installations of xp, 2,000, me, vista and 7 so I can test in different environments. Inevitably I end up sharing my project folder from Ubuntu so that I can run the project in whatever OS I am testing for.