Download CloudReady Image for VMware




  • Avatar
    James LaBarre

    Has ANYONE (other than me) brought up the issue of the display incompatibility to the VirtualBox folks? 

    Here is a good case for alternative extension packages.  The er software is designed to handle multiple extension kits, but it seems if it's not part of the Oracle-approved package, it will never be incorporated.  Much like the rest of VBox; if Oracle doesn't want it, it never gets done.

    Although at this point (especially as my day job centers around Openstack) I'll start migrating all my VMs over to KVM/QEMU anyway (I never run VMs on the rare occasions I'm booted to MSWin).  So does this OVA work with KVM?  (it will be a few days before I'm back home and can try it out again).


  • Avatar
    Forrest Smith

    We use qemu/kvm for almost all of our internal VM uses when developing and testing. CloudReady's compatible, but I am unsure whether the OVA file linked here will work there. Please post back here if you try it that and it works.

  • Avatar
    Rommel Rivera

    Thank you for posting the new OVA, Forrest.  I still can't get a higher resolution in VMware WS 14.  No big deal.  Your CloudReady VM is still a great resource to have in lieu of a Chromebook.  Thank you for making this product available to us!

  • Avatar
    Peter Fales

    Ditto here.  I was able to update my 66.3 VM to 66.4, but it still does not allow for any changes in screen resolution.   (VMware Workstation 14 Player)


  • Avatar
    Pedram Khoshdani

    I couldn't also solve the problem with screen resolution, but as an alternative, I am using "Chrome Remote Desktop" App which needs to be installed on both Host's and Guest's Chrome browser.

    Another problem is SSH. I can't find a way to connect to the Chrome OS using SSH. The port is closed and I can't open it. I tried the following command to open it with no success:

    iptables -I INPUT -p tcp --dport 22 -j ACCEPT

    can someone please help me out?

  • Avatar
    Forrest Smith

    Hi Pedram,


    Sorry to hear the display resizing isn't helping - we're not sure exactly what's wrong there, but hopefully it can repaired some time in the future.


    The SSH access situation should be something you can resolve pretty easily on a boot-by-boot basis:

    From a shell, just run:

    sudo start openssh-server

    That will start the service, which is off by default for security reason.


    You'll need run that again each time you need it. Do you want SSH enabled 100% of the time? This is not something we'd recommend for security reasons, but it may be possible to configure.

  • Avatar
    Esteban Quito

    Install and update went fine and fast but cannot change screen resolution.

    FYI: the title of this thread has a huge typo "CoudReady"

  • Avatar
    Pedram Khoshdani

    Hi Forrest,

    thanks for the SSH solution, however, I also managed to start it using the following guide (Note: read the comments underneath it to help you figure out how to do it correctly):

    What is the username and password to connect to the terminal from Putty using SSH?

  • Avatar
    Forrest Smith (Edited )

    Esteban: thanks for the catch. How embarrassing!


    Pedram: the standard user for Chromium OS is "chronos", but there's no password set by default. 

    I'm not sure how this will impact SSH - you may be able to SSH in without issue, but you might find you need to set a password:

  • Avatar
    Pedram Khoshdani

    When I try to use your link to set a password, it says "mount: cannot remount /dev/dm-0 read-write, is write-protected" in response to "sudo mount -o remount,rw /"

    However, I can change the root password using: "sudo chromeos-setdevpasswd", but still no success with SSH.

    With the last version (cloudready-free-64bit-59.3.37) I could connect using SSH using:

    username: chronos

    password: test0000

    but once it is updated using google chrome, I could no longer connect via SSH.

  • Avatar
    Forrest Smith

    Sorry for the confusion - 

    We've updated the file system to be more secure, so before making any changes to the root file system, including that command to remount that failed for you, you need to disable rootFS verification as described here:


    I've updated the password-article to reflect this as well. Thanks for your feedback noticing the missing info.


    The password changed from v59 to be un-set by default as "test0000" is a default password for the Chromium project and not reflective of any actual security measure.

  • Avatar
    Steve Ringley

    When I run the Home OVA with Fusion 10.1.2 I get prompted to upgrade virtual hardware from version 11 to version 14.  Is that doable with these images?

Please sign in to leave a comment.