Member since
12-22-2015
3
Posts
3
Kudos Received
0
Solutions
12-22-2015
08:23 AM
Many thanks Sean. (I posted much the same thing as I found a clue on another thread but my post crossed with yours.)
... View more
12-22-2015
08:22 AM
1 Kudo
Update: solved this one myself. Instead of doing what I did, I should have invoked File -> Import Appliance and selected the OVF file. That approach works much better 🙂
... View more
12-22-2015
07:48 AM
2 Kudos
Hi all I am trying both CDH and VirtualBox for the first time so apologies in advance if this is a basic error. My configuration is as follows: CDH 5.5 QuickStart VM VirtualBox 5.0.12 OS X 10.11.2 MacBook Pro (Retina, 13-inch, Early 2015) Memory: 8 GB I have successfully installed VirtualBox and downloaded the QuickStart VM. When creating a new VM for CDH 5.5, I use the following options in VirtualBox: Type: Linux Version: Other Linux (64-bit) Memory: 4096 MB (I am aware that I ought to use more but I lack memory on my laptop and don't believe that this is the cause of my problem) Hard disk: "Use an existing virtual hard disk file" (I select the downloaded cloudera-quickstart-vm-5.5.0-0-virtualbox-disk1.vmdk file) Then, when I try to start the VM, I see a large number of read-only filesystem errors and most services fail to start, e.g. touch: cannot touch '/var/lock/subsys/atd': Read-only file system A few services do start, e.g. Impala Server (impalad). All of the filesystem errors appear to refer to the /var filesystem. As per the instructions at http://www.cloudera.com/content/www/en-us/downloads/quickstart_vms/5-5.html, I have tried the following but with no effect: "Some users have reported problems running CentOS 6.4 in VirtualBox. If a kernel panic occurs while the VirtualBox VM is booting, you can try working around this problem by opening the Settings > System > Motherboard tab, and selecting ICH9 instead of PIIX3 for the chip set. If you have not already done so, you must also enable I/O APIC on the same tab." That's not surprising since my issue is the /var read-only filesystem, not a kernel panic. Thanks in advance for any advice. Kevin
... View more
Labels: