cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncVirtualBox Test eXecution Service
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync=================================
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncThis readme briefly describes how to install the Test eXecution Service (TXS)
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncon the various systems.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncThere are currently two transport options for the TXS:
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync - The default is to use it in TCP server mode, i.e. the test script needs
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync to know the guest's IP and therefore requires guest additions to be
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync installed as well. (Please use the latest stable additions compatible with
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync the VBox host versions you intend to test.)
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync - The alternative is for NATted setups where TXS will act like a TCP client
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync and try connect to the test script on the host. Since this require that
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync TXS knows which IP to connect to, it's only really possible in a NATted
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync setup where we know the host IP is 10.0.2.2.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncSince r85596 TXS operates in both modes by default so the nat version of
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncthe init scripts is not required anymore. Instead the other type can be installed
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncfor both cases.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncLinux Installation
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync------------------
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync2. scp/download VBoxValidationKit*.zip there.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync3. unzip VBoxValidationKit*.zip
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync4. chmod -R u+w,a+x /root/validationkit/
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync6. Link up the right init script (see connection type above):
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync nat) ln -s ../../root/validationkit/linux/vboxtxs-nat ./vboxtxs
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync other) ln -s ../../root/validationkit/linux/vboxtxs ./vboxtxs
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync7. Add vboxtxs to runlevels 2, 3, 5 and any other that makes sense
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync on the distro. There is usually some command for doing this...
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync8. Check the cdrom location in vboxtxs and fix it so it's correct, make sure
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync to update in svn as well.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync9. reboot / done.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncOS/2 Installation
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync--------------------
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync1. Start an "OS/2 Window" ("OS/2 System" -> "Command Prompts")
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync2. md C:\Apps
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync3. cd C:\Apps
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync4. Mount the validationkit iso.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync5. copy D:\os2\x86\* C:\Apps
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync5. copy D:\os2\x86\libc*.dll C:\OS2\DLL\
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync6. Open C:\startup.cmd in an editor (tedit.exe for instance or e.exe).
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync7. Add the line "start /C C:\Apps\TestExecService.exe --foreground" at the top of the file.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync8. reboot / done
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncSolaris Installation
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync--------------------
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync1. Start the guest and open a root console.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync4. scp/download VBoxValidationKit*.zip there.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync5. unzip VBoxValidationKit*.zip
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync6. chmod -R u+w,a+x /opt/VBoxTest/
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync7. Import the right service setup depending on the Solaris version:
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync <= 10u9) /usr/sbin/svccfg import /opt/VBoxTest/validationkit/solaris/vboxtxs-sol10.xml
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync >= 11.0) /usr/sbin/svccfg import /opt/VBoxTest/validationkit/solaris/vboxtxs.xml
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync8. /usr/sbin/svcadm enable svc:/system/virtualbox/vboxtxs
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync9. reboot / done.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncTo remove the service before repeating steps 7 & 8:
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync1. /usr/sbin/svcadm disable -s svc:/system/virtualbox/vboxtxs:default
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync2. /usr/sbin/svccfg delete svc:/system/virtualbox/vboxtxs:default
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncNote. To configure dhcp for more a new interface the files
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync/etc/hostname.<if#X> and /etc/dhcp.<ifnm#> have to exist. If you want the VM
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncto work with any network card you throw at it, create /etc/*.pcn[01] and
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync/etc/*.e1000g[012] as Solaris will remember it has seen the other variants
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncbefore and use a different instance number (or something to that effect).
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncWindows Installation
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync--------------------
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync1. Log on as Administrator.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync2. Set password to 'password'.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync3. Start CMD.EXE or equivalent.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync4. md C:\Apps
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync5. cd C:\Apps
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync6. Mount the validationkit iso.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync7. copy D:\win\* C:\Apps
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync8. copy D:\win\<x86 or amd64>\* C:\Apps
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync9. Import the right service setup (see connection type above):
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync nat) start C:\Apps\vboxtxs-nat.reg
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync other) start C:\Apps\vboxtxs.reg
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync11. reboot / done
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync12. Do test.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsyncTesting the setup
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync-----------------
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync1. Make sure the validationkit.iso is inserted.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync2. Boot / reboot the guest.
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync3. Depending on the TXS transport options:
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync nat) python testdrivers/tst-txsclient --reversed-setup
cf22150eaeeb72431bf1cf65c309a431454fb22bvboxsync other) python testdrivers/tst-txsclient --hostname <guest-ip>