Historical OpenVMS and Tru64 UNIX field reports include boot halts that end at the console with an XDELTA not loaded message. In the captured OpenVMS example below, issuing INIT at the console reset the guest and allowed another boot attempt. That observation has not been reproduced across the 5.1.0 candidate guest matrix, so INIT is not a universal remedy for every boot halt. Record the halt code and program counter first; if the same halt recurs, investigate the guest and boot configuration rather than repeatedly resetting it.

>>>b
(boot dka0.0.0.6.0 -flags 0)
block 0 of dka0.0.0.6.0 is a valid boot block
reading 904 blocks from dka0.0.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 71000
initializing HWRPB at 2000
initializing page table at 1e4000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
 
   OpenVMS (TM) Alpha Operating System, Version V7.1
 
ff.halt code = 5
HALT instruction executed
PC = 110678
fe.fd.fc.fb.fa.f9.f8.breakpoint at PC 1108e0 desired, XDELTA not loaded
f7.f6.f5.
ef.df.ee.ed.ec.f4.eb.ea.e9.e8.e7.e6.....e5.
V7.0-9, built on Mar 18 1999 at 13:25:37
>>>