Difference between revisions of "VM Feature Identification"

From Xen
(HVM-type:)
(HVM-type:)
Line 15: Line 15:
 
[ 0.000000] Booting paravirtualized kernel on Xen HVM
 
[ 0.000000] Booting paravirtualized kernel on Xen HVM
 
</pre>
 
</pre>
  +
  +
If it is actually PVHVM, you could see messages like:
  +
<pre>
  +
[ 0.127240] Xen: using vcpuop timer interface
  +
</pre>
  +
or:
  +
<pre>
  +
[ 1.424040] Initialising Xen virtual ethernet driver.
  +
</pre>
  +
indicating that PV drivers are being utilized within the HVM machine.
   
 
=== PV-type: ===
 
=== PV-type: ===

Revision as of 16:55, 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.

MODE DETECTION

The output of the dmesg command contains many useful bits of information about the processor mode:

HVM-type:

If your VM is either HVM or PVHVM, look for:

[    0.000000] Hypervisor detected: Xen HVM

and:

[    0.000000] Booting paravirtualized kernel on Xen HVM

If it is actually PVHVM, you could see messages like:

[    0.127240] Xen: using vcpuop timer interface

or:

[    1.424040] Initialising Xen virtual ethernet driver.

indicating that PV drivers are being utilized within the HVM machine.

PV-type:

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

If PV network drivers are in use, you might see:

[    0.432488] Initialising Xen virtual ethernet driver.

REFERENCES