From brent.hartzell at outlook.com Sat Dec 20 11:31:24 2014 Content-Type: multipart/mixed; boundary="===============5317796433622563414==" MIME-Version: 1.0 From: Brent Hartzell To: users at ovirt.org Subject: [ovirt-users] CPU Type Date: Sat, 20 Dec 2014 11:31:18 -0500 Message-ID: --===============5317796433622563414== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ------=3D_NextPart_000_0276_01D01C48.79079EF0 Content-Type: text/plain; charset=3D"us-ascii" Content-Transfer-Encoding: 7bit Hello, = Is there a way to add "Xeon" or another class of CPU Type to oVirt? We have some test hosts, which use a combo of the following CPU types: = Xeon L5420 Xeon E5430 Xeon E5420 = The only two CPU Types that will work in oVirt are Conroe & Penryn. Inside of a VM, it reports "Core 2 Duo". = Host reports: model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz = = VM reports: model name : Intel Core 2 Duo P9xxx (Penryn Class Core 2) = = // = Is there a way to have the VM report the correct CPU? It doesn't appear to cause any performance or other issues, but seems to be just a display issue. My concern though, is that we may not be able to add other servers with different Intels to the same cluster, for example, new hosts with E5-XXXX or E3-XXXX processors. Can someone confirm this wouldn't be an issue? = ------=3D_NextPart_000_0276_01D01C48.79079EF0 Content-Type: text/html; charset=3D"us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

Is there a = =3D way to add “Xeon” or another class of CPU Type to oVirt? We =3D have some test hosts, which use a combo of the following CPU =3D types:

 

Xeon L5420

Xeon = =3D E5430

Xeon E5420

 

The only tw= o =3D CPU Types that will work in oVirt are Conroe & Penryn. Inside of a =3D VM, it reports “Core 2 Duo”.

 

Host =3D reports:

model =3D name      : Intel(R) Xeon(R) =3D CPU           =3D E5430  @ 2.66GHz

 

 

VM =3D reports:

model =3D name      : Intel Core 2 Duo P9xxx (Penryn =3D Class Core 2)

 

 

//

 

Is there a = =3D way to have the VM report the correct CPU? It doesn’t appear to =3D cause any performance or other issues, but seems to be just a display =3D issue. My concern though, is that we may not be able to add other =3D servers with different Intels to the same cluster, for example, new =3D hosts with E5-XXXX or E3-XXXX processors. Can someone confirm this =3D wouldn’t be an issue?

 

