| 1 | $Id: vboxtxs-readme.txt 68181 2017-07-30 10:15:22Z vboxsync $
|
|---|
| 2 |
|
|---|
| 3 |
|
|---|
| 4 | VirtualBox Test eXecution Service
|
|---|
| 5 | =================================
|
|---|
| 6 |
|
|---|
| 7 | This readme briefly describes how to install the Test eXecution Service (TXS)
|
|---|
| 8 | on the various systems.
|
|---|
| 9 |
|
|---|
| 10 | There are currently two transport options for the TXS:
|
|---|
| 11 |
|
|---|
| 12 | - The default is to use it in TCP server mode, i.e. the test script needs
|
|---|
| 13 | to know the guest's IP and therefore requires guest additions to be
|
|---|
| 14 | installed as well. (Please use the latest stable additions compatible with
|
|---|
| 15 | the VBox host versions you intend to test.)
|
|---|
| 16 |
|
|---|
| 17 | - The alternative is for NATted setups where TXS will act like a TCP client
|
|---|
| 18 | and try connect to the test script on the host. Since this require that
|
|---|
| 19 | TXS knows which IP to connect to, it's only really possible in a NATted
|
|---|
| 20 | setup where we know the host IP is 10.0.2.2.
|
|---|
| 21 |
|
|---|
| 22 | Since r85596 TXS operates in both modes by default so the nat version of
|
|---|
| 23 | the init scripts is not required anymore. Instead the other type can be installed
|
|---|
| 24 | for both cases.
|
|---|
| 25 |
|
|---|
| 26 | Linux Installation
|
|---|
| 27 | ------------------
|
|---|
| 28 |
|
|---|
| 29 | 1. cd /root
|
|---|
| 30 | 2. scp/download VBoxValidationKit*.zip there.
|
|---|
| 31 | 3. unzip VBoxValidationKit*.zip
|
|---|
| 32 | 4. chmod -R u+w,a+x /opt/validationkit/
|
|---|
| 33 | 5. cd /etc/init.d/
|
|---|
| 34 | 6a. init.rc: Link up the right init script (see connection type above):
|
|---|
| 35 | nat) ln -s ../../opt/validationkit/linux/vboxtxs-nat ./vboxtxs
|
|---|
| 36 | other) ln -s ../../opt/validationkit/linux/vboxtxs ./vboxtxs
|
|---|
| 37 | 6b. systemd: Link/copy up the vboxtxs.system to [/usr]/lib/systemd/.
|
|---|
| 38 | 7a. init.rc: Add vboxtxs to runlevels 2, 3, 5 and any other that makes sense
|
|---|
| 39 | on the distro. There is usually some command for doing this...
|
|---|
| 40 | 7b: systemd: Enable the vboxtxs service.
|
|---|
| 41 | 8. Check the cdrom location in vboxtxs and fix it so it's correct, make sure
|
|---|
| 42 | to update in svn as well.
|
|---|
| 43 | 9. reboot / done.
|
|---|
| 44 |
|
|---|
| 45 |
|
|---|
| 46 | OS/2 Installation
|
|---|
| 47 | --------------------
|
|---|
| 48 |
|
|---|
| 49 | 1. Start an "OS/2 Window" ("OS/2 System" -> "Command Prompts")
|
|---|
| 50 | 2. md C:\Apps
|
|---|
| 51 | 3. cd C:\Apps
|
|---|
| 52 | 4. Mount the validationkit iso.
|
|---|
| 53 | 5. copy D:\os2\x86\* C:\Apps
|
|---|
| 54 | 5. copy D:\os2\x86\libc*.dll C:\OS2\DLL\
|
|---|
| 55 | 6. Open C:\startup.cmd in an editor (tedit.exe for instance or e.exe).
|
|---|
| 56 | 7. Add the line "start /C C:\Apps\TestExecService.exe --foreground" at the top of the file.
|
|---|
| 57 | 8. reboot / done
|
|---|
| 58 | 9. Do test.
|
|---|
| 59 |
|
|---|
| 60 |
|
|---|
| 61 | Solaris Installation
|
|---|
| 62 | --------------------
|
|---|
| 63 |
|
|---|
| 64 | 1. Start the guest and open a root console.
|
|---|
| 65 | 2. mkdir -p /opt/VBoxTest
|
|---|
| 66 | 3. cd /opt/VBoxTest
|
|---|
| 67 | 4. scp/download VBoxValidationKit*.zip there.
|
|---|
| 68 | 5. unzip VBoxValidationKit*.zip
|
|---|
| 69 | 6. chmod -R u+w,a+x /opt/VBoxTest/
|
|---|
| 70 | 7. Import the right service setup depending on the Solaris version:
|
|---|
| 71 | <= 10u9) /usr/sbin/svccfg import /opt/VBoxTest/validationkit/solaris/vboxtxs-sol10.xml
|
|---|
| 72 | >= 11.0) /usr/sbin/svccfg import /opt/VBoxTest/validationkit/solaris/vboxtxs.xml
|
|---|
| 73 | 8. /usr/sbin/svcadm enable svc:/system/virtualbox/vboxtxs
|
|---|
| 74 | 9. reboot / done.
|
|---|
| 75 |
|
|---|
| 76 | To remove the service before repeating steps 7 & 8:
|
|---|
| 77 | 1. /usr/sbin/svcadm disable -s svc:/system/virtualbox/vboxtxs:default
|
|---|
| 78 | 2. /usr/sbin/svccfg delete svc:/system/virtualbox/vboxtxs:default
|
|---|
| 79 |
|
|---|
| 80 | Note. To configure dhcp for more a new interface the files
|
|---|
| 81 | /etc/hostname.<if#X> and /etc/dhcp.<ifnm#> have to exist. If you want the VM
|
|---|
| 82 | to work with any network card you throw at it, create /etc/*.pcn[01] and
|
|---|
| 83 | /etc/*.e1000g[012] as Solaris will remember it has seen the other variants
|
|---|
| 84 | before and use a different instance number (or something to that effect).
|
|---|
| 85 |
|
|---|
| 86 |
|
|---|
| 87 | Windows Installation
|
|---|
| 88 | --------------------
|
|---|
| 89 |
|
|---|
| 90 | 1. Log on as Administrator.
|
|---|
| 91 | 2. Set password to 'password'.
|
|---|
| 92 | 3. Start CMD.EXE or equivalent.
|
|---|
| 93 | 4. md C:\Apps
|
|---|
| 94 | 5. cd C:\Apps
|
|---|
| 95 | 6. Mount the validationkit iso.
|
|---|
| 96 | 7. copy D:\win\* C:\Apps
|
|---|
| 97 | 8. copy D:\win\<x86 or amd64>\* C:\Apps
|
|---|
| 98 | 9. Import the right service setup (see connection type above):
|
|---|
| 99 | nat) start C:\Apps\vboxtxs-nat.reg
|
|---|
| 100 | other) start C:\Apps\vboxtxs.reg
|
|---|
| 101 | 11. reboot / done
|
|---|
| 102 | 12. Do test.
|
|---|
| 103 |
|
|---|
| 104 |
|
|---|
| 105 | Testing the setup
|
|---|
| 106 | -----------------
|
|---|
| 107 |
|
|---|
| 108 | 1. Make sure the validationkit.iso is inserted.
|
|---|
| 109 | 2. Boot / reboot the guest.
|
|---|
| 110 | 3. Depending on the TXS transport options:
|
|---|
| 111 | nat) python testdrivers/tst-txsclient --reversed-setup
|
|---|
| 112 | other) python testdrivers/tst-txsclient --hostname <guest-ip>
|
|---|
| 113 |
|
|---|
| 114 |
|
|---|
| 115 |
|
|---|
