This also implies that the box running LiquidVM (and the lower-lever hypervisor) can run no other applications besides the one running in the JVM. This may actually be desirable for embedded systems and appliances, where simplicity and raw performance are important qualities.
Take a look at Oracle-BEA's description of LiquidVM:
LiquidVM provides the following features:
JRockit JVM as the Java runtime component.
Java run-time class libraries.
A scaled-down OS kernel that replaces the OS for LiquidVM. It differs from a normal OS in that it is a single-user, single-process environment that is designed to only run a single JVM. No other processes can be started. It implements the following services that the JRockit JVM needs to run Java:
Low-level memory management
Interaction with the hypervisor
Java-based services, started after the JRockit JVM has started, that run in threads that are separate from your application. The LiquidVM services are:
LiquidVM syslog publisher
Tools that are used to create and control LiquidVM instances. The LiquidVM tools run on a standard OS; they do not run inside LiquidVM. LiquidVM tools include:
LiquidVM launcher—used to start and stop LiquidVM instances
LiquidVM Configuration Wizard—used to configure the connection between LiquidVM and the VMware VirtualCenter
A virtual local disk for each WLS-VE instance. The local disk removes the dependence on NFS and provides faster and more secure file transfers
Building A Mobile Business MindsetAmong 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps – and it's past time for those with no plans to get cracking.