===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== > edit the config file to reflect desired paths and settings: # SVCIDENT: the ID string to use for "Port URI:" in VM settings. $SVCIDENT=@vulture # WORKHOME: # base spool directory for serial I/O log files. # subdirectories will be created here using vmNames. $WORKHOME=/var/spool/vulture # LISTEN_HOST: default IP-addr/host for the "listen" column. $LISTEN_HOST=127.0.0.1 # local SSL file locations. $SSLCERTFILE=/etc/ssl/my-combo-cert-key.pem $SSLPRIVKEY=/etc/ssl/my-combo-cert-key.pem #vmName listen log-type-list #------ ------ ------------- 'my-VM-name' 30010 Raw,CSV #--- # generic entry for un-matched VM names: # - empty VM name will match anything. # - no listening port (ie. no interactive connections). # - save serial-I/O from VM in raw format only. '' - Raw #### ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== > adjust the ./in-wrapper script to use your correct local paths. eg. vspy=/usr/local/lib/vulture/in-vSPC.py logf=/var/log/vulture-err conf="/usr/local/etc/vulture.conf" ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== > configure an inetd server to accept incoming connections. see ./inetd-cf for an example of entries for basic inetd. ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== > configure VM (Edit Settings) to send serial I/O via network: > Edit Settings > [ Add... ] Serial Port | | Connection | ... | | (*) Use network ... | (*) Client (VM initiates connection) | Port URI: [ @vulture ] ... [ plain ] | [+] Use Virtual Serial Port Concentrator | vSPC URI: [ telnet://888.10.22.33:40000 ] [ or SSL ] | [+] Use Virtual Serial Port Concentrator | vSPC URI: [ telnets://888.10.22.33:49999 ] ... where {888.10.22.33} is the IP-address of your inetd server. ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== > configure firewall on ESXi server(s) to permit VM serial I/O traffic to the inetd server. Using vSphere client, select the ESXi host and ... [ Configuration > Security Profile > Firewall > Properties ] ### either #### ... to allow one of ... [] VM serial port connected to vSPC [] VM serial port connected over network ### or #### ... add {888.10.22.33} to the list for ... [+] NFS Client ----- Or via SSH to the ESXi host, to add IPs to ESX firewall ... (where the 'nfsClient' ruleset permits all ports outbound) # esxcli network firewall ruleset allowedip add -r nfsClient -i 888.10.22.33 ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== > to verify that a VM's serial I/O server is working: # ls /var/spool/vulture/{vmName}/ can expect to see: ",pid" = PID file of the in-vSPCy.py for this serial-port. {file(s) with a timestamp} = timestamp is the start-up time for that in-vSPC.py session. = contains serial I/O saved since that time-stamp until its in-vSPC.py server stopped/stops. ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== > to connect to a VM's remote serial port: # ./in-wrapper connect {vmName} launches a telnet connection to the port where in-vSPC.py is listening NB: {vmName} must have a "listen" port configured in vulture-conf. ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== =====