Part A — Initial setup

A.1 Before you begin

CheckRequirement
Hardware64-bit server with CPU virtualization (Intel VT-x / AMD-V) enabled in BIOS/UEFI
Secure BootOff for install and for Permital Hypervisor boot on this appliance
DiskAt least 27 GiB free on the install target
NetworkKnown management IPv4 address, prefix, gateway, and DNS
MediaTOORCE HV ISO written to USB (or mounted as virtual media)
ConsoleKeyboard and monitor, or iDRAC/iLO remote console

Control plane (management) receives 30% of host RAM and 30% of the install disk. The rest of the disk is mounted at /var/lib/xen for local VM disks and ISO storage.

A.2 Boot the installer ISO

  1. Boot the server from the TOORCE HV USB/ISO.
  2. In the boot menu choose:
    • 1 Install Toorce Type-1 Hypervisor — interactive install
    • 2 Automatic install — needs kernel parameters (see A.4)
    • 3 Boot installed OS from hard disk — leave the live media

The live environment starts the installer on tty1. Packages come from the ISO; the target does not need internet during install. After install, apt is pointed at repo.toorce.com.

A.3 Interactive installer (TTY)

Banner: TOORCE HV installer.

Step 1 — What should be erased?

ChoiceMeaning
1Format only the disk you select for the OS
2Erase every discovered disk, then install on the selected OS disk

Step 2 — Disk number

Enter the number of the disk that receives the OS (≥ 27 GiB). Other disks stay unless you chose erase-all.

Step 3 — Network

PromptExampleMeaning
Address with prefix192.168.100.50/24Management address on netbr0
Gateway192.168.100.1Default gateway
DNS [gateway]Enter or 8.8.8.8DNS (Enter = use gateway)

Physical Ethernet ports are named eth0, eth1, … in PCI order and joined to the management bridge.

Step 4 — Web admin password

PromptRules
Web console userAlways admin at install
Web admin passwordAt least 6 characters
ConfirmMust match

Step 5 — Clock

Press Enter to keep it, or type a new time as YYYY-MM-DD HH:MM

Step 6 — Confirm erase

Type exactly ERASE. Summary before erase includes erase scope, disk, firmware mode (UEFI and BIOS loaders are written), control plane size, VM storage, RAM, address, gateway, DNS, and web user.

After reboot

Sign-in
Figure A.1 — Web console sign-in after install

A.4 Automatic install (optional)

Boot menu entry 2, or append to the kernel command line:

ParameterPurpose
hv.autoinstall=1Run unattended install
hv.erase=allErase every disk (omit to erase only the OS disk)
hv.address=Management CIDR, e.g. 192.168.100.50/24
hv.gateway=Gateway
hv.dns=DNS (optional)
hv.admin_pass=Web admin password
hv.datetime=Optional YYYY-MM-DD HH:MM

A.5 First-login checklist

  1. Sign in as admin.
  2. Open Hypervisor — confirm state, serial, address, free memory/CPU/disk.
  3. Open Storage — confirm local datastore and local VM disks; mount any SAN/NAS you need.
  4. Open Network — confirm netbr0 and add bridges/VLANs before creating VMs.
  5. (Optional) Create Resource profiles and Console users for self-service.
  6. Create the first virtual machine.
Hypervisor status
Figure A.2 — Hypervisor status (first health check)