Differences

This shows you the differences between two versions of the page.

--- doc:appunti:linux:sa:virtualization [2019/08/28 12:01] – [Libvirt to manage KVM hosts: install, start, stop] niccolo
+++ doc:appunti:linux:sa:virtualization [2019/08/28 12:09] (current) – [Libvirt to manage KVM hosts: install, start, stop] niccolo
@@ Line 272: / Line 272: @@
 The VNC port can be assigned automatically (seting it to **''%%port='autoport'%%''**), or assigned statically, e.g. **''%%port='5901'%%''**.
-The **%%<type>%%** and **%%<cpu>%%** tags of the XML configuration file, determines what CPU is offered to the guest machine. Here it is the default choosed by ''virt-install'' on a Xeon host (Debian 10 Buster with libvirt 5.0):
+The **%%<os><type>%%** and **%%<cpu>%%** tags of the XML configuration file, determines what CPU is offered to the guest machine. Here it is the default choosed by ''virt-install'' on a Xeon host (Debian 10 Buster with libvirt 5.0):
 <code xml>
-  <type arch='x86_64' machine='pc'>hvm</type>
+  <os>
+    <type arch='x86_64' machine='pc'>hvm</type>
+  </os>
   <cpu mode='host-model' check='partial'>
     <model fallback='allow'/>
   </cpu>
 </code>
+See the documentation about **[[https://libvirt.org/formatdomain.html#elementsOS|Operating system booting]]** and **[[https://libvirt.org/formatdomain.html#elementsCPU|CPU model and topology]]** for more info about **%%<os><type>%%** and **%%<cpu>%%** tags.
 You can use a **specific option** if you have an **Intel CPU**: