Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Channels ▼

Community Voices

Dr. Dobb's Bloggers

Wind River; Welcome to the Party

June 18, 2009

Wind River (Finally) Releases Virtualization Platform; Welcome to the Party

This week Wind River announced availability of its long-anticipated hypervisor for embedded systems.  Originally announced in June of 2008, Alameda finally appears to have a product ready to ship to OEMs.
Structurally, the introduction makes sense.  The company needs some way of reconciling the attributes of their many and divergent embedded platforms. A hypervisor provides a potential home for any or all of them – in one neat package.  At the very least the Wind hypervisor provides a place to sell and install VxWorks, as a way to salvage RTOS revenues.
The announcement and the materials supporting it primarily tout multicore applications. However, Alameda is keenly interested in all things mobile: they are members of LiMo and OHA and participate in Moblin.  Moreover, the mobile focus of Atom silicon from their new parent company, Intel, signals that mobile virtualization is likely in their sights as well.

Caveat Emptor – Mobile OEMs Beware

Technology stands on its own merits, but to make business sense, successful technology needs the right supplier behind it.  It’s too early and the Wind virtualization product is likely too immature to make definitive claims about its functionality or reliability.  However, it’s worth considering how the source for this technology impacts its position in the mobile marketplace.
Double Lock-In
The Wind River embedded hypervisor locks OEMs into a single proprietary solution in both the short- and long-term. 
Read Full Blog Post Here

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.