Free vm software for linux

NanoVM is a tiny (less than 8 kB of code including simple native classes and a bootloader) implementation of the Java VM. NanoVM project currently runs on Linux and the AVR microcontroller family.
Unix/Linux is supported as the main development and testing platform, whereas the VM is primarily intended to be used on tiny embedded devices such as the AVR. The VM can very easily be ported for other targets.
Main features:
- Support for standard java bytecode
- Tested on AVR Mega8 and Mega32
- Complete 15 bit integer arithmetic
- Garbage collection
- Bootloader for simple application upload
- Tested with Suns JDK and IBMs jikes
- Supports inheritance
- Unified stack and heap architecture
- Requires less than 8kBytes of code memory
- 512 Bytes code storage for java byte code (the complete 512 eeprom bytes available on the AVR ATmega8 CPU)
- 768 Bytes application RAM available (of 1k total RAM available on the AVR ATmega8 CPU)
- About 20k Java opcodes per second on 8 Mhz AVR
- Native classes include:
- java/lang/Object (object handling)
- java/lang/System (IO handling)
- java/io/PrintStream (console output)
- java/lang/StringBuffer (string processing)
- asuro (asuro control)
Enhancements:
- Nibo robot support
- Asuro ATmega168 support
- Virtual machine source folder cleanup
- New html class documentation (javadoc)
- updated install_avr_gcc script to install gcc-4.1.2, GDB=gdb-6.6, avr-libc-1.4.6 and avrdude-5.4

Ovm is a tool for generating virtual machines. Ovm includes a variety of compilers, garbage collectors, and threading systems that can be used to create a free-standing VM.
This VM can (and currently must) be specialized to a particular application. Ovm is currently able generate virtual machines for ordinary Java programs, and programs written to the Real-time Specification for Java.
Main features:
- dynamic loading - Like many ahead-of-time compilers for real-time/embedded systems, the Ovm does not support dynamic loading of classes. In the future we expect to support this via some form of mixed-mode operation and/or using the JIT compiler.
- weak references and finalization - There is no support for weak references and heap finalizers are never run. Finalizers for objects allocated in RTSJ scoped memory are run.
- Non-core JDK APIs that rely on native code - Ovm does not support the AWT and other APIs that are non-core. Ovm depends on GNU Classpath for all of the JDK APIs, but must provide its own special code to replace all native calls.
- JNI support - Ovm does not support JNI and it is not planned at the present. Much native code is replaced in Ovm by Java code operating in what we term the "executive domain". There are ways to provide additional native code support but there are highly specialized and not intended for general application use.
Code using dynamic loading, native calls or finalizers will need to be adapted to work with Ovm.
The implementation of the real-time APIs is also incomplete - see the package.html file in src/syslib/user/ovm_realtime/javax/realtime for details.
This is a BETA release. Ovm still has known bugs that can lead to unexpected behavior, especially when migrating large applications to Ovm.
Usage
Ovm is regularly tested on Linux/x86, Linux/ppc, and OS X/ppc. The JIT only works on x86. Ovm requires a Sun, IBM, or Apple release of Java 1.4 and gcc 3.x to build. 256 MB of main memory are also required, 1 GB are recommended.
In order to run Java applications under Ovm, it is strongly recommended that you compile the applications against Ovms version of the JDK (which is based on GNU classpath). This is the easiest way to ensure that you do not rely on library functionality that is not available. Instructions on how to compile Java code against the Ovm JDK are in the file TUTORIAL. The TUTORIAL also describes how to run the SPEC JVM and the real-time benchmarks.
Also note that all class files must have been compiled to the format defined by the javac -target 1.1 setting. This restriction will be removed in the future.
At this point in time, Ovm always requires whole-world compilation of the application. Ovm has three execution backends, an interpreter, a JIT and J2C which is a front-end to GCC. Both the interpreter and the JIT are intended to be used in conjunction with dynamic loading in the future. At this stage, building Ovm with these configurations is only useful for development purposes. All benchmarking should always be done with the J2C configuration with gcc-3.4.
Version restrictions:
- The Ovm program (gen-ovm), may very rarely hang after calling out to a subprocess. This appears to be a bug in Linux implemenations of Java 1.4, and occurs more frequently with Blackdown Java distributions than Sun. Ovm attempts to detect and work around the problem, but this code is extremely difficult to test. One simple trick that sometimes unhangs things is to stop the process (use -Z) and then restart it using fg.

