{"id":353,"date":"2010-07-20T22:05:08","date_gmt":"2010-07-21T03:05:08","guid":{"rendered":"http:\/\/otac.isa-geek.net\/blog\/?p=353"},"modified":"2010-07-20T22:05:08","modified_gmt":"2010-07-21T03:05:08","slug":"more-os-fun-with-virtualbox-chrome-os","status":"publish","type":"post","link":"https:\/\/otac.isa-geek.net\/blog\/?p=353","title":{"rendered":"More OS fun with VirtualBox – Chrome OS!"},"content":{"rendered":"

I recently saw a demo of Google Chrome OS<\/a> online, and I must admit it intrigued me, both with the uniqueness of the vision behind it, and the underlying technology. So I decided to take a quick look at this beastie in the lab, and of course, there is no better way to study a captive OS than with VirtualBox<\/a>!<\/p>\n

The first step was to locate a download source for the Chrome OS VMWare virtual machine, previously distributed by Google (November, 2009). I found a copy here<\/a>, but searching online will probably turn up others.<\/p>\n

Next, I started up the VirtualBox 3.1 GUI, and chose to create a new virtual machine, using the New Machine wizard. I specified the type as other and unknown, since that will give the greatest flexibility in the setup wizard selection. I set the memory for the VM as 512 MB to simulate the more constrained resources that Google Chrome OS is expected to operate under. For the disk, I chose to use Existing Disk (and checked Boot Hard Disk), then chose the previously saved ChromeOS virtual machine appliance definition as the image to use.<\/p>\n\n\n\n\n\n
\"Sun<\/a><\/p>\n

VirtualBox-Chrome<\/p>\n<\/td>\n

\n

\n

\n

\n

\n

\n

\"VirtualBox-ChromeOS<\/a>

VirtualBox-ChromeOS Definition<\/p><\/div><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Finally, I confirmed the settings, then started the new Chrome OS VirtualBox appliance. On boot up (which is fast!), the main screen prompts for your Google account details, after which the default email page starts up.<\/p>\n\n\n\n
\n\n\n
\n
\n
\"ChromeOS<\/a><\/dt>\n
ChromeOS default startup<\/dd>\n<\/dl>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

As can be seen, the UI looks essentially like Google Chrome, however, the default application page allows the execution of predefined apps, as well as adding new ones (currently disabled in the beta).<\/p>\n\n\n\n
\n
\n
\n
\"ChromeOS<\/a><\/dt>\n
ChromeOS applications<\/dd>\n<\/dl>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Clicking on the icons at the right-top of the page, will show the status of the system, as well as allow the changing of current network settings.<\/p>\n\n\n\n
\n\n\n
\n
\n
\"ChromeOS<\/a><\/dt>\n
ChromeOS calendar<\/dd>\n<\/dl>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

As a beta, there is not a lot of functionality now available, however, I did notice that the system state was saved once it is powered down, and resumed at next signin. This was an interesting exploration of Google’s OS design decisions, and I’m looking forward to seeing their next release and what it can do!
\n References<\/strong><\/p>\n

Download the Google Chrome OS Virtual Machine<\/a><\/p><\/blockquote>\n