| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
- MicroVAX II
- MicroVAX 3600
- MicroVAX 3900
- MicroVAX 3100 models 96 and 98
- VAXserver 3600
- VAXserver 3900
- VAXstation 4000 models 90, 106, 108, 700 and 705
- VAX 6310
- VAX 6610, 6620, 6630, 6640, 6650 and 6660
...
| Include Page | ||||
|---|---|---|---|---|
|
The principles of VAX Hardware Virtualization
...
The following table explains which hardware boards we virtualize:
Subsystem | Covered VAX hardware |
UART, QUART, CXA16, CXB16, CXY08, DHQ11, DHV11, DZV11, | |
RQDX3, KDB50, TQK50, TUK50, KDM70 | |
NCR53C94 | |
| DSSI Subsystem | SHAC, HSD50 |
| CI Subsystem | CIXCD, HSJ50 |
| Network Controllers | DEQNA, DESQA, DELQA, DEUNA, DELUA, DEMNA, DEBNI, PMADAA |
...
| Include Page | ||||
|---|---|---|---|---|
|
Host platform
The Virtualization Software presents standard VAX devices to the VAX operating system, allowing the OS to function as though it were still running on a VAX computer. For example, virtual disk container files in a directory or device files in /dev directory of the host Linux platform are presented by the Virtualization Software to the VAX OS as emulated SCSI disks attached to a SCSI adapter.
...
A similar translation process is also valid for other emulated hardware devices.
...
| Include Page | ||||
|---|---|---|---|---|
|