On 08/05/2018 03:48 PM, Marek Marczykowski-Górecki wrote:
Use preferred name: 'xen'.
I'd be fine with this change if the actual code used the preferred name too :-). E.g. config containing <type arch='x86_64' machine='xenpv'>xen</type> will be shown as <type arch='x86_64' machine='xenpv'>linux</type> after virsh define; virsh dumpxml. Also, virsh domxml-from-native will produce the linux variant. Regards, Jim
Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> --- docs/formatdomain.html.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 19b7312..8043c7c 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -144,8 +144,8 @@ <dd>The content of the <code>type</code> element specifies the type of operating system to be booted in the virtual machine. <code>hvm</code> indicates that the OS is one designed to run - on bare metal, so requires full virtualization. <code>linux</code> - (badly named!) refers to an OS that supports the Xen 3 hypervisor + on bare metal, so requires full virtualization. <code>xen</code> + refers to an OS that supports the Xen 3 hypervisor guest ABI. There are also two optional attributes, <code>arch</code> specifying the CPU architecture to virtualization, and <code>machine</code> referring to the machine