Posts

Showing posts with the label vbox

UUID of the medium does not match the value stored in the media registry

If you try to load a VM to VBox and it name previously exists in the records with a different UUID, you will get this error. NS_ERROR_FAILURE(0x80004005) In VBox you will see a message that said your hard disk is inaccessible. To fix it, you need replace the new UUID in the configuration (.vbox file) of your VM. Copy from ~/.config/VirtualBox/VirtualBox.xml the respective UUID from your virtual disk (see MachineEntry uuid). After, replace the UUID in your .vbox configuration file inside your VM folder. Enjoy it!

Increment your VM storage size in VBox

Image
The reason of this tutorial is because I was playing with a Virtual Machine and I overfill the hardisk space. To resize the storage, first you need de-attach the hardisk from your VM and close VBOX. Later, you need convert your .vmdk to a .vdi file with the following command: vboxmanage clonehd ./machine.vmdk clone.vdi --format vdi  VBoxManage: error: Cannot register the hard disk 'machine.vmdk' {4e55fd9e-f496-4cbf-9610-ad2f8c6b8634} because a hard disk 'machine.vmdk' with UUID {4e55fd9e-f496-4cbf-9610-ad2f8c6b8634} already exists VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 178 of file VBoxManageDisk.cpp If you get this error, you must change the UUID from your VM with the following command: vboxmanage internal...

Could not get the storage format of the medium .iso (VERR_NOT_SUPPORTED).

Image
This is a typical problem in VBox when you try to load a corrupted iso file. Check if your iso has the same original iso hash with the following commad: md5sum file.iso In my case, I could check the hash in gparted download section, and effectively was different.

Install ASDM 6.4(9) for an ASA 5520 in GNS3

Image
In my last post , I use a TAP interface to connect a VBox network to my pc. Now, I going to show you how to install Cisco Adaptive Security Device Manager (ASDM) in an ASA firewall. First, you can download ASA iOS from  http://www.mediafire.com/download/c228c2sjdyrkwf3/ASA_842.7z Extract the files and add a new Qemu image in GNS3. Configure as follows: Connect ASA to a cloud with TAP interface to be in the same network. Maybe you can get this error at the moment to play your project: Execution log: Failed to initialize module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so Note: only modules from the same build can be loaded. Failed to initialize module: /usr/lib/x86_64-linux-gnu/qemu/block-rbd.so Note: only modules from the same build can be loaded. qemu-system-x86_64: -netdev tap,id=gns3-0,ifname=tap0,script=no,downscript=no: could not configure /dev/net/tun (tap0): Operation not permitted qemu-system-x86_64: -netdev tap,id=gns3-0,ifname=tap0,scr...

Configure a Vbox network for GNS3 with Internet through a cloud with a TAP interface

Image
Today we going to configure a virtual network within GNS3. We can download older GNS3 versiones from sourceforge or the most recent from  gns3.com. We need to add the repositories to apt and after install gns3: sudo add-apt-repository ppa:gns3/ppa sudo apt-get update sudo apt-get install gns3-gui To have a connection to access Internet through our physical interface, we create a TAP interface (virtual bridge): sudo apt-get install uml-utilities modprobe tun tunctl ifconfig tap0 10.0.0.1 netmask 255.255.255.0 up On the last line, you configure the ip, that will be the gateway for your virtual topology. Now, as we need forward the packets, between the virtual network and your physical router, you must enable the forwarding option: sudo iptables -I INPUT -j ACCEPT -i tap0 sudo iptables -I OUTPUT -j ACCEPT -o tap0 sudo sysctl -w net.ipv4.ip_forward=1 Now, you need an appliance or a any host image to create our virtual network. You can use a minimal Ubuntu version ...