. 97 7.1.1 Common third-party RDP viewers . . . . . . . . . . . . . . . . . . . . . 97 7.1.2 VBoxHeadless, the remote desktop server . . . . . . . . . . . . . . . . . 98 7.1.3 Step by step: creating a VBoxSDL is described in chapter 9.1, VBoxSDL, the simplified VM displayer, page 143. 4. Finally, VBoxHeadless is yet another front-end that produces no visible output on the host at all, but merely acts as a headless Linux server that has no X Window system installed. For details, see chapter 7.1.2, VBoxHeadless, the remote desktop server, page 98. 30 1 First steps If the above front-ends still do not satisfy

101 7.1.1 Common third-party RDP viewers . . . . . . . . . . . . . . . . . . . . . 101 7.1.2 VBoxHeadless, the remote desktop server . . . . . . . . . . . . . . . . . 102 7.1.3 Step by step: creating VBoxSDL is described in chapter 9.1, VBoxSDL, the simplified VM displayer, page 150. 4. Finally, VBoxHeadless is yet another front-end that produces no visible output on the host at all, but merely acts as a headless Linux server that has no X Window system installed. For details, see chapter 7.1.2, VBoxHeadless, the remote desktop server, page 102. If the above front-ends still do not satisfy your particular

103 7.1.1 Common third-party RDP viewers . . . . . . . . . . . . . . . . . . . . . 103 7.1.2 VBoxHeadless, the remote desktop server . . . . . . . . . . . . . . . . . 104 7.1.3 Step by step: creating VBoxSDL is described in chapter 9.1, VBoxSDL, the simplified VM displayer, page 158. 4. Finally, VBoxHeadless is yet another front-end that produces no visible output on the host at all, but merely acts as a headless Linux server that has no X Window system installed. For details, see chapter 7.1.2, VBoxHeadless, the remote desktop server, page 104. If the above front-ends still do not satisfy your particular

108 7.1.1 Common third-party RDP viewers . . . . . . . . . . . . . . . . . . . . . 108 7.1.2 VBoxHeadless, the remote desktop server . . . . . . . . . . . . . . . . . 109 7.1.3 Step by step: creating VBoxSDL is described in chapter 9.1, VBoxSDL, the simplified VM displayer, page 193. 4. Finally, VBoxHeadless is yet another front-end that produces no visible output on the host at all, but can act as a a headless Linux server that has no X Window system installed. For details, see chapter 7.1.2, VBoxHeadless, the remote desktop server, page 109. 34 1 First steps If the above front-ends still do not satisfy

108 7.1.1 Common third-party RDP viewers . . . . . . . . . . . . . . . . . . . . . 108 7.1.2 VBoxHeadless, the remote desktop server . . . . . . . . . . . . . . . . . 109 7.1.3 Step by step: creating VBoxSDL is described in chapter 9.1, VBoxSDL, the simplified VM displayer, page 192. 4. Finally, VBoxHeadless is yet another front-end that produces no visible output on the host at all, but can act as a a headless Linux server that has no X Window system installed. For details, see chapter 7.1.2, VBoxHeadless, the remote desktop server, page 109. 34 1 First steps If the above front-ends still do not satisfy

This ensures the entire Main API is both well-documented and well-tested. (The same applies to VBoxHeadless, which is not shown in the image.) 1.2 Two guises of the same “Main API”: the web service or COM/XPCOM process. The following are currently supported: • "gui": VirtualBox Qt GUI front-end • "headless": VBoxHeadless (VRDE Server) front-end • "sdl": VirtualBox SDL front-end • "emergencystop": reserved value, used front-end for virtual machines; but this API gets called internally by the existing front-ends such as VBoxHeadless and the VirtualBox GUI to acquire a write lock on the machine that they are running.) On success

This ensures the entire Main API is both well-documented and well-tested. (The same applies to VBoxHeadless, which is not shown in the image.) 1.2 Two guises of the same “Main API”: the web service or COM/XPCOM process. The following are currently supported: • "gui": VirtualBox Qt GUI front-end • "headless": VBoxHeadless (VRDE Server) front-end • "sdl": VirtualBox SDL front-end • "emergencystop": reserved value, used front-end for virtual machines; but this API gets called internally by the existing front-ends such as VBoxHeadless and the VirtualBox GUI to acquire a write lock on the machine that they are running.) On success

This ensures the entire Main API is both well-documented and well-tested. (The same applies to VBoxHeadless, which is not shown in the image.) 1.2 Two guises of the same “Main API”: the web service or COM/XPCOM process. The following are currently supported: • "gui": VirtualBox Qt GUI front-end • "headless": VBoxHeadless (VRDE Server) front-end • "sdl": VirtualBox SDL front-end • "emergencystop": reserved value, used front-end for virtual machines; but this API gets called internally by the existing front-ends such as VBoxHeadless and the VirtualBox GUI to acquire a write lock on the machine that they are running.) On success

This ensures the entire Main API is both well-documented and well-tested. (The same applies to VBoxHeadless, which is not shown in the image.) 1.2 Two guises of the same “Main API”: the web service or COM/XPCOM process. The following are currently supported: • "gui": VirtualBox Qt GUI front-end • "headless": VBoxHeadless (VRDE Server) front-end • "sdl": VirtualBox SDL front-end • "emergencystop": reserved value, used front-end for virtual machines; but this API gets called internally by the existing front-ends such as VBoxHeadless and the VirtualBox GUI to acquire a write lock on the machine that they are running.) On success

This ensures the entire Main API is both well-documented and well-tested. (The same applies to VBoxHeadless, which is not shown in the image.) 1.2 Two guises of the same “Main API”: the web service or COM/XPCOM process. The following are currently supported: • "gui": VirtualBox Qt GUI front-end • "headless": VBoxHeadless (VRDE Server) front-end • "sdl": VirtualBox SDL front-end • "emergencystop": reserved value, used front-end for virtual machines; but this API gets called internally by the existing front-ends such as VBoxHeadless and the VirtualBox GUI to acquire a write lock on the machine that they are running.) 207 5 Classes