Re: [ovirt-users] Upgrade to 3.5 issues, vm cannot be started
It 's a NUMA problem. It 's like : http://lists.ovirt.org/pipermail/users/2014-September/027787.html http://lists.ovirt.org/pipermail/users/2014-September/027891.html Is it possible to change the default NUMA mode to interleave in GUI ? 2014-11-11 10:58 GMT+01:00 James James jre...@gmail.com: Hi, today I've decided to upgrade my 3.4 Ovirt cluster to 3.5/ The engine migration was OK. Everything was good .. after I want upgraded the node .. I've installed the rpm on the node and follow : http://www.ovirt.org/OVirt_3.5_Release_Notes#Install_.2F_Upgrade_from_Previous_Versions . Now my vms cannot be started. I've got this error message : 2014-11-11 10:49:37,305 WARN [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-8-thread-13) CanDoAction of action RunVm failed. Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS 2014-11-11 10:49:37,307 INFO [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-8-thread-13) Lock freed to object EngineLock [exclusiveLocks= key: 0fdea856-9aec-4300-8d88-4cfd330cf4ff value: VM , sharedLocks= ] There is a full log in attachment .. Any help will be appreciated ... James ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade to 3.5 issues, vm cannot be started
On Tue, Nov 11, 2014 at 11:30 AM, James James jre...@gmail.com wrote: It 's a NUMA problem. It 's like : http://lists.ovirt.org/pipermail/users/2014-September/027787.html http://lists.ovirt.org/pipermail/users/2014-September/027891.html Is it possible to change the default NUMA mode to interleave in GUI ? Gilad, from your latest answer to the same referred thread, here: http://lists.ovirt.org/pipermail/users/2014-September/027891.html I sorted out that it was a problem of mine, coming from a 3.5-rc2 to 3.5-rc3 now it actually seems that it is indeed a regression from 3.4 to 3.5. So I propose to consider something managing this for 3.5.1 so that a user upgrading from 3.4.x to 3.5.1 will not get this kind of nasty problem. Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade to 3.5 issues, vm cannot be started
On 11/11/14 12:37, Gianluca Cecchi wrote: Gilad, from your latest answer to the same referred thread, here: http://lists.ovirt.org/pipermail/users/2014-September/027891.html I sorted out that it was a problem of mine, coming from a 3.5-rc2 to 3.5-rc3 now it actually seems that it is indeed a regression from 3.4 to 3.5. So I propose to consider something managing this for 3.5.1 so that a user upgrading from 3.4.x to 3.5.1 will not get this kind of nasty problem. this is already targeted for 3.5.1 and marked as a blocker: https://bugzilla.redhat.com/show_bug.cgi?id=1157149 But it's still not backported to 3.5 branch HTH -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
