wiki:VmServer

Version 7 (modified by Christian Beer, 17 years ago) (diff)

added information about NAT and Bridged networking with VMware

Linux Virtual Machines for use with BOINC

These files are big (1 GB or so). Please download them as seldom as possible.

On all these systems, the root (or sudo) password is 'boincadm'. There is a user account 'boincadm' with password 'boincadm'; build software under this account. Change these passwords if you're concerned about security.

Virtual server

BOINC Virtual Server. Use this to create BOINC projects. It's a VMWare virtual machine; you'll need the VMWare player. It's a Debian 4.0 32-bit system with all the BOINC prerequisites installed, the BOINC software (not the latest version) installed and compiled. It's ready to run make_project and go.

If you want the latest BOINC software, run update_latest.sh and then configure/make. Instructions and more information is in the readme.html file on boincadm's desktop.

The passwords can be found in the file 'README-vmware-image' that is part of the zip file.

Network Access

You can either use NAT (Network Address Translation) or Bridged Ethernet to get network access from within the VM:

NAT
means that you share the IP address of the host machine in order to make outgoing connections (access internet sites from within your VM). Incoming connections from other machines (except the host machine) are not possible. Scanning the network will only reveal one machine, your host.
Bridget
means that the VM will act like a real machine within your network. It tries to get an IP over DHCP within the same range like your host machine. Outgoing and Incoming connections are possible. Scanning the network will reveal two machines, your host and the VM.

On Windows, you may need to do the following to get network access in the VM:

Start | Programs | VMware | VMware Server | Manage Virtual Networks
(Virtual Network Editor):
Host Virtual Network Mapping:
VMnet0: Bridged to an automatically chosen adapter.
VMnet8: VMware Network Adapter VMnet8
In the NAT tab: VMnet host: VMnet8

You should also add the IP address and hostname of the VM to your windows hosts file. To do this edit c:\windows\system32\drivers\etc\hosts with an editor and add for example:

192.168.190.128 debian.localdomain

With this you can connect a client from your host machine to your VM.

Virtual machines for building and testing apps

NOTE: THE FOLLOWING VIRTUAL MACHINES ARE TEMPORARILY UNAVAILABLE

These are based on Microsoft Virtual PC. (VMWare can reportedly also run these files, though we haven't tried it).