[ANNOUNCE] [OFFTOPIC] Xvisor ARM with and/or without virtualization extensions

GoogleGroups
1

Xvisor (eXtensible Versatile hypervISOR) is an open source bare-metal
monolithic hypervisor, which aims towards providing virtualization solution,
which is light-weight, portable, and flexible with small memory foot print
and less overhead. It is distributed under GNU Public License (GPLv2).

Xvisor has most of the features expected from a modern full-fledged hypervisor,
such as:
- Tree based configuration
- Tickless and high resolution timekeeping
- Wall-clock for tracking real-time
- Threading framework
- Host device driver framework
- CPU virtualization
- Address space virtualization
- IO device emulation framework
- Pass through hardware access
- Dynamic guest creation/destruction
- Serial port virtualization
- Management terminal

The ARM port of Xvisor (or Xvisor ARM) supports a wide range of ARM processors
namely:
- ARM9 (Boards: VersatilePB)
- Cortex-A8 (Boards: Realview-PB-A8)
- OMAP3 (Boards: BeagleBoard-xM)
- Cortex-A9 (UP) (Boards: Vexpress-A9)
- Cortex-A15 (UP) Without VE (Boards: Vexpress-A15)
- Cortex-A15 (UP) With VE (Boards: Vexpress-A15)

For all supported ARM processors Xvisor ARM is able to boot multiple unmodified
Linux-3.0.4 guest with a fairly interactive and smooth Busybox 0.19.2 console.

On real hardware specifically BeagleBoard-xM (OMAP3 @ 600 MHz) we get near
native CPU performance (i.e. Native Linux 3.0.4 gives 1120 DMIPS whereas Linux
3.0.4 running as guest on Xvisor ARM gives 960 DMIPS)

Please try out our Xivsor Cortex-A15 demo on ARM Fast Models 7.0 and/or
Linaro QEMU (2.02 or higher). To download the demo tarball visit:
https://docs.google.com/open?id=0B0ABS_s60oP_WjNQQ0QtUzNmdmc

Xvisor is currently hosted on Github, to clone or download source code please
visit following links:
Wiki: https://github.com/xvisor/xvisor/wiki
Mainline Repository: https://github.com/xvisor/xvisor
Stagging Repository: https://github.com/avpatel/xvisor-next

Our developer mailing list is xvisor-devel[at]googlegroups[
dot]com, please feel free to post your queries or join our development
mailing list.

2

Hi Alex,

Network Virtualization and Block Device Virtualization are at top most
priority for Xvisor right now. Couple of folks have already started
working on Network virtualization but Block Device Virtualization
still unexplored.

We would be glad to have your contributions. Do join our xvisor-devel
googlegroup.

Thanks & Regards,
Anup Patel

3

Hi, I don’t know how can I run Xvisor that supports Cortex-A15 Without VE.
I just can find manual - How to run Xvisor that supports Cortex-A15 With VE.
Without VE, hypervisor handles sensitive instructions using hypercall.
So I want to know how Xvisor handles sensitive instructions using hypercall and converting sensitive instruction, without trap&emulation.
I want to run Xvisor that supports Cortex-A15 Without VE.

How can I run Xvisor at Cortex-A15 Without VE.

2012년 4월 24일 화요일 오전 6시 36분 34초 UTC-7, Anup Patel 님의 말:

4

Hi,

(Dropping other mailing list to avoid unnecessary noise)

Hi, I don't know how can I run Xvisor that supports Cortex-A15 Without VE.
I just can find manual - How to run Xvisor that supports Cortex-A15 With VE.
Without VE, hypervisor handles sensitive instructions using hypercall.
So I want to know how Xvisor handles sensitive instructions using hypercall
and converting sensitive instruction, without trap&emulation.
I want to run Xvisor that supports Cortex-A15 Without VE.
How can I run Xvisor at Cortex-A15 Without VE.

Sorry for little delay in reply. I missed this email. Please try to post your
Xvisor related queries on xvisor-devel (CCed here) and also join xvisor-devel.

Actually, Cortex-A15 is a processor with virtualization extension hence we
use our ARM32VE port for it. We don't use ARM32 port for Cortex-A15.

Latest Xvisor source can be found at:

To try Linux guest on Xvisor for Cortex-A15, refer:

I hope above helps. Let me know if you have more queries.

Regards,
Anup