[Engine-devel] oVirt 3.4 test day - PPC support
Hi, I tried to test various engine features related to PPC support, However since I don't have a real Power PC HW I tried using the fake PPC configuration introduced by http://gerrit.ovirt.org/#/c/18718 So I added the following configuration to /etc/vdsm/vdsm.conf on a x86_64 host: fake_kvm_support=true fake_kvm_architecture=ppc64 And indeed it looked successful as you can see below [root@bazulay1 ~]# vdsClient -s 0 getVdsCaps | grep -i cpu cpuCores = '4' cpuFlags = 'powernv,model_POWER7_v2.3' cpuModel = 'POWER 7 (fake)' cpuSockets = '1' cpuSpeed = '3401.000' cpuThreads = '8' However after creating the appropriate cluster: CPU Architecture = ppc64 CPU name = IBM POWER 7* (meaning I tried all IBM POWER 7... cpus) Adding the host always ended in non operational status with the error: "Host bazulay1 has architecture x86_64 and cannot join Cluster TESTDAY-CLUSTER which has architecture ppc64." Thanks Barak Azulay
Maybe this is a problem with ovirt-host-deploy, it must be configured to avoid overwriting your vdsm.conf file. There are instructions in the wiki: http://www.ovirt.org/Features/Vdsm_for_PPC64#Testing_the_PPC64_support ________________________________________ De: Barak Azulay [bazulay@redhat.com] Enviado: quinta-feira, 23 de janeiro de 2014 17:29 Para: Vitor de Lima; Roy Golan; Michal Skrivanek Cc: VDSM Project Development; engine-devel Assunto: oVirt 3.4 test day - PPC support Hi, I tried to test various engine features related to PPC support, However since I don't have a real Power PC HW I tried using the fake PPC configuration introduced by http://gerrit.ovirt.org/#/c/18718 So I added the following configuration to /etc/vdsm/vdsm.conf on a x86_64 host: fake_kvm_support=true fake_kvm_architecture=ppc64 And indeed it looked successful as you can see below [root@bazulay1 ~]# vdsClient -s 0 getVdsCaps | grep -i cpu cpuCores = '4' cpuFlags = 'powernv,model_POWER7_v2.3' cpuModel = 'POWER 7 (fake)' cpuSockets = '1' cpuSpeed = '3401.000' cpuThreads = '8' However after creating the appropriate cluster: CPU Architecture = ppc64 CPU name = IBM POWER 7* (meaning I tried all IBM POWER 7... cpus) Adding the host always ended in non operational status with the error: "Host bazulay1 has architecture x86_64 and cannot join Cluster TESTDAY-CLUSTER which has architecture ppc64." Thanks Barak Azulay
Yes, sounds like the overriding of vdsm.conf is an issue that we need to avoid what I wonder is that it is not a regression, old versions of vdsm also overwrited the vdsm.conf file during deploy, so how is it harming us only now? please open a bug on the overwriting issue Thanks. Yaniv Bronhaim. ----- Original Message -----
From: "Vitor de Lima" <vitor.lima@eldorado.org.br> To: "Barak Azulay" <bazulay@redhat.com>, "Roy Golan" <rgolan@redhat.com>, "Michal Skrivanek" <mskrivan@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org>, "VDSM Project Development" <vdsm-devel@lists.fedorahosted.org> Sent: Friday, January 24, 2014 4:52:50 PM Subject: [Engine-devel] RES: oVirt 3.4 test day - PPC support
Maybe this is a problem with ovirt-host-deploy, it must be configured to avoid overwriting your vdsm.conf file. There are instructions in the wiki:
http://www.ovirt.org/Features/Vdsm_for_PPC64#Testing_the_PPC64_support
________________________________________ De: Barak Azulay [bazulay@redhat.com] Enviado: quinta-feira, 23 de janeiro de 2014 17:29 Para: Vitor de Lima; Roy Golan; Michal Skrivanek Cc: VDSM Project Development; engine-devel Assunto: oVirt 3.4 test day - PPC support
Hi,
I tried to test various engine features related to PPC support, However since I don't have a real Power PC HW I tried using the fake PPC configuration introduced by http://gerrit.ovirt.org/#/c/18718
So I added the following configuration to /etc/vdsm/vdsm.conf on a x86_64 host:
fake_kvm_support=true fake_kvm_architecture=ppc64
And indeed it looked successful as you can see below
[root@bazulay1 ~]# vdsClient -s 0 getVdsCaps | grep -i cpu cpuCores = '4' cpuFlags = 'powernv,model_POWER7_v2.3' cpuModel = 'POWER 7 (fake)' cpuSockets = '1' cpuSpeed = '3401.000' cpuThreads = '8'
However after creating the appropriate cluster: CPU Architecture = ppc64 CPU name = IBM POWER 7* (meaning I tried all IBM POWER 7... cpus)
Adding the host always ended in non operational status with the error:
"Host bazulay1 has architecture x86_64 and cannot join Cluster TESTDAY-CLUSTER which has architecture ppc64."
Thanks Barak Azulay _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On Sun, Jan 26, 2014 at 04:53:08AM -0500, Yaniv Bronheim wrote:
Yes, sounds like the overriding of vdsm.conf is an issue that we need to avoid what I wonder is that it is not a regression, old versions of vdsm also overwrited the vdsm.conf file during deploy, so how is it harming us only now?
please open a bug on the overwriting issue
I do not think a bug is warrented. We wanted that a remote-controlled installation of a host would get it into a known good state. Needing to faking the hardware is a special case, not the rule, and for it, https://github.com/oVirt/ovirt-host-deploy/blob/master/README#L52 VDSM/configOverride=bool:False was devised.
participants (4)
-
Barak Azulay -
Dan Kenigsberg -
Vitor de Lima -
Yaniv Bronheim