Difference between revisions of "VM Feature Identification"
From Xen
Rcpavlicek (talk | contribs) |
Rcpavlicek (talk | contribs) (→MODE DETECTION) |
||
| Line 3: | Line 3: | ||
== MODE DETECTION == |
== MODE DETECTION == |
||
| + | The output of the <pre>dmesg</pre> command contains many useful bits of information about the processor mode: |
||
| − | From dmesg: |
||
| + | |||
| + | === HVM === |
||
If your VM is either HVM or PVHVM, look for: |
If your VM is either HVM or PVHVM, look for: |
||
| Line 10: | Line 12: | ||
</pre> |
</pre> |
||
| + | === PV === |
||
If your VM is PV or PVH, look for: |
If your VM is PV or PVH, look for: |
||
<pre> |
<pre> |
||
[ 0.000000] Booting paravirtualized kernel on Xen |
[ 0.000000] Booting paravirtualized kernel on Xen |
||
| + | </pre> |
||
| + | |||
| + | This message indicates that PV timers are in use: |
||
| + | <pre> |
||
| + | [ 0.000000] Xen: using vcpuop timer interface |
||
</pre> |
</pre> |
||
Revision as of 16:40, 13 October 2014
When you control your own hypervisor, you are aware of the features you are using, since you have configured the system and the VMs. However, if you are using a service provider for your hosting or cloud, you need to do some detective work to determine the hypervisor mode and features employed.
Contents
MODE DETECTION
The output of the
dmesg
command contains many useful bits of information about the processor mode:
HVM
If your VM is either HVM or PVHVM, look for:
[ 0.000000] Hypervisor detected: Xen HVM
PV
If your VM is PV or PVH, look for:
[ 0.000000] Booting paravirtualized kernel on Xen
This message indicates that PV timers are in use:
[ 0.000000] Xen: using vcpuop timer interface
REFERENCES
- A truly great article by Brendan Gregg
