Hypervisor proposed to use one core for RTOS and each other core for an operating system using kernels.

This concept is obsolete because it(TenAsys RTOS) is for embedded system of limited resources. Wasting one core without much usage of hardware.

The new RTOS concept has to go by the components already in the PC architecture, mouse, keyboard, printer, hdd, video monitor and sound equipment. Most of them are on bridges; therefore does not need more than one RT hard thread per bridge of many soft threads.

So, with TenAsys RTOS for Intel official hypervisor, the efficiency is terrible.

Instead, most RTOS will use the internal components on a few hard threads. the rest of typically 12 threads will be used for intranet and Internet surfing or RT application programs using data base that needs synchronization across the network. That means you don't waste one core just for RTOS. Each core will handle RTOS and other kernel driven operating systems(OsX, Unix, Linux or Windows) as well as even robotic programming in Connected Digital Factory.

Footnote:
RTOS uses simple packets, when used in netware becomes Ethernet packets, and when used in browser, RTOS packet becomes dotnet packet. So, simple packet conversion is done in the respective applications. RTOS merely deliver the macros that drive the applications.