Memory in VirtualBox

Comments

8 comments

  • Forrest Smith

    did you take the installer image (the .bin from https://neverware.com/free-download ) and use that for your VM? If so - the OS thinks its an installer and won't expand storage to fill the space you give it,.

     

    You would want to create a 16 GB virtual storage device and then have the VM boot from a mounted virtual device imaged with the .bin image and run the installer.

     

    Otherwise - what VM are you using?

     

     

    0
    Comment actions Permalink
  • Wolfgang K. Meister

    Host is Windows 7 x64 with VirtualBox (latest) 8GB RAM

    I tried the following versions:

    a.) converted the bin to a vdi for VirtualBox. After start it complains about low memory.

    b.) created an USB stick with the .bin file and Chrome tool.

    Set up a VirtualBox machine with a dynamic .vdi, mounted the USB with

    an .vmd file, booted from VirtualBox machine from USB, clicked on the lower right corner to install. Proceeded to e.)

    c.) converted the bin to a vdi for VirtualBox. Created a dynamic .vdi drive

    and attached the converted .bin -> .vdi as the Primary Master and the dynamic .vdi as a Primary Slave. Proceeded to e.)

    e.) Using either methode b.) or c.) by clicking lower right corner and continued to 'Install', the installation screen hangs for ever. Interresting, it says, it will erase 'the HD', but it does not say which one etc. The blue bubbles are shown, but there is no write or read into the .vdi. At least one can not see the blinking red/green in the VirtualBox info in the lower border.

     

     

    0
    Comment actions Permalink
  • Forrest Smith

    Hey,

     

    If you can copy the file

    /var/log/cloudready-install.log 

    and post it's contents here, it should give us some info.

     

    Easiest way to do this:

    1. in browser, input URL of file:///var/log/
    2. Find the file "cloudready-install.log" and right click
    3. Choose "save as" 
    4. rename to "cloudready-install.txt" and change the file type from "LOG file" to "All file types"
    5. Save it
    6. From Downloads folder, open it and copy past contents here (preferably formatted as code) 
    0
    Comment actions Permalink
  • Wolfgang K. Meister

    Thanks for the advice.

    As I said - I did not start CloudReady, I tried to install it either way, b.) or c.) described in my previous message. And it hangs for ever in the install, without writing to the virtual second HD.(?).

    The only way to terminate is to completey power down the VirtualMachine.

    Reached never an installed machine, so how could I access the browser or the log ?

    with best regards

    Wolfgang

    0
    Comment actions Permalink
  • Forrest Smith

    The Home edition allows live boot behavior, so if you're able to trigger the install via the GUI, you can instead just set up the network connection and log in

    0
    Comment actions Permalink
  • Wolfgang K. Meister

    @Forrest Smith

    Looks like, we having complete different experiences.

    Had to power down the VirtualMachine, logged in at the original image, memory warning came up again and I found the cloudready-install.log

    Here is a copy of it:

    INFO:root:found 2 disks
    INFO:root:filtering out root disk, 1 remaining
    INFO:root:filtering out disks smaller than 6442450944, 1 remaining
    INFO:root:best disk: Disk(device_path='/dev/sdb', is_installer=False, is_removable=False, is_root=False, size_in_bytes=11689394176)
    INFO:root:Running from installer; installing to /dev/sdb
    INFO:root:Checking if EFI is enabled
    INFO:root:EFI enabled: True
    INFO:root:running /usr/sbin/parted --script /dev/sdb mklabel gpt
    DEBUG:root:output: 
    INFO:root:running /usr/sbin/chromeos-install --dst /dev/sdb --yes --skip_dst_removable --target_bios efi
    ERROR:root:Error calling ['/usr/sbin/chromeos-install', '--dst', '/dev/sdb', '--yes', '--skip_dst_removable', '--target_bios', 'efi']
    output: Error: Source does not look like a removable device: /dev/sda
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 65, in run_cmd
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib64/python2.7/subprocess.py", line 573, in check_output
        raise CalledProcessError(retcode, cmd, output=output)
    CalledProcessError: Command '['/usr/sbin/chromeos-install', '--dst', '/dev/sdb', '--yes', '--skip_dst_removable', '--target_bios', 'efi']' returned non-zero exit status 1
    INFO:root:No existing CloudReady install could be found on this machine
    ERROR:root:subprocess error
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 248, in main
        install(dest, args.dualboot)
      File "/opt/neverware/auto_install.py", line 198, in install
        run_chromeos_install(dest, is_efi, dualboot)
      File "/opt/neverware/auto_install.py", line 124, in run_chromeos_install
        output = run_cmd(cmd)
      File "/opt/neverware/auto_install.py", line 65, in run_cmd
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib64/python2.7/subprocess.py", line 573, in check_output
        raise CalledProcessError(retcode, cmd, output=output)
    CalledProcessError: Command '['/usr/sbin/chromeos-install', '--dst', '/dev/sdb', '--yes', '--skip_dst_removable', '--target_bios', 'efi']' returned non-zero exit status 1
    INFO:root:found 2 disks
    INFO:root:filtering out root disk, 1 remaining
    INFO:root:filtering out disks smaller than 6442450944, 1 remaining
    INFO:root:best disk: Disk(device_path='/dev/sdb', is_installer=False, is_removable=False, is_root=False, size_in_bytes=11689394176)
    INFO:root:Running from installer; installing to /dev/sdb
    INFO:root:Checking if EFI is enabled
    INFO:root:EFI enabled: True
    INFO:root:running /usr/sbin/parted --script /dev/sdb mklabel gpt
    DEBUG:root:output: 
    INFO:root:running /usr/sbin/chromeos-install --dst /dev/sdb --yes --skip_dst_removable --target_bios efi
    ERROR:root:Error calling ['/usr/sbin/chromeos-install', '--dst', '/dev/sdb', '--yes', '--skip_dst_removable', '--target_bios', 'efi']
    output: Error: Source does not look like a removable device: /dev/sda
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 65, in run_cmd
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib64/python2.7/subprocess.py", line 573, in check_output
        raise CalledProcessError(retcode, cmd, output=output)
    CalledProcessError: Command '['/usr/sbin/chromeos-install', '--dst', '/dev/sdb', '--yes', '--skip_dst_removable', '--target_bios', 'efi']' returned non-zero exit status 1
    INFO:root:No existing CloudReady install could be found on this machine
    ERROR:root:subprocess error
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 248, in main
        install(dest, args.dualboot)
      File "/opt/neverware/auto_install.py", line 198, in install
        run_chromeos_install(dest, is_efi, dualboot)
      File "/opt/neverware/auto_install.py", line 124, in run_chromeos_install
        output = run_cmd(cmd)
      File "/opt/neverware/auto_install.py", line 65, in run_cmd
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib64/python2.7/subprocess.py", line 573, in check_output
        raise CalledProcessError(retcode, cmd, output=output)
    CalledProcessError: Command '['/usr/sbin/chromeos-install', '--dst', '/dev/sdb', '--yes', '--skip_dst_removable', '--target_bios', 'efi']' returned non-zero exit status 1

     

     

    0
    Comment actions Permalink
  • Forrest Smith

    Hey Wolfgang,

     

    Sorry for any confusions, but thanks for the logs. Looks like the install sequence is failing because /dev/sda (the installer storage) doesn't identify as removable.

    It should be possible to run install from cmd line and add an exception to avoid that problem:

    Get a cmd line and srun:

    sudo /usr/sbin/chromeos-install --dst /dev/sdb --yes --skip_dst_removable --skip_src_removable --target_bios efi

     

    That should allow install from /dev/sda -> /dev/sdb without worry as to the storage type.

    0
    Comment actions Permalink
  • Wolfgang K. Meister

    @Forrest Smith

     

    YES - that worked ! perfect!

    As a non-Chromeian I had to find out, how to access the command line.

    Google is my friend...

    with best regards from Vienna / Austria

     

    Wolfgang

     

    0
    Comment actions Permalink

Please sign in to leave a comment.