8 VBoxManage • --teleporterport port, --teleporteraddress address: these must be used with –teleporter and tell the virtual machine on which port and address it should listen for a teleporting request from another virtual machine. port can be any free TCP/IP port number (e.g. 6000) address can be any IP address or hostname and specifies the TCP/IP socket to bind to. The default is “0.0.0.0”, which means any address. • --teleporterpassword password: if this optional argument is given, then the tele- porting request will only succeed if the source machine specifies the same password as the one given with this command. Note: Currently, the password is stored without encryption (i.e. in clear text) in the XML machine configuration file. • --cpuid leaf eax ebx ecx edx: Advanced users can use this command be- fore a teleporting operation to restrict the virtual CPU capabilities that VirtualBox presents to the guest operating system. This must be run on both the source and the target machines involved in the teleporting and will then modify what the guest sees when it executes the CPUID machine instruction. This might help with misbehaving applications that wrongly assume that certain CPU capabilities are present. The meaning of the parameters is hard- ware dependent please refer to the AMD or Intel processor manuals. 8.8 VBoxManage import This command imports a virtual appliance in OVF format by copying the virtual disk images and creating virtual machines in VirtualBox. See chapter 1.12, Importing and exporting virtual machines, page 26 for an introduction to appliances. The import subcommand takes at least the path name of an OVF file as input and expects the disk images, if needed, in the same directory as the OVF file. A lot of additional command- line options are supported to control in detail what is being imported and modify the import parameters, but the details depend on the content of the OVF file. It is therefore recommended to first run the import subcommand with the --dry-run or -n option. This will then print a description of the appliance’s contents to the screen how it would be imported into VirtualBox, together with the optional command-line options to influence the import behavior. As an example, here is the screen output with a sample appliance containing a Windows XP guest: VBoxManage import WindowsXp.ovf --dry-run Interpreting WindowsXp.ovf... OK. Virtual system 0: 0: Suggested OS type: "WindowsXP" (change with "--vsys 0 --ostype type" use "list ostypes" to list all) 1: Suggested VM name "Windows XP Professional_1" (change with "--vsys 0 --vmname name") 3: Number of CPUs: 1 (change with "--vsys 0 --cpus n") 4: Guest memory: 956 MB (change with "--vsys 0 --memory MB") 5: Sound card (appliance expects "ensoniq1371", can change on import) (disable with "--vsys 0 --unit 5 --ignore") 6: USB controller (disable with "--vsys 0 --unit 6 --ignore") 7: Network adapter: orig bridged, config 2, extra type=bridged 8: Floppy (disable with "--vsys 0 --unit 8 --ignore") 9: SCSI controller, type BusLogic 115