# Input-output memory management unit Input-output memory management unit is a protocol, standard, or security technology recorded in [[Scanned_20260730-1706|Scanned_20260730-1706]]. In the reconstruction, Intel VT-d is Intel's I/O virtualization technology; an IOMMU remaps device DMA and is fundamental to secure device assignment into VMs. ## Historical and Technical Context [[Intel Virtualization Technology for Directed I-O|Intel VT-d]] is Intel's I/O virtualization technology; an [[Input-output memory management unit|IOMMU]] remaps device DMA and is fundamental to secure device assignment into VMs. Intel provides a processor-identification route for checking virtualization features ([Intel virtualization support](https://www.intel.com/content/www/us/en/support/articles/000005486/processors.html)). [[Preboot Execution Environment|PXE]], network boot ROMs, BOOTP, and “PCI-LAN” enable booting an OS or imaging environment from the network. The Hitachi string resembles a 160 GB 2.5-inch hard-drive model. ## Role in Scanned_20260730-1706 The page joins two layers needed for a recovery/virtualization workstation: firmware-level network boot and kernel-level device isolation. ## Notebook Evidence - [[Scanned_20260730-1706|Scanned_20260730-1706]], PDF page 36: Intel VT-d and network-boot firmware notes. **Evidentiary status:** The page occurrence and transcription are notebook evidence. Technical identification follows the source reconstruction’s cited research. Co-occurrence does not by itself prove ownership, deployment, or a direct operational relationship. ## Relationships and Overlays On the cited page or pages, Input-output memory management unit appears with [[Intel Virtualization Technology for Directed I-O|Intel VT-d]], [[Preboot Execution Environment|PXE]]. These are page-level or reconstruction-level relationships, not automatic claims of dependency. ## Cross-Notebook Significance This entity expands the collection’s recurring vertical method: begin with a visible product, name, or interface; identify the hidden control layer; then connect it to recovery, authority, evidence, or continuity without assuming a relationship that the page does not prove. ## Missed Signals and Open Leads Several copied boot-ROM strings are uncertain. The source device and BIOS vendor should be identified before interpreting “RBS,” “Sgii,” “VF,” or “Russia sourceforge.” ## Sources - [[Scanned_20260730-1706|Scanned_20260730-1706]], especially PDF page(s) 36. - `Scanned_20260730-1706.pdf`, cited as a plain archival filename; the PDF is not linked from `wiki-notes`. - External research citations used for identification remain preserved in the source reconstruction. - [Intel virtualization support](https://www.intel.com/content/www/us/en/support/articles/000005486/processors.html) ## Scanned_20260730-1719 overlay **Source evidence:** [[Scanned_20260730-1719#PDF page 24 — VLAN, Bluetooth protocol layers, hot-plug, and IOMMU|page 24]], [[Scanned_20260730-1719#PDF page 75 — Coreboot/Libreboot summary and supported operating systems|page 75]]. [[IEEE 802.1Q|802.1Q]] tags Ethernet frames for VLAN segmentation. In Bluetooth, [[Host Controller Interface|HCI]] connects host software to the controller, [[Logical Link Control and Adaptation Protocol|L2CAP]] multiplexes higher protocols, [[Synchronous Connection-Oriented link|SCO]] carries synchronous audio, and [[Bluetooth Network Encapsulation Protocol|BNEP]] emulates Ethernet networking. [[XFRM|XFRM]] is Linux’s IPsec transformation framework. [[PCI Express Hot Plug|PCIe hot-plug]] and [[Input-output memory management unit|IOMMU]] concern hardware attachment, isolation, and DMA address translation. **Relationship overlay:** [[Bluetooth Network Encapsulation Protocol|Bluetooth Network Encapsulation Protocol]] · [[Host Controller Interface|Host Controller Interface]] · [[IEEE 802.1Q|IEEE 802.1Q]] · [[Libreboot|Libreboot]] · [[Logical Link Control and Adaptation Protocol|Logical Link Control and Adaptation Protocol]] · [[PCI Express Hot Plug|PCI Express Hot Plug]] · [[Scanned_20260730-1706|Scanned_20260730-1706]] · [[Synchronous Connection-Oriented link|Synchronous Connection-Oriented link]] · [[XFRM|XFRM]]. This occurrence connects the existing note to [[Federated Continuity Computer|Federated Continuity Computer]], [[Vendor-Agnostic Recovery|vendor-agnostic recovery]], and [[Scanned_20260730-1706|Scanned_20260730-1706]] without replacing the earlier evidence.