diff options
| author |   Markos Chandras <mchandras@suse.de> | 2018-02-23 08:50:03 +0000 |
|---|---|---|
| committer | Markos Chandras <mchandras@suse.de> | 2018-02-23 09:32:11 +0000 |
| commit | 13f9ec07a26835064027817ff2a6f16cb7120cde (patch) | |
| tree | 2c692a20355b438124a637bb2a6974dc6dc5d850 /xci/scripts/vm | |
| parent | e92f64a24a04b08387af618a9bc398d0315bb7ce (diff) | |
xci: Switch default CPU model to 'host-model'
From upstream docs:
'The host-model mode is essentially a shortcut to copying host CPU
definition from capabilities XML into domain XML. Since the CPU
definition is copied just before starting a domain, exactly the
same XML can be used on different hosts while still providing
the best guest CPU each host supports'
It's probably safer to use that instead of 'host-passthrough' so
we can get a CPU (both for main VM and the nested ones) that libvirt
understands. Moreover, it's important to present a CPU that the
guest OS understands as well.
Change-Id: I25a8ff0e8635df9804c793d184f048cc86059ce0
Signed-off-by: Markos Chandras <mchandras@suse.de>
Diffstat (limited to 'xci/scripts/vm')
| -rwxr-xr-x | xci/scripts/vm/start-new-vm.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/xci/scripts/vm/start-new-vm.sh b/xci/scripts/vm/start-new-vm.sh index f3ddcc07..02c14b5c 100755 --- a/xci/scripts/vm/start-new-vm.sh +++ b/xci/scripts/vm/start-new-vm.sh @@ -83,7 +83,7 @@ update_clean_vm_files() { [[ $# -ne 1 ]] && usage && exit 1 -declare -r CPU=${XCI_CPU_TYPE:-host-passthrough} +declare -r CPU=${XCI_CPU_TYPE:-host-model} declare -r NCPUS=${XCI_NCPUS:-24} declare -r MEMORY=${XCI_MEMORY_SIZE:-65536} declare -r DISK=${XCI_DISK_SIZE:-500} |