SlaBuntuVMware is a useful installation suite for installing VMware Server on Slackware or Ubuntu.

The project automatically downloads packages from the VMware site.

Tested on Slackware 11. (Slackware 10.2 might not work - try)
Tested on Ubuntu Desktop Dapper Drake and Ubuntu Desktop Edgy.

IMPORTANT: this suite does not include the vmware server packs,
they are downloaded from the official VMware site.
You also need a server key for activating the product that you must
get (for free) from the VMware web-site (http://www.vmware.com/server/)

INSTALLATION (Slackware Linux) :

a) 1- The perfect setup for running vmware on Slackware is:
Slackware 11 (When you install the OS leave a big partion for your
virtual machines).

Using a good server with an hardware raid controller:

Suggested Partition Table (scsi disks, if ide hda):
/dev/sda1 swap (megs?gb? depends on your system)
/dev/sda2 / 10Gb
/dev/sda3 /home 2Gb
/dev/sda4 /vm (160 Gb the rest for your virtual machines)

You must do a normal install with X support but no KDE.


2- Dropline Gnome (http://www.droplinegnome.net)
It is suggested you run gnome on Slackware 11. Gnome is not
included in the distro cds, therefore you must download
Dropline Gnome.

3- Kernel 2.6.x (with the kernel sources into /usr/src/linux)
(Default Kernel 2.4.33.3 works perfectly though)

CAUTION: take a look on www.vmware.com for the
supported kernel 2.6 versions.

OR

- If you have problems building 2.6.x vmware kernel module, just use
the normal 2.4.33.3 kernel supplied with your slackware, or try the test26.s
or huge26.s supplied with your slackware cds.

b) - The base setup for running vmware on Slackware is:
1- Slackware 11
2- Kde(not tested can have problems with some libraries)
(if you do not want to Download and install Dropline Gnome)
3- Kernel 2.4.33 (with the kernel sources into /usr/src/linux)

Using a normal pc with no raid controller (so you should use linux
raid software):

Suggested Partition Table (scsi disks, if ide hda):
/dev/md1 swap (megs?gb? depends on your system)
/dev/md2 / 10Gb
/dev/md3 /home 2Gb
/dev/md4 /vm (100 Gb? the rest for your virtual machines)

---------------------------------------------------------------------------
If you do not want to use Gnome or Kde go at the end of this file.
---------------------------------------------------------------------------

2) After making sure you have everything (including the kernel sources
inside /usr/src/linux) you can run:

3) as root ./setup.sh

4) follow the steps provided
(you can hit ENTER to most of the questions (90%)

4) provide the vmware free key when needed
(ask for it on the site http://www.vmware.com)

6) under an X session: Run the command "vmware" and Enjoy vmware!

INSTALLATION (Ubuntu Desktop, Alternate,NOT Server):

1) edit /etc/apt/sources.list and uncomment all the lines starting with deb

2) open a terminal (xterm) and type "sudo ./setup.sh"

3) follow the steps provided
(you can hit ENTER to most of the questions (90%)

4) provide the vmware free key when needed
(ask for it on the site http://www.vmware.com)

5) Run the command "vmware" and Enjoy vmware!

INSTALLATION ON UBUNTU SERVER

- Not tried yet, but you should at first download and install X11 and gnome
and then follow the steps provided for Ubuntu Desktop above.

IMPORTANT INFO:

- Remember that vmware server packs are downloaded from the official vmware
site and are property of the VMware Company: http://www.vmware.com/

- Remember that in order to use VMware you should accept the terms of the
VMware license that will be displayed during the installation process.

- Remember that in order to installa VMware you should ask the VMware
fellows for a key. Do this at the VMware site: http://www.vmware.com/

- To create virtual machines you should use the vmware console.
a) Run the command "vmware" and the vmware console starts up.
b) Then connect to localhost.

- After created a virtual machine to run it from the cmd line use:
bash# vmware-cmd vmname.vmx start

Author: Lorenzo Allori

#####################################################

If you do not have Gnome or Kde youll need the following:

#####################################################

- Slack with glibc and glibcsolibs installed. Make sure you
have X11 installed with a window manager.

