Hi guys : I am trying to run the Cloudera Hadoop VM in Virtual box.
First, I noted that the download is a .vmdk file. Of course, this suffix is for VMWare, so that was a bit odd.
Luckily, I found a tutorial on how to convert the cloudera vmdk into a virtual box file here : http://www.ubuntugeek.com/howto-convert-vmware-image-to-virtualbox-image.html. However, when I tried to convert the vmdk file to a virtual box file by using convertdd, and ultimately got a message that "Failed to write to disk image "cdh.vdi" VERR_DISK_FULL"
So my question is , how do you run the Cloudera Hadoop VM in vbox ? I found a site http://www.facebook.com/note.php?note_id=108313592002 here, but it does not appear to work (this site suggests loading the VMDK image as a new hard disk, but "new" hard disks are not enabled in my fresh virtual box install). I only get "remove" and "refresh" options in my VBox disk manager.
OUTPUT FROM VBOX CONVERTING TO CDH
~/Development$ VBoxManage convertdd /tmp/vh.bin cdh.vdi
Converting from raw image file="/tmp/vh.bin" to file="cdh.vdi"...
Creating dynamic image with size 5475663872 bytes (5222MB)...
VBoxManage: error: Failed to write to disk image "cdh.vdi": VERR_DISK_FULL
:~/Development$ ls
VBox supports VMDK since v2.0 AFAIR.
VBox UI of Virtual Media Manager changed in 4.0 version, so there is no direct option of adding hard disk in Virtual Media Manager (there used to be one -- strange decision in my opinion).
Although, you can create a new virtual machine in Virtualbox, and in the stage of choosing disk, choose existing one (VMDK) so you don't need to convert VMDK to VDI (there is a dropdown, but besides, also a button to choose a hard disk file not listed yet in Virtual Media Manager.
Here is a guide from Cloudera themselves: http://www.cloudera.com/blog/2009/07/cloudera-training-vm-virtualbox/
I created a new VM using Red Hat 64b. Chose existing drive and opened the vmdk file. Gave it 2G Ram and it started up fine.
Related
I have Virtual box and a customized vagrant box. The thing is that my own laptop (Macbook) has only about 10 Gb of free space. So I bought a 128Gb USB Stick. Now I need to figure out a way to boot up vagrant boxes on this usb stick instead of the default hard drive of my laptop.
Almost all google articles explain how to boot up from the usb. But this is not what I exactly want. Have you ever been through such a situation?
any help would be appreciated!
you can do 3 things :
move your vagrant home directory with all the box on the USB stick (if you have many boxes, it will save some space)
you need to set $VAGRANT_HOME environment variable
move your VirtualBox VM to the USB stick; Open VirtualBox preferences panel and select the new default location folder for VMs. You would need to remove/re-add the VMs in VirtualBox after you moved all files to the external hard drive
You can use Linked Clones
By default new machines are created by importing the base box. For large boxes this produces a large overhead in terms of time (the import operation) and space (the new machine contains a copy of the base box's image). Using linked clones can drastically reduce this overhead.
Linked clones are based on a master VM, which is generated by importing the base box only once the first time it is required. For the linked clones only differencing disk images are created where the parent disk image belongs to the master VM.
It will not help for existing vagrant VM but for your new project, it will help to save space
I have a Mac OS X (10.11) virtual machine. But it has stopped working. It just about finishes loading the virtual machine and then just freezes on a black screen. Anyway, I wanna know if there is a way for me to recover the files on that virtual machine (Specifically Xcode files). They were not part of the shared folders so I'm not sure how to access them from the host (which is a windows 10).
One way to do this is to do the following:
Create another virtual machine with Ubuntu
Attached the virtual disk image (.vdi) or whichever format you chose to store the OSX image as a second HDD to the Ubuntu VM.
Follow these instructions to enable HFS+ read write in the Ubuntu virual image.
Another way to do it would be to use something like Arsenal Image mounter which supports direct mounting of a bunch of virtual image formats including VDI, VHD etc.
I am trying to run mapr sandbox on a windows pc and with 8gb ram. But when I am trying to import the ovf its always saying ovf is corrupt while I have used multiple sources the ovf that is running on the other machine is not running in my one.I have tried to play with the configuration as well I also tried to extract and run the ovf as a vmdk but than there will be no config setup done for so that doesn't works as well. Now I have tried that on vmplayer it got install and said that the ovf format is unsupproted and when you try again it will not see the ovf file specification concern so it imported the file successfully but now its says that the vmx file is incompatible. I cannot find any way out?
I did the following for install it on Ubuntu 14.04 (being virtual machines the final destination, shouldn't be mayor problems):
On VirtualBox
Don't use the ovf file.
Create virtual machine (Machine -> New...)
On operating system, choose red hat 64 bits
On memory, you should asing 8 GB for the VM (or less, if you have an old computer like me :D)
Don't add virtual drives, you can't add both drives. Use the option "Do not add a Virtual Hard Drive"
After creation of the VM
Add both disks to the virtual machine, from settings
Configure the network of the machine as following
Attached to "Bridget Adapter"
Name: Eht0
Adapter Type: Intel PRO/1000 MT Desktop
Promiscuos mode: Deny
Cable Connected: yes
After this small steps, you should be capable of doing right click -> start, and start using MapR. Basically, we import the machine in a very complicated way, because the ovf file that is supposed to use for importing doesn't work!!
I was facing same issue on my Windows & machine. Here is what I did:
Again downloaded MapR sandbox for VMWare for windows.
Uninstalled previous version of VMWare which was giving this issue and downloaded VMWare Workstation Player for Windows 64 bit.
This time it worked.
As I had the chance to experiment with MapR recently-
MapR needs 6GB RAM
at least for the Virtual Box
(or the virtual machine you are using on windows)
if you don't grant the MapR these 6gb it is just not starting with some strange error saying nothing about that issue. You have 8gb ram on your windows machine so I recommend you to spend at least 6.2gb ram for the process.
p.s. Later I had other problems with the mapper as you can see with no support. (previous I found 1 more bug that they say will be fixed in MapR 6)
I am currently using MapR 5.2
Not sure why it was so challenging to bring up Cloudera CDH 5.5 on VirtualBox 5.0.14 on my Windows 7 workstation (64-bit). My desktop is a Lenovo 30AGS01Y00 w/ 1 Intel64 CPU, 16GB RAM, and 1TB of HDD. The detail OS version: 6.1.7601 Service Pack 1 Build 7601.
After installing VirtualBox and unzip Cloudera QuickStart VM 5.5, I created my VM with Red Hat (64-bit), Memory Size: 8,192MB and the "Use an existing virtual hard disk file" option to point to the vmdk file of the Cloudera quickstart for virtual box file. After the VM was created I adjusted its settings, as recommended, such as "Shared Clipboard", "DragnDrop", "Boot Order" (leave Hard Disk only).
The chipset setting was PIIX3 by default. It made no difference when I tried both PIIX3 and ICH9.
I left Processor as 1 CPU because my desktop has only 1 physical CPU even though its VT-x and physical HyperThreading were enabled. Nested Paging was also enabled.
The Storage of the Cloudera VM was created with SATA and Type: AHCI. The rest of settings remained no change (as default).
When I tried to boot the VM my VM screen looked exactly the same as depicted in this question:
Virtual machine "Cloudera quick start" not booting
I've been Googling this issues for about a week. The above question is the closest case I could find on the web. I tried a variety of VM settings but no luck. Not sure what the root cause is.
I tried to fall back to Cloudera QuickStart VM 5.4.2. No luck either.
Looks like zip file cannot be attached. Some key elements in VBox and VboxHardening logs were excerpted as follows:
Vbox.log
00:00:02.535619 VMSetError: F:\tinderbox\win-5.0\src\VBox\Storage\VD.cpp(6410) int __cdecl VDOpen(struct VBOXHDD *,const char *,const char *,unsigned int,struct VDINTERFACE *); rc=VERR_NOT_SUPPORTED
Note: I don't know what F: drive is. There is no F: drive on my desktop.
00:00:02.520998 AIOMgr: Endpoint for file 'C:\CDH_5.4.2\cloudera-quickstart-vm-5.4.2-0-virtualbox-disk1.vmdk' (flags 000c0781) created successfully
00:00:02.535626 VMSetError: VD: error VERR_NOT_SUPPORTED opening image file 'C:\CDH_5.4.2\cloudera-quickstart-vm-5.4.2-0-virtualbox-disk1.vmdk'
00:00:02.567924 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
VBoxHardening.log:
62a4.318: NtOpenDirectoryObject failed on \Driver: 0xc0000022
This may not make a difference, but have you tried importing the .ovf file (not the .vmdk one)?
Also, for future reference, there is much Cloudera VM knowledge here: https://community.cloudera.com/t5/Apache-Hadoop-Concepts-and/bd-p/ApacheHadoopConcepts
I still can't get the "Use an existing virtual hard disk file" part to work.
But, "Import Appliance" via .ovf does bring up the CDH VM. Here is what I do in case if anyone hit the same issue as me.
To import the QuickStart VM (.ovf or .ova):
Select File and then "Import Appliance (Ctrl I) " in VirtualBox.
Browse to find your .ovf (or .ova) and click Next
You may leave everything default and click Import.
Via this "Import Appliance" method, I was able to bring up QuickStart 5.4.2 and 5.5.0, on VirtualBox 5.0.14 on my Windows 7 desktop. It took about 4-5 minutes to finish the boot up process.
I just bought a Macbook Air and installed Oracle VirtualBox on it. I have a Lenovo laptop with Windows 7 on it that I took a system image of it (Control Panel -> Backup and Restore -> Create a system image) on an external hard drive. I would like to have this system image on the VirtualBox, but I'm having trouble. On the external harddrive there seems to be two different VHD files (one is 4.4 mb and one is 50.3 gb in size). I do not see an ISO file on the external harddrive. When I created the new virtual machine and selected the 50.3gb vhd file as the virtual hard disk, I received the "Fatal boot: Int 18" error. Does anyone have any suggestions or ideas how I can get this to work? Thanks in advance!
The Windows 7 backup image is not intended to be bootable by all accounts. You will need to restore the image. Acronis appears to be able to restore the image to a partition, if you dont want to write 50 Gb to DVDs.
the backup VHDs are not bootable in the form they are created with
Windows backup.
Reference