<div dir="ltr"><div>the second one I am not so sure if it is an bug or a feature?<br></div><div>The numa menu is grayed if the VM is HA.<br></div><div>If one remove the HA and force set VM to run on single node without migration flag, then numa flag is editable so you can change to "interleave" mode.<br><br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 20, 2014 at 2:23 PM, Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><p dir="ltr"><br>
On Oct 20, 2014 8:08 AM, Arman Khalatyan <<a href="mailto:arm2arm@gmail.com" target="_blank">arm2arm@gmail.com</a>> wrote:<br>
><br>
> I did not play anything. I had before Ovirt 3.4.4 up and running.<br>
> After upgrade I got 2 problems:<br>
> 1) disk profiles are empty<br>
> 2) numa box by default is preferred- grayed.<br>
> a.</p>
</span><p dir="ltr">Then please open an urgent bug. Well. Two. One for each.</p><div class="HOEnZb"><div class="h5">
<p dir="ltr">><br>
> On Mon, Oct 20, 2014 at 1:42 PM, Itamar Heim <<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a>> wrote:<br>
>><br>
>> On 10/20/2014 05:56 AM, Arman Khalatyan wrote:<br>
>>><br>
>>> My bad!!<br>
>>> False Alarm.everything is working after some massaging:)<br>
>>> 1) start VM get error: error NUMA memory tuning in 'preferred' mode only<br>
>>> supports single node<br>
>>> 2) stop VM edit properties:<br>
>>> 2.a)- edit->host->Start Running on->specific host<br>
>>> 2.b)- edit->host->Migration options->do not allow migration<br>
>>> 2.c)- edit->host->ConfigureNuma->tune mode->interleave<br>
>>> Run VM and enjoy.<br>
>><br>
>><br>
>> but did you play with the numa definition or this happened on its own as part of the upgrade?<br>
>><br>
>>> done!<br>
>>><br>
>>><br>
>>> On Mon, Oct 20, 2014 at 11:44 AM, Arman Khalatyan <<a href="mailto:arm2arm@gmail.com" target="_blank">arm2arm@gmail.com</a><br>
>>> <mailto:<a href="mailto:arm2arm@gmail.com" target="_blank">arm2arm@gmail.com</a>>> wrote:<br>
>>><br>
>>> My upgrade went well no problems.<br>
>>> Unfortuneatly I am not able to run any VM on Intel Hosts.<br>
>>> It throws an error: Exit message: internal error internal error NUMA<br>
>>> memory tuning in 'preferred' mode only supports single node.<br>
>>> I cannot edit numa menu it is disabled on the VM.<br>
>>> thanks,<br>
>>> Arman.<br>
>>><br>
>>><br>
>>> On Mon, Oct 20, 2014 at 10:50 AM, Sandro Bonazzola<br>
>>> <<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a> <mailto:<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>>> wrote:<br>
>>><br>
>>> Il 20/10/2014 10:13, Tiemen Ruiten ha scritto:<br>
>>> > Hello,<br>
>>> ><br>
>>> > Last week I upgraded to 3.5 and on the engine side everything went absolutely fine. Now I'm wondering what to do about my hosts (full CentOS 6<br>
>>> > installs). Is the upgrade something the engine takes care of when I set the compatibility version to 3.5? Or should I install the ovirt-release35 rpm<br>
>>> > and run yum update on all hosts?<br>
>>> ><br>
>>> > Should I expect impact on running VM's, eg. from restarting vdsm?<br>
>>><br>
>>><br>
>>> Looks like we have a documentation gap here.<br>
>>> I tried to search the oVirt site for pointing you to a section<br>
>>> describing how to upgrade hosts but did not found one.<br>
>>><br>
>>> I think that we need to finish<br>
>>> <a href="http://www.ovirt.org/DraftInstallationGuide" target="_blank">http://www.ovirt.org/DraftInstallationGuide</a><br>
>>> and probably prepare an upgrade guide too.<br>
>>><br>
>>> You'll need to install the ovirt-release35 rpm on your hosts<br>
>>> since the engine is not able to add the new repository (yet?<br>
>>> maybe an RFE on this should<br>
>>> be filled for easing the upgrade process of the hosts).<br>
>>><br>
>>> ><br>
>>> > On 20 October 2014 08:48, Sandro Bonazzola<br>
>>> <<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a> <mailto:<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>><br>
>>> <mailto:<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a> <mailto:<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>>>> wrote:<br>
>>> ><br>
>>> > Il 19/10/2014 16:53, Daniel Helgenberger ha scritto:<br>
>>> > > Congratulations! Hope you could get your party.<br>
>>> > ><br>
>>> > > Sandro, as I know you always like to hear things like this:<br>
>>> > > I just upgraded my oVirt 3.4.4 installation to 3.5 and<br>
>>> everything went<br>
>>> > > really well (apart from some package siging / deps; but<br>
>>> these are really<br>
>>> > > not your issues).<br>
>>> ><br>
>>> > I really like when someone report everything goes fine :-)<br>
>>> ><br>
>>> > ><br>
>>> > > Tomorrow I start checking out the new stuff.<br>
>>> > ><br>
>>> > > Thank you! I really appreciate the work you do.<br>
>>> > ><br>
>>> > > Daniel<br>
>>> > ><br>
>>> > > On 17.10.2014 14:46, Sandro Bonazzola wrote:<br>
>>> > >> The oVirt Project is pleased to announce the general<br>
>>> availability of its sixth formal release, oVirt 3.5, as of<br>
>>> October 17, 2014.<br>
>>> > >><br>
>>> > >> oVirt is an open source alternative to VMware vSphere,<br>
>>> and provides an excellent KVM management interface for<br>
>>> multi-node virtualization. oVirt is<br>
>>> > >> available now for Fedora 19, Fedora 20, Red Hat<br>
>>> Enterprise Linux 6.5, and CentOS 6.5 (or similar) and allow you<br>
>>> to use Red Hat Enterprise Linux<br>
>>> > 7 and<br>
>>> > >> CentOS 7 too as node and for running Hosted Engine.<br>
>>> > >><br>
>>> > >> New features include:<br>
>>> > >><br>
>>> > >> Live Merge<br>
>>> > >> ----------<br>
>>> > >> If an image has one or more snapshots, oVirt 3.5's<br>
>>> merge command will combine the data of one volume into another.<br>
>>> Live merges can be performed<br>
>>> > with<br>
>>> > >> data is pulled from one snapshot into another<br>
>>> snapshot. The engine can merge multiple disks at the same time<br>
>>> and each merge can independently<br>
>>> > fail or<br>
>>> > >> succeed in each operation.<br>
>>> > >> Import Storage Domain<br>
>>> > >><br>
>>> > >> This latest release expands oVirt's feature of<br>
>>> importing ISOs and exporting storage domains to expand support<br>
>>> for importing an existing data<br>
>>> > storage<br>
>>> > >> domain. Based on information stored in the storage<br>
>>> domain, oVirt can revive entities such as disks, virtual<br>
>>> machines, and templates in the setup of<br>
>>> > >> any data center to which the storage domain is attached.<br>
>>> > >><br>
>>> > >><br>
>>> > >> Advanced Foreman Integration<br>
>>> > >> ----------------------------<br>
>>> > >> oVirt 3.5 adds the capability to provision and add<br>
>>> hypervisors to oVirt from bare metal. Foreman is a complete<br>
>>> lifecycle management tool for<br>
>>> > physical<br>
>>> > >> and virtual servers. Through deep integration with<br>
>>> configuration management, DHCP, DNS, TFTP, and PXE-based<br>
>>> unattended installations, Foreman<br>
>>> > manages<br>
>>> > >> every stage of the lifecycle of your physical or<br>
>>> virtual servers. Integrating Foreman with oVirt helps add<br>
>>> hypervisor hosts managed by Foreman<br>
>>> > to the<br>
>>> > >> oVirt engine.<br>
>>> > >><br>
>>> > >><br>
>>> > >> Enhanced Authentication, Authorization and Accounting<br>
>>> Support<br>
>>> > >><br>
>>> -------------------------------------------------------------<br>
>>> > >> A new architecture has been built for oVirt 3.5's<br>
>>> authentication, authorization and accounting (AAA) system. The<br>
>>> enhancements will provide a clear<br>
>>> > >> separation of authentication from authorization and<br>
>>> provide a developer API to develop custom extensions for<br>
>>> authentication and authorization.<br>
>>> > >><br>
>>> > >><br>
>>> > >> New PatternFly Interface<br>
>>> > >> ------------------------<br>
>>> > >> oVirt 3.5 will have a new look and feel, using<br>
>>> PatternFly, the open interface project. The new look and feel<br>
>>> aims to maintain the colors and spirit<br>
>>> > >> associated with oVirt, while updating it with a new,<br>
>>> modern, sleek, and minimal look. The minimal design allows<br>
>>> complex screens to look cleaner and<br>
>>> > >> airier, and lets the user focus on the data and the<br>
>>> tasks by removing all extraneous visual elements.<br>
>>> > >><br>
>>> > >><br>
>>> > >> Advanced Scheduling with Optaplanner<br>
>>> > >> ------------------------------------<br>
>>> > >> The Optaplanner is a new service that takes a snapshot<br>
>>> of a cluster (a list of hosts and VMs) and computes an optimized<br>
>>> VM-to-Host assignment<br>
>>> > >> solution. Optimization will is done on per Cluster<br>
>>> basis. The administrator can use this information as a hint to<br>
>>> tweak the cluster to better<br>
>>> > utilize<br>
>>> > >> resources.<br>
>>> > >><br>
>>> > >><br>
>>> > >><br>
>>> > >> This release of oVirt also includes numerous bug<br>
>>> fixes. See the release notes [1] for a complete list of the new<br>
>>> features and bugs fixed.<br>
>>> > >><br>
>>> > >> A new repository has been created and will be<br>
>>> automatically enabled by installing / upgrading ovirt-release35<br>
>>> package.<br>
>>> > >> See release notes page for further instructions about<br>
>>> install / upgrade.<br>
>>> > >><br>
>>> > >> A new oVirt Live iso is also available [2] and a new<br>
>>> oVirt Node iso will be available soon.<br>
>>> > >><br>
>>> > >> [1] <a href="http://www.ovirt.org/OVirt_3.5_Release_Notes" target="_blank">http://www.ovirt.org/OVirt_3.5_Release_Notes</a><br>
>>> > >> [2]<br>
>>> <a href="http://resources.ovirt.org/pub/ovirt-3.5/iso/ovirt-live-el6-3.5.0.iso" target="_blank">http://resources.ovirt.org/pub/ovirt-3.5/iso/ovirt-live-el6-3.5.0.iso</a><br>
>>> > >><br>
>>> > ><br>
>>> ><br>
>>> ><br>
>>> > --<br>
>>> > Sandro Bonazzola<br>
>>> > Better technology. Faster innovation. Powered by<br>
>>> community collaboration.<br>
>>> > See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a> <<a href="http://redhat.com" target="_blank">http://redhat.com</a>><br>
>>> <<a href="http://redhat.com" target="_blank">http://redhat.com</a>><br>
>>> > _______________________________________________<br>
>>> > Users mailing list<br>
>>> > <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> <mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>><br>
>>> <mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> <mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>>><br>
>>> > <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > --<br>
>>> > Tiemen Ruiten<br>
>>> > Systems Engineer<br>
>>> > R&D Media<br>
>>><br>
>>><br>
>>> --<br>
>>> Sandro Bonazzola<br>
>>> Better technology. Faster innovation. Powered by community<br>
>>> collaboration.<br>
>>> See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a> <<a href="http://redhat.com" target="_blank">http://redhat.com</a>><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> <mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>><br>
>>> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
>>> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
>>><br>
>><br>
><br>
</p>
</div></div></blockquote></div><br></div>