=item B<linux_vserver>
+This is printed for backwards compatibility with older virt-what which
+could not distinguish between a Linux VServer container guest and
+host.
+
+=item B<linux_vserver-guest>
+
This process is running in a Linux VServer container.
Status: contributed by Barış Metin
+=item B<linux_vserver-host>
+
+This process is running as the Linux VServer host (VxID 0).
+
+Status: contributed by Barış Metin and Elan Ruusamäe
+
+=item B<lxc>
+
+This process is running in a Linux LXC container.
+
+Status: contributed by Marc Fournier
+
=item B<kvm>
This guest is running on the KVM hypervisor using hardware
The guest is running inside IBM PowerVM Lx86 Linux/x86 emulator.
-Status: data supplied by Jeffrey Scheel, not confirmed
+Status: data originally supplied by Jeffrey Scheel, confimed by
+Yufang Zhang and RWMJ
=item B<qemu>
Status: contributed by Laurent Léonard
+=item B<virt>
+
+Some sort of virtualization appears to be present, but we are not sure
+what it is. In some very rare corner cases where we know that
+virtualization is hard to detect, we will try a timing attack to see
+if certain machine instructions are running much more slowly than they
+should be, which would indicate virtualization. In this case, the
+generic fact C<virt> is printed.
+
=item B<virtage>
This is Hitachi Virtualization Manager (HVM) Virtage
You might include this information in status and monitoring programs.
+=item System tuning (sometimes)
+
+You might use this program to tune an operating system so it runs
+better as a virtual machine of a particular hypervisor. However if
+installing paravirtualized drivers, it's better to check for the
+specific features your drivers need (eg. for the presence of PCI devices).
+
=back
=head1 SEE ALSO