Changes between Version 67 and Version 68 of VmServer


Ignore:
Timestamp:
Mar 27, 2013, 11:20:24 AM (12 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • VmServer

    v67 v68  
    44It has all the BOINC server prerequisites installed, the BOINC software installed and compiled,
    55and user accounts and permissions set up.
    6 It's ready to run ~/boinc-trunk/tools/[MakeProject make_project] and go.
     6It's ready to run ~/boinc-master/tools/[MakeProject make_project] and go.
    77
    88The VM image is for [http://www.virtualbox.org/ VirtualBox], an open-source VM system.
    … …  
    2525  If you want the latest version, run
    2626{{{
    27 $ cd ~/boinc-trunk
    28 $ svn update
    29 $ cd ..
     27$ ~/update_master.sh
    3028$ ~/configure_server.sh
    3129$ ~/make_server.sh
    … …  
    3331
    3432 * The Linux/PHP/MySQL/Apache software on this VM is not necessarily the latest version.
    35   If you want the latest version, use 'apt-get update' and 'apt-get upgrade'.
     33  If you want the latest version, use 'apt-get update' and 'apt-get upgrade'. Please change the mirror locations in ''/etc/apt/sources.list'' before upgrading!
    3634
    3735 * The "sudo" command is available as user "boincadm" and there is an OpenSSH server running by default.
    … …  
    3937=== Network Access === #server-network
    4038
    41 VMware provides two ways to access the network from the VM:
     39!VirtualBox provides two ways to access the network from the VM:
    4240Bridged Ethernet and NAT (Network Address Translation).
    43 These are selected using the pulldown menu below "Ethernet" in the VMware player.
     41These are selected in the configuration section of the !VirtualMachine. Please power down the VM before changing this value.
    4442We recommend that you start with Bridged Ethernet.
    4543
    46 The first time you boot the VM, log on as root and, if present, delete the file
     44If you somehow change the MAC address of the VM (e.g. cloning the VM) you also have to edit the file `/etc/udev/rules.d/70-persistent-net.rules` after first startup of the VM. The file should look like this:
    4745{{{
    48 /etc/udev/rules.d/z25_persistent-net.rules
     46$ cat /etc/udev/rules.d/70-persistent-net.rules
     47 
     48# This file was automatically generated by the /lib/udev/write_net_rules
     49# program, run by the persistent-net-generator.rules rules file.
     50#
     51# You can modify it, as long as you keep each rule on a single
     52# line, and change only the value of the NAME= key.
     53 
     54# PCI device 0x8086:0x100e (e1000)
     55SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:bc:85:01", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
     56 
     57# PCI device 0x8086:0x100e (e1000)
     58SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:bc:85:02", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
    4959}}}
     60delete the line that ends with `NAME="eth0"` and rename `eth1` to `eth0`. Use the command:
     61{{{
     62$ sudo nano /etc/udev/rules.d/70-persistent-net.rules
     63}}}
     64restart the VM after this.
    5065
    5166General info about network configuration under Debian is in the
    … …  
    8297You should also add the IP address and hostname of the VM to your hosts file. To do this edit {{{C:\Windows\system32\drivers\etc\hosts}}} (if the host is Windows) or {{{/etc/hosts}}} (as root; if the host is Unix) with an editor, and add for example:
    8398{{{
    84 141.142.234.9 debian.localdomain
     99141.142.234.9 debian6.localdomain
    85100}}}
    86101
    87102With this you can connect a client from your host machine to your VM.
    88 If you're using a proxy to access the internet you should add 'debian.localdomain' to your list of exceptions in your browser.
     103If you're using a proxy to access the internet you should add 'debian6.localdomain' to your list of exceptions in your browser.
    89104You won't need a proxy to resolve a local address.
    90105
    … …  
    98113issue IP address to new hosts.
    99114
    100 At this point, for the network changes to take effect, you may want to restart the Linux instance:
     115At this point, for the network changes to take effect, you may want to restart the Linux VM:
    101116{{{
    102 shutdown -rF now
     117$ sudo reboot
    103118}}}
    104 
    105 If you're running the VM on Windows and networking stops working,
    106 try the following.
    107 In a Windows command window:
    108 {{{
    109 net stop vmnetbridge
    110 net start vmnetbridge
    111 }}}
    112 Then restart the VM's network as well, with:
    113 {{{
    114 sudo ifconfig eth0 down
    115 sudo ifconfig eth0 up
    116 }}}
    117 If that still doesn't work, reboot your machine and try the same process again.
    118119
    119120=== NAT ===
    … …  
    125126so this mode is not recommended.
    126127
    127 However, this limitation can be circumvented using port forwarding
    128 (not available with the free VMware player).
    129 To do this, use the VMware virtual network editor (Edit > Virtual Network Settings > NAT > Edit > Port Forwarding).
    130 More information in [http://www.vmware.com/support/ws5/doc/ws_net.html Configuring a Virtual Network].
    131 On Windows, if NAT is to be used and not already set,
    132 do the following to get network access in the VM:
    133 {{{
    134 Start | Programs | VMware | VMware Server | Manage Virtual Networks
    135 (Virtual Network Editor):
    136 Host Virtual Network Mapping:
    137 VMnet0: Bridged to an automatically chosen adapter.
    138 VMnet8: VMware Network Adapter VMnet8
    139 In the NAT tab: VMnet host: VMnet8
    140 }}}
     128However, this limitation can be circumvented using port forwarding.
     129To do this, use the !VirtualBox Manager (Edit > Network), change the ''Attached to:'' option to NAT, click on ''Advanced'' then ''Port Forwarding''.
     130More information in [http://www.virtualbox.org/manual/ch06.html#natforward Configuring port forwarding with NAT].
     131