Running GUI Linux in a virtual machine on a Mac

At a glance

Project structure

Source bundle/
├── GUILinuxVirtualMachineSampleApp/
│   ├── AppDelegate.swift
│   ├── Base.lproj/
│   │   └── MainMenu.xib
│   ├── GUILinuxVirtualMachineSampleApp.entitlements
│   └── Info.plist
├── Configuration/
│   └── SampleCode.xcconfig
└── GUILinuxVirtualMachineSampleApp.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 6 project/configuration file(s) and 1 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["Virtualization APIs"]
    N1 --> N2

Reference code

GUILinuxVirtualMachineSampleApp/AppDelegate.swift:15 — architecture anchor

@main
class AppDelegate: NSObject, NSApplicationDelegate, VZVirtualMachineDelegate {
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Virtualization.

Ownership and state

classDiagram
    AppDelegate *-- NSHomeDirectory : vmBundlePath
    AppDelegate o-- NSWindow : window
    AppDelegate o-- VZVirtualMachineView : virtualMachineView
    AppDelegate o-- VZVirtualMachine : virtualMachine

Ownership evidence

GUILinuxVirtualMachineSampleApp/AppDelegate.swift:10 — stored dependency or nearest verified ownership anchor

let vmBundlePath = NSHomeDirectory() + "/GUI Linux VM.bundle/"

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Class and protocol design

GUILinuxVirtualMachineSampleApp/AppDelegate.swift:16 — representative type boundary

class AppDelegate: NSObject, NSApplicationDelegate, VZVirtualMachineDelegate {
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

GUILinuxVirtualMachineSampleApp/AppDelegate.swift:22 — representative boundary

    private var virtualMachine: VZVirtualMachine!

    private var installerISOPath: URL?

    private var needsInstall = true

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: Delegate: AppDelegate.
• Protocols: no local protocol declaration in the scanned source.
• Methods: createVMBundle, createMainDiskImage, createBlockDeviceConfiguration, computeCPUCount, computeMemorySize, createAndSaveMachineIdentifier, retrieveMachineIdentifier, createEFIVariableStore.
• Files: GUILinuxVirtualMachineSampleApp/AppDelegate.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches Virtualization through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation