| 8 | | The kernel obviously uses some mechanism to realize it's running on virtualized h/w and pulls some additional info thru some hypervisor API |
| | 8 | The kernel obviously uses some mechanism to realize it's running on virtualized h/w and pulls some additional info thru some hypervisor API. |
| | 9 | |
| | 10 | [https://lkml.org/lkml/2008/10/20/469 Here's a link] to the relevant post on LKML, it's quite date and VirtualBox could use the same / similar mechanism as the original poster mentioned: "This patch also adds a hypervisor_get_tsc_freq function, instead of |
| | 11 | calibrating the frequency which can be error prone in virtualized |
| | 12 | environment, we ask the hypervisor for it. We get the frequency from |
| | 13 | the hypervisor by accessing the backdoor port if we are running on VMware. |
| | 14 | '''Other hypervisors too can add code to get frequency on their platform |
| | 15 | to this routine.''' " |
