[ovirt-devel] oVirt 3.5 test day 2 results - NUMA

2014-07-30 Thread Martin Perina
Hi, I tried to test NUMA feature. Unfortunately the feature has no UI yet, so I tested just db content and REST API calls: 1) Two NUMA hosts added to 3.5 cluster with shared NFS storage using webadmin 2) Database: a) Both hosts have is_numa_supported=true, auto_numa_balancing=1 in

Re: [ovirt-devel] oVirt 3.5 test day 2 results

2014-07-30 Thread Simone Tiraboschi
Thanks Francesco, some comments between the lines. - Original Message - From: Francesco Romani from...@redhat.com To: users us...@ovirt.org, devel@ovirt.org Sent: Tuesday, July 29, 2014 5:42:06 PM Subject: [ovirt-devel] oVirt 3.5 test day 2 results Hi everyone, Hi tested again

[ovirt-devel] oVirt 3.5 test day 2 results - spice-html5 button to show debug console/output window - 1108599

2014-07-30 Thread Simone Tiraboschi
Hi, I had to test the presence of a button to show the debug output for the spice-html5 console. I created a setup with two host (the first with the engine in all-in-one fashion and the second with just a websocket proxy). I launched a VM and I tried to open the spice-html5 console. The new

[ovirt-devel] oVirt 3.5 Test day 2 results

2014-07-29 Thread Tomas Jelinek
Hey, I have tested the instance type feature and found 2 issues: instance types: does not remember advanced/basic settings from previously opened dialog: https://bugzilla.redhat.com/show_bug.cgi?id=1124254 new Instance type: enable soundcard is not persisted:

[ovirt-devel] oVirt 3.5 test day 2 results

2014-07-29 Thread Francesco Romani
Hi everyone, Hi tested again http://www.ovirt.org/Features/WebSocketProxy_on_a_separate_host What happened on tast day 1 * found minor packaging issues * stopped earlier facing SSL issues, had a followup the day after an managed to have the feature working. This time things got better, and

[ovirt-devel] oVirt 3.5 test day 2 results

2014-07-29 Thread Greg Sheremeta
I once again tested 1091863 Accept vlan devices identified by any name Steps to Reproduce: - Change Host to maintenance mode. - Add a vlan with alternative name to the Host: # ip link add dev eth1.myvlan10 link eth1 name eth1.myvlan10 type vlan id 10 - Activate the Host. It works perfectly.