Packages needed are:
glibc-2.3.6-i486-6.tgz
glibc-solibs-2.3.6-i486-6.tgz
kernel-source-2.4.33.3-noarch-1.tgz
x11-6.9.0-i486-11.tgz
x11-devel-6.9.0-i486-11.tgz
windowmaker-0.92.0-i486-1.tgz

You can find those on http://www.slackware.com.

Download them and to install those just type (as root):

# installpkg pkgname

When you have finished installing all the packages you need remember to run:

# ldconfig

- If you need a window manager you can install windowmaker:

# installpkg windowmaker-0.92-i486.tgz
# wmaker.inst

Convert::IBM390 is a Perl module functions for manipulating mainframe data.

SYNOPSIS

use Convert::IBM390 qw(...those desired... or :all);

$eb = asc2eb($string);
$asc = eb2asc($string);
$asc = eb2ascp($string);

$ebrecord = packeb($template, LIST...);
@fields = unpackeb($template, $record);
@lines = hexdump($string [,startaddr [,charset]]);

Convert::IBM390 supplies various functions that you may find useful when messing with IBM System/3[679]0 data. No functions are exported automatically; you must ask for the ones you want. "use ... qw(:all)" exports all functions.

By the way, this module is called "IBM390" because it will deal with data from any mainframe operating system. Nothing about it is specific to z/OS, z/VM, or z/VSE.

UMLMON is a complete run time environment for User Mode Linux. There is a separate monitor daemon for every VM.
UMLMON project creates the run time environment and starts the VM by executing the UML kernel. The daemon also determines the arguments that are passed to the UML kernel, and includes special support to set up arguments for memory size, virtual disks, virtual network interfaces, and console channels in a convenient way.
UMLMON also includes routines to do certain administration tasks like the creation of disks.
The team UMLMON + UML can be applied in the following areas:
- Server consolidation: Improve the utilization of server hardware, and ease the operation of servers.
- Virtual security zones: Instead of building demilitarized zones (DMZ) with real hardware, it is a cost-effective alternative to set up purely virtual DMZs on a single host.
- Virtual hosting: A cheap version of server hosting is virtual hosting; instead of leasing real computers to customers, virtual machines are used.
- Laboratory nets: By using virtual machines it is possible to build cheap laboratory nets, e.g. to test software in real network environments.
- Training environments: One can use virtual machines for Linux trainings where participants can get true administrators priviledges without any risks.
Enhancements:
- This release no longer call the problematic glibc function getgrouplist, which is often broken (symptom: segmentation fault immediately after starting umlmon).

Qemudo is a Web interface to QEMU offering a way for users to access and control multiple virtual machines (guest systems) running on one or more remote physical machines (host systems).
From the Web interface, VMs can be created, started up, shut down, reset, and accessed (monitor, keyboard and mouse). Access to the VMs is done through a VNC applet making use of the VNC protocol natively supported by QEMU 0.8.1 and later.
Qemudo has been primarily designed to function in a cluster environment, where its Web interface gives a unified view on all the VMs running on a cluster of physical machines. Of course it can also be used just as easily to manage only a couple of VMs running locally.
Known Issues
A core component of Qemudo, qsh, crashes with the error message send: Cannot determine peer address due to a Perl bug that manifests itself only on certain platforms such as OpenBSD. See Perl bug 41521. Perl 5.8.9 (yet to be released) will apparently include a patch for this bug.
Enhancements:
- Support was added for the new -vnc option syntax in QEMU 0.9.0.
- A qemudorc shell script that launches QEMU is created by qd for every VM that is started up.
- This gives users the possibility to manually edit this file to tweak the options passed to QEMU.
- A Perl bug has been fixed in qsh: sockname() was replaced with hostpath().
- Installation documentation has been improved.

Java::SJ is a highly configurable Java program startup system.

SYNOPSIS

sj myprogram.sj

This module allows you to very easily run Java services that rely on complex configuration at the VM and library level. It also provides an easy way of specifying a sensible default configuration that can be overridden by specific applications should they need to.

The system is configured on a machine and application level. The system looks for configuration files in a set of well-known locations, currently these are:

/etc/sj.conf
.sj.conf in users HOME directory
.sj.conf in current working directory

Every application is defined in terms of a similar configuration file. The configuration system has been designed so that it is easy to write a simple and minimal configuration file for a program.
Provided the system has a fairly complete configuration associated with it then an application configuration file need only have the class name to be executed.