2004-2015 Oracle Corporation http://www.virtualbox.org Contents 1 First steps 10 1.1 Why is virtualization useful? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.2 Some terminology . . . . . . . . 169 10.3 Hardware vs. software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 171 10.4 Details about software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 172 10.5 Details about hardware virtualization . . . . . . . . . . . . . . . . . . . . . . . . 174 10.6 Nested paging and VPIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 11 VirtualBox

2004-2015 Oracle Corporation http://www.virtualbox.org Contents 1 First steps 11 1.1 Why is virtualization useful? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.2 Some terminology . . . . . . . . 190 10.3 Hardware vs. software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 192 10.4 Details about software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 193 10.5 Details about hardware virtualization . . . . . . . . . . . . . . . . . . . . . . . . 195 10.6 Nested paging and VPIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 11 VirtualBox

2004-2016 Oracle Corporation http://www.virtualbox.org Contents 1 First steps 11 1.1 Why is virtualization useful? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.2 Some terminology . . . . . . . . 200 10.3 Hardware vs. software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 202 10.4 Details about software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 203 10.5 Details about hardware virtualization . . . . . . . . . . . . . . . . . . . . . . . . 205 10.6 Nested paging and VPIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 11 VirtualBox

2004-2020 Oracle Corporation http://www.virtualbox.org Contents 1 First steps 12 1.1 Why is virtualization useful? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.2 Some terminology . executables and components . . . . . . . . . . . . . . . . . . . . . . 250 10.3 Hardware vs. software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 252 10.4 Paravirtualization providers . . . . . . . . . 253 10.5 Details about software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 253 10.6 Details about hardware virtualization . . . . . . . . . . . . . . . . . . . . . . .

2004-2018 Oracle Corporation http://www.virtualbox.org Contents 1 First steps 12 1.1 Why is virtualization useful? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.2 Some terminology . executables and components . . . . . . . . . . . . . . . . . . . . . . 249 10.3 Hardware vs. software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 251 10.4 Paravirtualization providers . . . . . . . . . 252 10.5 Details about software virtualization . . . . . . . . . . . . . . . . . . . . . . . . 252 10.6 Details about hardware virtualization . . . . . . . . . . . . . . . . . . . . . . .

function calls (de-virtualization) CPin pin { GPIO_PIN_6 }; CLed led { &pin }; while (true) { led.toggle(); delay(1000); } 41Dynamic Polymorphism without de-virtualization 42

: push 08000198 <_ZN4CPin5resetEv>: ... 080001b0 <_ZN4CPin3setEv>: ...Dynamic Polymorphism without de-virtualization Load the vtable address in r3. 43

: push {r0, r1, r2, lr} ldr r3, [pc, #28] 0x08000258 : 0x080001b1 0x0800025c : 0x08000199 CPin vtableDynamic Polymorphism without de-virtualization Load the address of the set method from the vtable into r3. 44

: push {r0, r1,

represents userspace code. At the bottom of the stack resides the hypervisor – the core of the virtualization engine, con- trolling execution of the virtual machines and making sure they do not conflict mentioned blocks. This API, which we call the “Main API”, exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces) VirtualBox and VBoxManage use nothing but this API as well – there are no hidden backdoors into the virtualization engine for our own front- ends. This ensures the entire Main API is both well-documented and

represents userspace code. At the bottom of the stack resides the hypervisor – the core of the virtualization engine, con- trolling execution of the virtual machines and making sure they do not conflict mentioned blocks. This API, which we call the “Main API”, exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces) VirtualBox and VBoxManage use nothing but this API as well – there are no hidden backdoors into the virtualization engine for our own front- ends. This ensures the entire Main API is both well-documented and

represents userspace code. At the bottom of the stack resides the hypervisor – the core of the virtualization engine, con- trolling execution of the virtual machines and making sure they do not conflict mentioned blocks. This API, which we call the “Main API”, exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces) VirtualBox and VBoxManage use nothing but this API as well – there are no hidden backdoors into the virtualization engine for our own front- ends. This ensures the entire Main API is both well-documented and

represents userspace code. At the bottom of the stack resides the hypervisor – the core of the virtualization engine, con- trolling execution of the virtual machines and making sure they do not conflict mentioned blocks. This API, which we call the “Main API”, exposes the entire feature set of the virtualization engine below. It is completely documented in this SDK Reference – see chapter 5, Classes (interfaces) VirtualBox and VBoxManage use nothing but this API as well – there are no hidden backdoors into the virtualization engine for our own front- ends. This ensures the entire Main API is both well-documented and