------=3D_NextPart_000_0276_01D01C48.79079EF0-- --===============5317796433622563414== Content-Type: multipart/alternative MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.bin" LS0tLS0tPV9OZXh0UGFydF8wMDBfMDI3Nl8wMUQwMUM0OC43OTA3OUVGMApDb250ZW50LVR5cGU6 IHRleHQvcGxhaW47IGNoYXJzZXQ9InVzLWFzY2lpIgpDb250ZW50LVRyYW5zZmVyLUVuY29kaW5n OiA3Yml0CgpIZWxsbywKCiAKCklzIHRoZXJlIGEgd2F5IHRvIGFkZCAiWGVvbiIgb3IgYW5vdGhl ciBjbGFzcyBvZiBDUFUgVHlwZSB0byBvVmlydD8gV2UgaGF2ZQpzb21lIHRlc3QgaG9zdHMsIHdo aWNoIHVzZSBhIGNvbWJvIG9mIHRoZSBmb2xsb3dpbmcgQ1BVIHR5cGVzOgoKIAoKWGVvbiBMNTQy MAoKWGVvbiBFNTQzMAoKWGVvbiBFNTQyMAoKIAoKVGhlIG9ubHkgdHdvIENQVSBUeXBlcyB0aGF0 IHdpbGwgd29yayBpbiBvVmlydCBhcmUgQ29ucm9lICYgUGVucnluLiBJbnNpZGUKb2YgYSBWTSwg aXQgcmVwb3J0cyAiQ29yZSAyIER1byIuCgogCgpIb3N0IHJlcG9ydHM6Cgptb2RlbCBuYW1lICAg ICAgOiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTU0MzAgIEAgMi42NkdIegoKIAoK IAoKVk0gcmVwb3J0czoKCm1vZGVsIG5hbWUgICAgICA6IEludGVsIENvcmUgMiBEdW8gUDl4eHgg KFBlbnJ5biBDbGFzcyBDb3JlIDIpCgogCgogCgovLwoKIAoKSXMgdGhlcmUgYSB3YXkgdG8gaGF2 ZSB0aGUgVk0gcmVwb3J0IHRoZSBjb3JyZWN0IENQVT8gSXQgZG9lc24ndCBhcHBlYXIgdG8KY2F1 c2UgYW55IHBlcmZvcm1hbmNlIG9yIG90aGVyIGlzc3VlcywgYnV0IHNlZW1zIHRvIGJlIGp1c3Qg YSBkaXNwbGF5IGlzc3VlLgpNeSBjb25jZXJuIHRob3VnaCwgaXMgdGhhdCB3ZSBtYXkgbm90IGJl IGFibGUgdG8gYWRkIG90aGVyIHNlcnZlcnMgd2l0aApkaWZmZXJlbnQgSW50ZWxzIHRvIHRoZSBz YW1lIGNsdXN0ZXIsIGZvciBleGFtcGxlLCBuZXcgaG9zdHMgd2l0aCBFNS1YWFhYIG9yCkUzLVhY WFggcHJvY2Vzc29ycy4gQ2FuIHNvbWVvbmUgY29uZmlybSB0aGlzIHdvdWxkbid0IGJlIGFuIGlz c3VlPwoKIAoKCi0tLS0tLT1fTmV4dFBhcnRfMDAwXzAyNzZfMDFEMDFDNDguNzkwNzlFRjAKQ29u dGVudC1UeXBlOiB0ZXh0L2h0bWw7IGNoYXJzZXQ9InVzLWFzY2lpIgpDb250ZW50LVRyYW5zZmVy LUVuY29kaW5nOiBxdW90ZWQtcHJpbnRhYmxlCgo8aHRtbCB4bWxuczp2PTNEInVybjpzY2hlbWFz LW1pY3Jvc29mdC1jb206dm1sIiA9CnhtbG5zOm89M0QidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNv bTpvZmZpY2U6b2ZmaWNlIiA9CnhtbG5zOnc9M0QidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpv ZmZpY2U6d29yZCIgPQp4bWxuczptPTNEImh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vb2Zm aWNlLzIwMDQvMTIvb21tbCIgPQp4bWxucz0zRCJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRt bDQwIj48aGVhZD48bWV0YSA9Cmh0dHAtZXF1aXY9M0RDb250ZW50LVR5cGUgY29udGVudD0zRCJ0 ZXh0L2h0bWw7ID0KY2hhcnNldD0zRHVzLWFzY2lpIj48bWV0YSBuYW1lPTNER2VuZXJhdG9yIGNv bnRlbnQ9M0QiTWljcm9zb2Z0IFdvcmQgMTUgPQooZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwh LS0KLyogRm9udCBEZWZpbml0aW9ucyAqLwpAZm9udC1mYWNlCgl7Zm9udC1mYW1pbHk6IkNhbWJy aWEgTWF0aCI7CglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30KQGZvbnQtZmFjZQoJe2Zv bnQtZmFtaWx5OkNhbGlicmk7CglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9Ci8qIFN0 eWxlIERlZmluaXRpb25zICovCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3Jt YWwKCXttYXJnaW46MGluOwoJbWFyZ2luLWJvdHRvbTouMDAwMXB0OwoJZm9udC1zaXplOjExLjBw dDsKCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzZXJpZjt9CmE6bGluaywgc3Bhbi5Nc29IeXBlcmxp bmsKCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7Cgljb2xvcjojMDU2M0MxOwoJdGV4dC1kZWNvcmF0 aW9uOnVuZGVybGluZTt9CmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZAoJe21z by1zdHlsZS1wcmlvcml0eTo5OTsKCWNvbG9yOiM5NTRGNzI7Cgl0ZXh0LWRlY29yYXRpb246dW5k ZXJsaW5lO30Kc3Bhbi5FbWFpbFN0eWxlMTcKCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21w b3NlOwoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNlcmlmOwoJY29sb3I6d2luZG93dGV4dDt9Ci5N c29DaHBEZWZhdWx0Cgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7Cglmb250LWZhbWlseToi Q2FsaWJyaSIsc2VyaWY7fQpAcGFnZSBXb3JkU2VjdGlvbjEKCXtzaXplOjguNWluIDExLjBpbjsK CW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9CmRpdi5Xb3JkU2VjdGlvbjEKCXtwYWdl OldvcmRTZWN0aW9uMTt9Ci0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+CjxvOnNo YXBlZGVmYXVsdHMgdjpleHQ9M0QiZWRpdCIgc3BpZG1heD0zRCIxMDI2IiAvPgo8L3htbD48IVtl bmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4KPG86c2hhcGVsYXlvdXQgdjpleHQ9M0Qi ZWRpdCI+CjxvOmlkbWFwIHY6ZXh0PTNEImVkaXQiIGRhdGE9M0QiMSIgLz4KPC9vOnNoYXBlbGF5 b3V0PjwveG1sPjwhW2VuZGlmXS0tPjwvaGVhZD48Ym9keSBsYW5nPTNERU4tVVMgPQpsaW5rPTNE IiMwNTYzQzEiIHZsaW5rPTNEIiM5NTRGNzIiPjxkaXYgY2xhc3M9M0RXb3JkU2VjdGlvbjE+PHAg PQpjbGFzcz0zRE1zb05vcm1hbD5IZWxsbyw8bzpwPjwvbzpwPjwvcD48cCA9CmNsYXNzPTNETXNv Tm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPTNETXNvTm9ybWFsPklzIHRoZXJl IGEgPQp3YXkgdG8gYWRkICYjODIyMDtYZW9uJiM4MjIxOyBvciBhbm90aGVyIGNsYXNzIG9mIENQ VSBUeXBlIHRvIG9WaXJ0PyBXZSA9CmhhdmUgc29tZSB0ZXN0IGhvc3RzLCB3aGljaCB1c2UgYSBj b21ibyBvZiB0aGUgZm9sbG93aW5nIENQVSA9CnR5cGVzOjxvOnA+PC9vOnA+PC9wPjxwIGNsYXNz PTNETXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwID0KY2xhc3M9M0RNc29Ob3JtYWw+ WGVvbiBMNTQyMDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPTNETXNvTm9ybWFsPlhlb24gPQpFNTQz MDxvOnA+PC9vOnA+PC9wPjxwIGNsYXNzPTNETXNvTm9ybWFsPlhlb24gRTU0MjA8bzpwPjwvbzpw PjwvcD48cCA9CmNsYXNzPTNETXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNz PTNETXNvTm9ybWFsPlRoZSBvbmx5IHR3byA9CkNQVSBUeXBlcyB0aGF0IHdpbGwgd29yayBpbiBv VmlydCBhcmUgQ29ucm9lICZhbXA7IFBlbnJ5bi4gSW5zaWRlIG9mIGEgPQpWTSwgaXQgcmVwb3J0 cyAmIzgyMjA7Q29yZSAyIER1byYjODIyMTsuPG86cD48L286cD48L3A+PHAgPQpjbGFzcz0zRE1z b05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz0zRE1zb05vcm1hbD5Ib3N0ID0K cmVwb3J0czo8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz0zRE1zb05vcm1hbD5tb2RlbCA9Cm5hbWUm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgOiBJbnRlbChSKSBYZW9uKFIpID0KQ1BVJm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 ID0KRTU0MzAmbmJzcDsgQCAyLjY2R0h6PG86cD48L286cD48L3A+PHAgPQpjbGFzcz0zRE1zb05v cm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCA9CmNsYXNzPTNETXNvTm9ybWFsPjxvOnA+Jm5i c3A7PC9vOnA+PC9wPjxwIGNsYXNzPTNETXNvTm9ybWFsPlZNID0KcmVwb3J0czo8bzpwPjwvbzpw PjwvcD48cCBjbGFzcz0zRE1zb05vcm1hbD5tb2RlbCA9Cm5hbWUmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsgOiBJbnRlbCBDb3JlIDIgRHVvIFA5eHh4IChQZW5yeW4gPQpDbGFzcyBDb3Jl IDIpPG86cD48L286cD48L3A+PHAgY2xhc3M9M0RNc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48 L3A+PHAgPQpjbGFzcz0zRE1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48cCA9CmNsYXNz PTNETXNvTm9ybWFsPi8vPG86cD48L286cD48L3A+PHAgPQpjbGFzcz0zRE1zb05vcm1hbD48bzpw PiZuYnNwOzwvbzpwPjwvcD48cCBjbGFzcz0zRE1zb05vcm1hbD5JcyB0aGVyZSBhID0Kd2F5IHRv IGhhdmUgdGhlIFZNIHJlcG9ydCB0aGUgY29ycmVjdCBDUFU/IEl0IGRvZXNuJiM4MjE3O3QgYXBw ZWFyIHRvID0KY2F1c2UgYW55IHBlcmZvcm1hbmNlIG9yIG90aGVyIGlzc3VlcywgYnV0IHNlZW1z IHRvIGJlIGp1c3QgYSBkaXNwbGF5ID0KaXNzdWUuIE15IGNvbmNlcm4gdGhvdWdoLCBpcyB0aGF0 IHdlIG1heSBub3QgYmUgYWJsZSB0byBhZGQgb3RoZXIgPQpzZXJ2ZXJzIHdpdGggZGlmZmVyZW50 IEludGVscyB0byB0aGUgc2FtZSBjbHVzdGVyLCBmb3IgZXhhbXBsZSwgbmV3ID0KaG9zdHMgd2l0 aCBFNS1YWFhYIG9yIEUzLVhYWFggcHJvY2Vzc29ycy4gQ2FuIHNvbWVvbmUgY29uZmlybSB0aGlz ID0Kd291bGRuJiM4MjE3O3QgYmUgYW4gaXNzdWU/PG86cD48L286cD48L3A+PHAgPQpjbGFzcz0z RE1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48L2Rpdj48L2JvZHk+PC9odG1sPgotLS0t LS09X05leHRQYXJ0XzAwMF8wMjc2XzAxRDAxQzQ4Ljc5MDc5RUYwLS0K --===============5317796433622563414==-- From iheim at redhat.com Sat Dec 20 16:24:56 2014 Content-Type: multipart/mixed; boundary="===============3958796258938787627==" MIME-Version: 1.0 From: Itamar Heim To: users at ovirt.org Subject: Re: [ovirt-users] CPU Type Date: Sat, 20 Dec 2014 23:24:47 +0200 Message-ID: <5495E91F.600@redhat.com> In-Reply-To: BLU406-EAS166D5FA4E511725BD4807A98D680@phx.gbl --===============3958796258938787627== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 12/20/2014 06:31 PM, Brent Hartzell wrote: > Hello, > > Is there a way to add =E2=80=9CXeon=E2=80=9D or another class of CPU Type= to oVirt? We > have some test hosts, which use a combo of the following CPU types: > > Xeon L5420 > > Xeon E5430 > > Xeon E5420 > > The only two CPU Types that will work in oVirt are Conroe & Penryn. > Inside of a VM, it reports =E2=80=9CCore 2 Duo=E2=80=9D. > > Host reports: > > model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz > > VM reports: > > model name : Intel Core 2 Duo P9xxx (Penryn Class Core 2) > > // > > Is there a way to have the VM report the correct CPU? It doesn=E2=80=99t = appear > to cause any performance or other issues, but seems to be just a display > issue. My concern though, is that we may not be able to add other > servers with different Intels to the same cluster, for example, new > hosts with E5-XXXX or E3-XXXX processors. Can someone confirm this > wouldn=E2=80=99t be an issue? > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > you can set the VM to use the host cpu (it won't be migratable, but you = can check if it makes any difference before checking other alternatives) --===============3958796258938787627==--