Discussion:
[pve-devel] pve-manager: add IvyBridge cpu model
Alexandre Derumier
2015-06-03 12:21:44 UTC
Permalink
It's already added to qemuserver for qemu 2.3
Alexandre Derumier
2015-06-03 12:21:45 UTC
Permalink
Signed-off-by: Alexandre Derumier <***@odiso.com>
---
www/manager/form/CPUModelSelector.js | 1 +
1 file changed, 1 insertion(+)

diff --git a/www/manager/form/CPUModelSelector.js b/www/manager/form/CPUModelSelector.js
index 5d53527..901aab5 100644
--- a/www/manager/form/CPUModelSelector.js
+++ b/www/manager/form/CPUModelSelector.js
@@ -24,6 +24,7 @@ Ext.define('PVE.form.CPUModelSelector', {
['Nehalem', 'Nehalem'],
['Westmere', 'Westmere'],
['SandyBridge', 'SandyBridge'],
+ ['IvyBridge', 'IvyBridge'],
['Haswell', 'Haswell'],
['Broadwell', 'Broadwell'],
['Opteron_G1', 'Opteron_G1'],
--
2.1.4
Emmanuel Kasper
2015-06-03 14:11:15 UTC
Permalink
Hello Alexandre
Post by Alexandre Derumier
It's already added to qemuserver for qemu 2.3
_______________________________________________
Just to get the big picture, what does happen if I set my guest to this
cpu model, and my host is an for instance Opteron ( so there will be a
mismatch in cpuflags betwwen host and guest )

Is it safe ? Is there a performance penalty ?

Manu
Alexandre DERUMIER
2015-06-03 14:48:39 UTC
Permalink
Post by Alexandre Derumier
Post by Emmanuel Kasper
Just to get the big picture, what does happen if I set my guest to this
cpu model, and my host is an for instance Opteron ( so there will be a
mismatch in cpuflags betwwen host and guest )
Is it safe ? Is there a performance penalty ?
I think it'll will crash at boot ;) or don't start at all.

only kvm64 && qemu64 models are safe to use with any cpu model,
because they exposed only minimal flags which exist on both amd && intel.

If you have a mixed cluster with intel/amd, you need to used kvm64|qemu64 for live migration.

if you have only intel cluster or only amd cluster, you can choose the lowest cpu model you have in the cluster to be sure that migration will work.


----- Mail original -----
De: "Emmanuel Kasper" <***@proxmox.com>
À: "pve-devel" <pve-***@pve.proxmox.com>
Envoyé: Mercredi 3 Juin 2015 16:11:15
Objet: Re: [pve-devel] pve-manager: add IvyBridge cpu model

Hello Alexandre
Post by Alexandre Derumier
It's already added to qemuserver for qemu 2.3
_______________________________________________
Just to get the big picture, what does happen if I set my guest to this
cpu model, and my host is an for instance Opteron ( so there will be a
mismatch in cpuflags betwwen host and guest )

Is it safe ? Is there a performance penalty ?

Manu



_______________________________________________
pve-devel mailing list
pve-***@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Alexandre DERUMIER
2015-06-03 15:04:48 UTC
Permalink
Post by Alexandre Derumier
Post by Alexandre DERUMIER
don't start at all.
because we have also add the new cpu ensure flag, to be sure that all features are available

here the result with an intel process and opteron as cpu model

warning: host doesn't support requested feature: CPUID.01H:ECX.pclmulqdq|pclmuldq [bit 1]
warning: host doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
warning: host doesn't support requested feature: CPUID.01H:ECX.sse4.1|sse4_1 [bit 19]
warning: host doesn't support requested feature: CPUID.01H:ECX.sse4.2|sse4_2 [bit 20]
warning: host doesn't support requested feature: CPUID.01H:ECX.popcnt [bit 23]
warning: host doesn't support requested feature: CPUID.01H:ECX.aes [bit 25]
warning: host doesn't support requested feature: CPUID.01H:ECX.xsave [bit 26]
warning: host doesn't support requested feature: CPUID.01H:ECX.avx [bit 28]
warning: host doesn't support requested feature: CPUID.01H:ECX.f16c [bit 29]
warning: host doesn't support requested feature: CPUID.80000001H:EDX.pdpe1gb [bit 26]
warning: host doesn't support requested feature: CPUID.80000001H:EDX.rdtscp [bit 27]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.misalignsse [bit 7]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.3dnowprefetch [bit 8]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.xop [bit 11]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.tbm [bit 21]
kvm: Host doesn't support requested features
----- Mail original -----
De: "aderumier" <***@odiso.com>
À: "Emmanuel Kasper" <***@proxmox.com>
Cc: "pve-devel" <pve-***@pve.proxmox.com>
Envoyé: Mercredi 3 Juin 2015 16:48:39
Objet: Re: [pve-devel] pve-manager: add IvyBridge cpu model
Post by Alexandre Derumier
Post by Alexandre DERUMIER
Just to get the big picture, what does happen if I set my guest to this
cpu model, and my host is an for instance Opteron ( so there will be a
mismatch in cpuflags betwwen host and guest )
Is it safe ? Is there a performance penalty ?
I think it'll will crash at boot ;) or don't start at all.

only kvm64 && qemu64 models are safe to use with any cpu model,
because they exposed only minimal flags which exist on both amd && intel.

If you have a mixed cluster with intel/amd, you need to used kvm64|qemu64 for live migration.

if you have only intel cluster or only amd cluster, you can choose the lowest cpu model you have in the cluster to be sure that migration will work.


----- Mail original -----
De: "Emmanuel Kasper" <***@proxmox.com>
À: "pve-devel" <pve-***@pve.proxmox.com>
Envoyé: Mercredi 3 Juin 2015 16:11:15
Objet: Re: [pve-devel] pve-manager: add IvyBridge cpu model

Hello Alexandre
Post by Alexandre Derumier
It's already added to qemuserver for qemu 2.3
_______________________________________________
Just to get the big picture, what does happen if I set my guest to this
cpu model, and my host is an for instance Opteron ( so there will be a
mismatch in cpuflags betwwen host and guest )

Is it safe ? Is there a performance penalty ?

Manu



_______________________________________________
pve-devel mailing list
pve-***@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
_______________________________________________
pve-devel mailing list
pve-***@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Loading...