Re: [ovirt-users] Windows Product Activation

2016-12-22 Thread Nicolas Ecarnot 

Le 22/12/2016 à 22:06, Michal Skrivanek a écrit :

I read more about this WPA issue, and I also checked : all our
licences are MAK_B kind, which I read everywhere that they should
not induce such WPA trouble, once they are correctly registered
(which I obviously take care of). I also read the list of
components that are checked to create a hashed key linked to the
licence. As you wrote, changing to many components is triggering a
validity break.

Knowing this, may I ask you to comment on the promising "VM Custom
Serial Number" Alex was talking about : it sounded perfect, but
eventually not enough to cope with the hardware change?


That’s what it is for. Does it not work for this case?


I still have additional tests to do to validate it.
Moreover, as this WPA issue is triggered after 30 days, this kind of
tests is taking quite a lot of time.

Stay tuned.

PS : As usual, I'm very thankful to all who replied, and more generally
to everyone on this mailing list for your help throughout the year.

--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows Product Activation

2016-12-22 Thread Michal Skrivanek 

> On 22 Dec 2016, at 22:02, Nicolas Ecarnot  wrote:
> 
> Le 22/12/2016 à 17:26, Yaniv Kaul a écrit :
>> Windows activation, at least for 2008 and below, depend on enough hardware 
>> changes to happen. Each HW (of non-pluggable devices) change is a single 
>> 'penalty' point - except for NIC (based on MAC address) which is more. 4 or 
>> so points - and it requires re-activation. This does not apply to KMS 
>> licenses.
>> 
>> So unless you drastically change the hardware, you should be safe.
>> Y.
> Hello Yaniv,
> 
> When migrating, these VMs can jump from a recent hardware host to an older 
> one, with a different generation CPU (though of the same intel kind).
> 
> I read more about this WPA issue, and I also checked : all our licences are 
> MAK_B kind, which I read everywhere that they should not induce such WPA 
> trouble, once they are correctly registered (which I obviously take care of).
> I also read the list of components that are checked to create a hashed key 
> linked to the licence.
> As you wrote, changing to many components is triggering a validity break.
> 
> Knowing this, may I ask you to comment on the promising "VM Custom Serial 
> Number" Alex was talking about : it sounded perfect, but eventually not 
> enough to cope with the hardware change?

That’s what it is for.
Does it not work for this case?
There was a report of certain bits in cpuid being exposed from hypervisor 
without emulation, but that was quite obscure and IIRC not related to Windows 
licenses

> 
> -- 
> Nicolas ECARNOT
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows Product Activation

2016-12-22 Thread Nicolas Ecarnot 

Le 22/12/2016 à 17:26, Yaniv Kaul a écrit :
Windows activation, at least for 2008 and below, depend on enough 
hardware changes to happen. Each HW (of non-pluggable devices) change 
is a single 'penalty' point - except for NIC (based on MAC address) 
which is more. 4 or so points - and it requires re-activation. This 
does not apply to KMS licenses.


So unless you drastically change the hardware, you should be safe.
Y.

Hello Yaniv,

When migrating, these VMs can jump from a recent hardware host to an 
older one, with a different generation CPU (though of the same intel kind).


I read more about this WPA issue, and I also checked : all our licences 
are MAK_B kind, which I read everywhere that they should not induce such 
WPA trouble, once they are correctly registered (which I obviously take 
care of).
I also read the list of components that are checked to create a hashed 
key linked to the licence.

As you wrote, changing to many components is triggering a validity break.

Knowing this, may I ask you to comment on the promising "VM Custom 
Serial Number" Alex was talking about : it sounded perfect, but 
eventually not enough to cope with the hardware change?


--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Allocating only "x" amount of physical memory to hypervisor node

2016-12-22 Thread shishir praksh 
The requirement is to use ovirt hypervisor for one application along with vdsm. 
I want to only "x" amount of memory should be visible/allocated to hypervisor 
for hosting the VMs rest I will use for my application hosted on same physical 
box.
pointers will be appreciated 


Thanks

Shishir-
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [HEADS UP] CentOS 7.3 is rolling out, need qemu-kvm-ev 2.6

2016-12-22 Thread Gianluca Cecchi 
On Mon, Dec 12, 2016 at 1:49 PM, Sandro Bonazzola 
wrote:

> Hi,
> as you probably noticed, CentOS 7.3 is rolling out right now and will be
> announced pretty soon.
> Please note that due to new libvirt shipped within CentOS 7.3, it is
> required to update qemu-kvm-ev to 2.6 at the same time.
>
> If you're using CentOS Virt SIG rpms / repos for oVirt this should happen
> automatically.
> If you're using only ovirt repositories be sure to have qemu-kvm-ev 2.6 if
> you update to CentOS 7.3.
>
> In terms of ovirt repositories, qemu-kvm-ev 2.6 is available right now in
> ovirt-master-snapshot-static, ovirt-4.0-snapshot-static, and ovirt-4.0-pre
> (contains 4.0.6 RC4 rpms going to be announced in a few minutes.)
>
> Thanks,
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>


Hello,
I start again from the initial post.
There is still something that I miss on this.
I currently have a host in oVirt 4.0.5 and in CentOS 7.2 (last update run
on mid November)
What are the steps I should run to keep current my oVirt host os now?

If I now run

[root@ractor ~]# yum update
Loaded plugins: fastestmirror, langpacks
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: ba.mirror.garr.it
 * extras: artfiles.org
 * ovirt-3.6: ftp.nluug.nl
 * ovirt-3.6-epel: epel.besthosting.ua
 * ovirt-4.0: ftp.nluug.nl
 * ovirt-4.0-epel: epel.besthosting.ua
 * updates: ba.mirror.garr.it
Resolving Dependencies

and relevant updates proposed are

Installing:
 kernelx86_64   3.10.0-514.2.2.el7
   updates   37 M

. . .

Updating:

. . .

 centos-releasex86_64   7-3.1611.el7.centos
  base  23 k

. . .

 libvirt   x86_64   2.0.0-10.el7_3.2
   updates  138 k
 libvirt-clientx86_64   2.0.0-10.el7_3.2
   updates  4.3 M
 libvirt-daemonx86_64   2.0.0-10.el7_3.2
   updates  720 k
 libvirt-daemon-config-network x86_64   2.0.0-10.el7_3.2
   updates  139 k
 libvirt-daemon-config-nwfilterx86_64   2.0.0-10.el7_3.2
   updates  141 k
 libvirt-daemon-driver-interface   x86_64   2.0.0-10.el7_3.2
   updates  181 k
 libvirt-daemon-driver-lxc x86_64   2.0.0-10.el7_3.2
   updates  803 k
 libvirt-daemon-driver-network x86_64   2.0.0-10.el7_3.2
   updates  337 k
 libvirt-daemon-driver-nodedev x86_64   2.0.0-10.el7_3.2
   updates  181 k
 libvirt-daemon-driver-nwfilterx86_64   2.0.0-10.el7_3.2
   updates  205 k
 libvirt-daemon-driver-qemux86_64   2.0.0-10.el7_3.2
   updates  615 k
 libvirt-daemon-driver-secret  x86_64   2.0.0-10.el7_3.2
   updates  171 k
 libvirt-daemon-driver-storage x86_64   2.0.0-10.el7_3.2
   updates  375 k
 libvirt-daemon-kvmx86_64   2.0.0-10.el7_3.2
   updates  137 k
 libvirt-lock-sanlock  x86_64   2.0.0-10.el7_3.2
   updates  186 k
 libvirt-pythonx86_64   2.0.0-2.el7
  base 321 k

. . .

 vdsm  x86_64   4.18.15.3-1.el7.centos
   ovirt-4.0688 k
 vdsm-api  noarch   4.18.15.3-1.el7.centos
   ovirt-4.0 53 k
 vdsm-cli  noarch   4.18.15.3-1.el7.centos
   ovirt-4.0 67 k
 vdsm-hook-vmfex-dev   noarch   4.18.15.3-1.el7.centos
   ovirt-4.06.6 k
 vdsm-infranoarch   4.18.15.3-1.el7.centos
   ovirt-4.0 12 k
 vdsm-jsonrpc  noarch   4.18.15.3-1.el7.centos
   ovirt-4.0 25 k
 vdsm-python   noarch   4.18.15.3-1.el7.centos
   ovirt-4.0602 k
 vdsm-xmlrpc   noarch   4.18.15.3-1.el7.centos
   ovirt-4.0 25 k
 vdsm-yajsonrpcnoarch   4.18.15.3-1.el7.centos
   ovirt-4.0 27 k

. . .

No qemu related update proposed.

The same if I run a "yum clean all" before.

My current situation about it:

[root@ractor ~]# rpm -qa|grep ^qemu
qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64
qemu-img-ev-2.3.0-31.el7.16.1.x86_64
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64
qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64
[root@ractor ~]#

Does this mean I'm going to have problems still, because of libvirt version
provided by CentOS 7.3 and qemu-kvm-ev 2.3?
Also, what are exactly te problems we are speaking about?
Do I need to follow what suggested in one of the threads's mails

"
You can enable CentOS Virt

Re: [ovirt-users] Windows Product Activation

2016-12-22 Thread Yaniv Kaul 
Windows activation, at least for 2008 and below, depend on enough hardware
changes to happen. Each HW (of non-pluggable devices) change is a single
'penalty' point - except for NIC (based on MAC address) which is more. 4 or
so points - and it requires re-activation. This does not apply to KMS
licenses.

So unless you drastically change the hardware, you should be safe.
Y.


On Wed, Dec 21, 2016 at 3:27 PM, Nicolas Ecarnot 
wrote:

> Hello,
>
> Most of our virtual machines are Linux, but an increasing number of
> windows VMs are being integrated into our oVirt DCs.
>
> We bought tons of windows server licences, and successfully activated them.
>
> Due to how Windows Product Activation is working, when a windows VM is
> migrating from a host to another, this product activation is reset,
> launching a 30 days countdown to auto-shutdown.
>
> According to this old page :
>
> https://mazimi.wordpress.com/2007/07/11/getting-around-windo
> ws-activation-when-virtualizing/
>
> and what I can read in microsoft's 2012 server documentations, I then can
> re-activate it twice during the next 90 days.
>
> Assuming I *want* to have *no* control upon the location of the VMs
> amongst their hosts (I want them to fly freely, confident in the lovely
> auto-balance scheduler), I understand all this is not the way to go.
>
> At present, we have 2003, 2008 and 2012 server editions.
> the only things I can read about windows 2012 server is related to the
> commercial aspects (standard licence = 2 VMs, datacenter licencce =
> infinite # of VMs), but not about this Windows Product Activation trouble.
>
> How do you deal with this?
> Is there a special licence type or something dedicated that would prevent
> such an uncomfortable situation? (Christmas is near, I favor soft terms.)
>
> Regards.
>
> --
> Nicolas ECARNOT
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Fwd: [Call for feedback] anybody gave 4.1 beta a try?

2016-12-22 Thread Yaniv Kaul 
On Thu, Dec 22, 2016 at 12:50 PM, Nathanaël Blanchet 
wrote:

> Hi,
> sebool unconfigured module prevents vdsm from starting:
>

We always run with selinux. What's the reason for disabling it?
Y.


[root@gaua2 network-scripts]# vdsm-tool configure --force
>
> Checking configuration status...
>
> Current revision of multipath.conf detected, preserving
> libvirt is already configured for vdsm
> SUCCESS: ssl configured to true. No conflicts
>
> Running configure...
> libsepol.context_from_record: type ovirt_vmconsole_host_port_t is not
> defined (No such file or directory).
> libsepol.context_from_record: could not create context structure (Invalid
> argument).
> libsepol.port_from_record: could not create port structure for range
> 2223:2223 (tcp) (Invalid argument).
> libsepol.sepol_port_modify: could not load port range 2223 - 2223 (tcp)
> (Invalid argument).
> libsemanage.dbase_policydb_modify: could not modify record value (Invalid
> argument).
> libsemanage.semanage_base_merge_components: could not merge local
> modifications into policy (Invalid argument).
> Traceback (most recent call last):
>   File "/usr/bin/vdsm-tool", line 219, in main
> return tool_command[cmd]["command"](*args)
>   File "/usr/lib/python2.7/site-packages/vdsm/tool/__init__.py", line 38,
> in wrapper
> func(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py", line
> 141, in configure
> _configure(c)
>   File "/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py", line
> 88, in _configure
> getattr(module, 'configure', lambda: None)()
>   File "/usr/lib/python2.7/site-packages/vdsm/tool/configurators/sebool.py",
> line 84, in configure
> _setup_booleans(True)
>   File "/usr/lib/python2.7/site-packages/vdsm/tool/configurators/sebool.py",
> line 57, in _setup_booleans
> sebool_obj.finish()
>   File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 320,
> in finish
> self.commit()
>   File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 310,
> in commit
> rc = semanage_commit(self.sh)
> OSError: [Errno 22] Invalid argument
>
>
> Le 19/12/2016 à 11:55, Maton, Brett a écrit :
>
> I'll give that ago this evening, although that might be related to trying
> to deploy to the host multiple times
>
> On 19 December 2016 at 09:54, Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Mon, Dec 19, 2016 at 10:11 AM, Maton, Brett <
>> mat...@ltresources.co.uk> wrote:
>>
>>> Log from the last deploy attempt attached.
>>>
>>
>> 2016-12-18 12:52:05 DEBUG otopi.plugins.ovirt_host_mgmt.packages.update
>> update.verbose:94 Yum: There are unfinished transactions remaining. You
>> might consider running yum-complete-transaction, or
>> "yum-complete-transaction --cleanup-only" and "yum history redo last",
>> first to finish them. If those don't work you'll have to try
>> removing/installing packages by hand (maybe package-cleanup can help).
>>
>> It seams that you have unfinished yum transactions on your host; can you
>> please check for that and then try redeploying the host?
>>
>>
>>>
>>> On 19 December 2016 at 08:30, Simone Tiraboschi < 
>>> stira...@redhat.com> wrote:
>>>


 On Sat, Dec 17, 2016 at 7:17 PM, Maton, Brett <
 mat...@ltresources.co.uk> wrote:

> I had a mac address conflict so reinstalled ( from scratch ) 4.1 this
> morning, CPU load issue in UI was still there.
>

 We already have an open bug about this:
 
 https://bugzilla.redhat.com/show_bug.cgi?id=1390675
 Thanks for the report.


>
> I can't deploy additional hosts now though due to SSH errors.
>

 Could you please attach host-deploy logs?


>
> Experimenting, I updated the hosted engine this afternoon and the CPU
> load issue seems be have either been fixed or resolved itself.
>
> However, SSH errors deploying additional hosts persists ( I had no
> problem with the previous install on Friday ).
>
> enging.log snippet:
> 2016-12-17 17:09:54,764Z ERROR 
> [org.ovirt.engine.core.uutils.ssh.SSHDialog]
> (org.ovirt.thread.pool-6-thread-26) [b04a9eaf-65b5-4a80-a254-0b29a8fea573]
> SSH error running command r...@host2.example.com:'umask 0077;
> MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XX)";
> trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" >
> /dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x &&
> "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine
> DIALOG/customization=bool:True': Command returned failure code 1
> during SSH session ' r...@host2.example.com'
> 2016-12-17 17:09:54,765Z ERROR 
> [org.ovirt.engine.core.uutils.ssh.SSHDialog]
> (org.ovirt.thread.pool-6-thread-26)

Re: [ovirt-users] Regarding DAS for Shared Storage

2016-12-22 Thread Dan Yasny 
In theory, if you can see the DAS LUN with multipath, you can build the
storage domain as if it's FC. Might need to play with multipath settings to
make sure it's not filtered out.

On Thu, Dec 22, 2016 at 7:11 AM, Fernando Frediani <
fernando.fredi...@upx.com.br> wrote:

> Hello rex.
>
> I have a very similar situation and I'm interested to find out how people
> are doing to use DAS in these types of environments.
>
> Thanks
> Fernando
>
>
> On 22/12/2016 10:07, rex wrote:
>
> Hi,
>
> Have a VRTX Chassis enclosure populated with two Dell PowerEdge M620
> Blades and has a built-in DAS storage. Created a 1 TB Virtual Disk from the
> DAS storage using the Dell iDRAC interface. This block device is accessible
> from the two blades (CentOS 7 OS) like shown below,
>
>  [root@node1 ~]# lsblk /dev/sdc
>
>  NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
>  sdc8:32   0 1024G  0 disk
>
>  [root@node2 ~]# lsblk /dev/sdc
>
>  NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
>  sdc8:32   0 1024G  0 disk
>
>  oVirt rpms has been installed on both the blades with the aim of
> configuring them as oVirt nodes with Live Migration feature. But other than
> the DAS we don't have any storage which can be used as shared storage. So
> can some one please tell me whether the above block disk can be used as a
> shared storage (i.e mounted on the two nodes at the same time) and if it is
> possible how can this be done. Thank you.
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [HEADS UP] CentOS 7.3 is rolling out, need qemu-kvm-ev 2.6

2016-12-22 Thread Paolo Bonzini 


On 22/12/2016 15:29, Michal Skrivanek wrote:
>> it is important for 3.6 and 4.0, but in 4.1 we should not be using any 
>> rhel-6 machine type anymore
>> There is https://bugzilla.redhat.com/show_bug.cgi?id=1402435 for HE which 
>> should be fixed (if real)
> 
> though, the bug opened by Paolo talks about rhel-6.6.0 machine type, but we 
> are using rhel-6.5.0, and then only 7.0,7.2,7.3
> Can you confirm? The report from Juergen indicates 6.5 is broken too

All RHEL-6 machine types are broken in the same way.

Paolo
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [HEADS UP] CentOS 7.3 is rolling out, need qemu-kvm-ev 2.6

2016-12-22 Thread Michal Skrivanek 

> On 22 Dec 2016, at 15:01, Michal Skrivanek  wrote:
> 
> 
>> On 15 Dec 2016, at 16:46, Sandro Bonazzola  wrote:
>> 
>> 
>> 
>> Il 15/Dic/2016 16:17, "InterNetX - Juergen Gotteswinter" 
>>  ha scritto:
>> Am 15.12.2016 um 15:51 schrieb Sandro Bonazzola:
>>> 
>>> 
>>> On Thu, Dec 15, 2016 at 3:02 PM, InterNetX - Juergen Gotteswinter
>>> > wrote:
>>> 
>>>i can confirm that it will break ...
>>> 
>>>Dec 15 14:58:43 vm1 journal: internal error: qemu unexpectedly closed
>>>the monitor: Unexpected error in object_property_find() at
>>>qom/object.c:1003:#0122016-12-15T13:58:43.140073Z qemu-kvm: can't apply
>>>global Opteron_G4-x86_64-cpu.x1apic=off: Property '.x1apic' not found
>>> 
>>> 
>>> Just an heads up that qemu-kvm-ev 2.6 is now
>>> in http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/
>>> 
>> 
>> [16:16:47][root@vm1:/var/log]$rpm -aq |grep qemu-kvm-ev
>> qemu-kvm-ev-2.6.0-27.1.el7.x86_64
>> [16:16:52][root@vm1:/var/log]$
>> 
>> this message is from 2.6
>> 
>> Adding Paolo and Michal.
> 
> it is important for 3.6 and 4.0, but in 4.1 we should not be using any rhel-6 
> machine type anymore
> There is https://bugzilla.redhat.com/show_bug.cgi?id=1402435 for HE which 
> should be fixed (if real)

though, the bug opened by Paolo talks about rhel-6.6.0 machine type, but we are 
using rhel-6.5.0, and then only 7.0,7.2,7.3
Can you confirm? The report from Juergen indicates 6.5 is broken too

> 
>> 
>> 
>> 
>> 
>> 
>>> 
>>> 
>>> 
>>> 
>>>cheers,
>>> 
>>>Juergen
>>> 
>>>Am 13.12.2016 um 10:30 schrieb Ralf Schenk:
 Hello
 
 by browsing the repository on
 http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/
>>> I can't see
 any qemu-kvm-ev-2.6.* RPM.
 
 I think this will break if I update the Ovirt-Hosts...
 
 [root@microcloud21 yum.repos.d]# yum check-update | grep libvirt
 libvirt.x86_64  2.0.0-10.el7_3.2
 updates
 libvirt-client.x86_64   2.0.0-10.el7_3.2
 updates
 libvirt-daemon.x86_64   2.0.0-10.el7_3.2
 updates
 libvirt-daemon-config-network.x86_642.0.0-10.el7_3.2
 updates
 libvirt-daemon-config-nwfilter.x86_64   2.0.0-10.el7_3.2
 updates
 libvirt-daemon-driver-interface.x86_64  2.0.0-10.el7_3.2
 updates
 libvirt-daemon-driver-lxc.x86_642.0.0-10.el7_3.2
 updates
 libvirt-daemon-driver-network.x86_642.0.0-10.el7_3.2
 updates
 libvirt-daemon-driver-nodedev.x86_642.0.0-10.el7_3.2
 updates
 libvirt-daemon-driver-nwfilter.x86_64   2.0.0-10.el7_3.2
 updates
 libvirt-daemon-driver-qemu.x86_64   2.0.0-10.el7_3.2
 updates
 libvirt-daemon-driver-secret.x86_64 2.0.0-10.el7_3.2
 updates
 libvirt-daemon-driver-storage.x86_642.0.0-10.el7_3.2
 updates
 libvirt-daemon-kvm.x86_64   2.0.0-10.el7_3.2
 updates
 libvirt-lock-sanlock.x86_64 2.0.0-10.el7_3.2
 updates
 libvirt-python.x86_64   2.0.0-2.el7
 base
 
 [root@microcloud21 yum.repos.d]# yum check-update | grep qemu*
 ipxe-roms-qemu.noarch   20160127-5.git6366fa7a.el7
 base
 libvirt-daemon-driver-qemu.x86_64   2.0.0-10.el7_3.2
 updates
 
 
 Am 13.12.2016 um 08:43 schrieb Sandro Bonazzola:
> 
> 
> On Mon, Dec 12, 2016 at 6:38 PM, Chris Adams >>
> >> wrote:
> 
>Once upon a time, Sandro Bonazzola  
>>> said:
>> In terms of ovirt repositories, qemu-kvm-ev 2.6 is available
>right now in
>> ovirt-master-snapshot-static, ovirt-4.0-snapshot-static, and
>ovirt-4.0-pre
>> (contains 4.0.6 RC4 rpms going to be announced in a few minutes.)
> 
>Will qemu-kvm-ev 2.6 be added to any of the oVirt repos for prior
>versions (such as 3.5 or 3.6)?
> 
> 
> You can enable CentOS Virt SIG repo by running "yum install
> centos-release-qemu-ev" on your CentOS 7 systems.
> and you'll have updated qemu-kvm-ev.
> 
> 
> 
>--
>Chris Adams 
>>>>>
>___
>Users mailing list
>Users@ovirt.org 
>>>>
>http://lists.phx.ovirt.org/mailman/listinfo/users
>>>
>

Re: [ovirt-users] [HEADS UP] CentOS 7.3 is rolling out, need qemu-kvm-ev 2.6

2016-12-22 Thread Michal Skrivanek 

> On 15 Dec 2016, at 16:46, Sandro Bonazzola  wrote:
> 
> 
> 
> Il 15/Dic/2016 16:17, "InterNetX - Juergen Gotteswinter"  
> ha scritto:
> Am 15.12.2016 um 15:51 schrieb Sandro Bonazzola:
> >
> >
> > On Thu, Dec 15, 2016 at 3:02 PM, InterNetX - Juergen Gotteswinter
> > > wrote:
> >
> > i can confirm that it will break ...
> >
> > Dec 15 14:58:43 vm1 journal: internal error: qemu unexpectedly closed
> > the monitor: Unexpected error in object_property_find() at
> > qom/object.c:1003:#0122016-12-15T13:58:43.140073Z qemu-kvm: can't apply
> > global Opteron_G4-x86_64-cpu.x1apic=off: Property '.x1apic' not found
> >
> >
> > Just an heads up that qemu-kvm-ev 2.6 is now
> > in http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/
> > 
> 
> [16:16:47][root@vm1:/var/log]$rpm -aq |grep qemu-kvm-ev
> qemu-kvm-ev-2.6.0-27.1.el7.x86_64
> [16:16:52][root@vm1:/var/log]$
> 
> this message is from 2.6
> 
> Adding Paolo and Michal.

it is important for 3.6 and 4.0, but in 4.1 we should not be using any rhel-6 
machine type anymore
There is https://bugzilla.redhat.com/show_bug.cgi?id=1402435 for HE which 
should be fixed (if real)

> 
> 
> 
> 
> 
> >
> >
> >
> >
> > cheers,
> >
> > Juergen
> >
> > Am 13.12.2016 um 10:30 schrieb Ralf Schenk:
> > > Hello
> > >
> > > by browsing the repository on
> > > http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/
> >  I can't see
> > > any qemu-kvm-ev-2.6.* RPM.
> > >
> > > I think this will break if I update the Ovirt-Hosts...
> > >
> > > [root@microcloud21 yum.repos.d]# yum check-update | grep libvirt
> > > libvirt.x86_64  2.0.0-10.el7_3.2
> > > updates
> > > libvirt-client.x86_64   2.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon.x86_64   2.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-config-network.x86_642.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-config-nwfilter.x86_64   2.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-driver-interface.x86_64  2.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-driver-lxc.x86_642.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-driver-network.x86_642.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-driver-nodedev.x86_642.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-driver-nwfilter.x86_64   2.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-driver-qemu.x86_64   2.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-driver-secret.x86_64 2.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-driver-storage.x86_642.0.0-10.el7_3.2
> > > updates
> > > libvirt-daemon-kvm.x86_64   2.0.0-10.el7_3.2
> > > updates
> > > libvirt-lock-sanlock.x86_64 2.0.0-10.el7_3.2
> > > updates
> > > libvirt-python.x86_64   2.0.0-2.el7
> > > base
> > >
> > > [root@microcloud21 yum.repos.d]# yum check-update | grep qemu*
> > > ipxe-roms-qemu.noarch   20160127-5.git6366fa7a.el7
> > > base
> > > libvirt-daemon-driver-qemu.x86_64   2.0.0-10.el7_3.2
> > > updates
> > >
> > >
> > > Am 13.12.2016 um 08:43 schrieb Sandro Bonazzola:
> > >>
> > >>
> > >> On Mon, Dec 12, 2016 at 6:38 PM, Chris Adams  > 
> > >> >> wrote:
> > >>
> > >> Once upon a time, Sandro Bonazzola  > 
> > >> >> said:
> > >> > In terms of ovirt repositories, qemu-kvm-ev 2.6 is available
> > >> right now in
> > >> > ovirt-master-snapshot-static, ovirt-4.0-snapshot-static, and
> > >> ovirt-4.0-pre
> > >> > (contains 4.0.6 RC4 rpms going to be announced in a few 
> > minutes.)
> > >>
> > >> Will qemu-kvm-ev 2.6 be added to any of the oVirt repos for prior
> > >> versions (such as 3.5 or 3.6)?
> > >>
> > >>
> > >> You can enable CentOS Virt SIG repo by running "yum install
> > >> centos-release-qemu-ev" on your CentOS 7 systems.
> > >> and you'll have updated qemu-kvm-ev.
> > >>
> > >>
> > >>
> > >> --
> > >> Chris Adams 
> > >>
> > >> ___
> > >> Users mailing list
> > >> Users@ovirt.org 
> > >
> > >>

Re: [ovirt-users] Regarding DAS for Shared Storage

2016-12-22 Thread Fernando Frediani 

Hello rex.

I have a very similar situation and I'm interested to find out how 
people are doing to use DAS in these types of environments.


Thanks
Fernando

On 22/12/2016 10:07, rex wrote:

Hi,

Have a VRTX Chassis enclosure populated with two Dell PowerEdge M620 
Blades and has a built-in DAS storage. Created a 1 TB Virtual Disk 
from the DAS storage using the Dell iDRAC interface. This block device 
is accessible from the two blades (CentOS 7 OS) like shown below,


 [root@node1 ~]# lsblk /dev/sdc

 NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
 sdc8:32   0 1024G  0 disk

 [root@node2 ~]# lsblk /dev/sdc

 NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
 sdc8:32   0 1024G  0 disk

 oVirt rpms has been installed on both the blades with the aim of 
configuring them as oVirt nodes with Live Migration feature. But other 
than the DAS we don't have any storage which can be used as shared 
storage. So can some one please tell me whether the above block disk 
can be used as a shared storage (i.e mounted on the two nodes at the 
same time) and if it is possible how can this be done. Thank you.



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Regarding DAS for Shared Storage

2016-12-22 Thread rex 
Hi,

Have a VRTX Chassis enclosure populated with two Dell PowerEdge M620 Blades
and has a built-in DAS storage. Created a 1 TB Virtual Disk from the DAS
storage using the Dell iDRAC interface. This block device is accessible
from the two blades (CentOS 7 OS) like shown below,

 [root@node1 ~]# lsblk /dev/sdc

 NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
 sdc8:32   0 1024G  0 disk

 [root@node2 ~]# lsblk /dev/sdc

 NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
 sdc8:32   0 1024G  0 disk

 oVirt rpms has been installed on both the blades with the aim of
configuring them as oVirt nodes with Live Migration feature. But other than
the DAS we don't have any storage which can be used as shared storage. So
can some one please tell me whether the above block disk can be used as a
shared storage (i.e mounted on the two nodes at the same time) and if it is
possible how can this be done. Thank you.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt Java SDK

2016-12-22 Thread TranceWorldLogic . 
Hi,

I am getting below error logs
---
[INFO] ERROR org.ovirt.api.metamodel.tool.Main - Error while executing the
"run" method of tool class "org.ovirt.sdk.java.Tool".
[INFO] java.lang.reflect.InvocationTargetException
[INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[INFO] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO] at java.lang.reflect.Method.invoke(Method.java:498)
[INFO] at org.ovirt.api.metamodel.tool.Main.main(Main.java:74)
[INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[INFO] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO] at java.lang.reflect.Method.invoke(Method.java:498)
[INFO] at
org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
[INFO] at java.lang.Thread.run(Thread.java:745)
[INFO] Caused by: java.lang.NoSuchMethodError:
org.apache.commons.cli.Option.builder()Lorg/apache/commons/cli/Option$Builder;
[INFO] at org.ovirt.sdk.java.Tool.run(Tool.java:71)
[INFO] at org.ovirt.sdk.java.Tool$Proxy$_$$_WeldClientProxy.run(Unknown
Source)
[INFO] ... 11 more
[INFO] Weld SE container STATIC_INSTANCE shut down by shutdown hook
-

Please let me know what is wrong I did.

Thanks,
~Rohit

On Thu, Dec 22, 2016 at 3:56 PM, Roy Golan  wrote:

>
>
> On 22 December 2016 at 11:21, TranceWorldLogic . <
> tranceworldlo...@gmail.com> wrote:
>
>> Hi,
>>
>> I want to try Java SDK to see its usability.
>>
>> Can someone help me how to checkout code and compile Java SDK ?
>> or Install Java SDK ?
>>
>> I am using Eclipse-Java for IDE.
>>
>
>
> Start with the readme https://github.com/oVirt/ovirt-engine-sdk-java/tree/
> master/sdk
> and check out the examples https://github.com/oVirt/
> ovirt-engine-sdk-java/tree/master/sdk/src/test/java/org/
> ovirt/engine/sdk4/examples
>
>
>> Thanks,
>> ~Rohit
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
[INFO] Scanning for projects...
[INFO] 
[INFO] Building oVirt Java SDK
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] 
[INFO] [release:prepare {execution: default-cli}]
[INFO] Resuming release from phase 'run-preparation-goals'
[INFO] Executing goals 'clean verify'...
[WARNING] Maven will be executed in interactive mode, but no input stream has 
been configured for this MavenInvoker instance.
[INFO] [INFO] Scanning for projects...
[INFO] [INFO] 

[INFO] [INFO] Building oVirt Java SDK
[INFO] [INFO]task-segment: [clean, verify]
[INFO] [INFO] 

[INFO] [INFO] [clean:clean {execution: default-clean}]
[INFO] [INFO] Deleting file set: 
/exports/Tools/tools/ovirt_tools/ovirt-engine-sdk-java/sdk/target (included: 
[**], excluded: [])
[INFO] [INFO] [dependency:copy {execution: copy-model}]
[INFO] [INFO] Configured Artifact: org.ovirt.engine.api:model:sources:4.0.37:jar
[INFO] [INFO] Copying model-4.0.37-sources.jar to 
/exports/Tools/tools/ovirt_tools/ovirt-engine-sdk-java/sdk/target/model.jar
[INFO] [INFO] [dependency:unpack {execution: copy-metamodel}]
[INFO] [INFO] Configured Artifact: 
org.ovirt.engine.api:metamodel-runtime:sources:1.0.21:jar
[INFO] [INFO] Unpacking 
/home/ipa/.m2/repository/org/ovirt/engine/api/metamodel-runtime/1.0.21/metamodel-runtime-1.0.21-sources.jar
 to
[INFO]   
/exports/Tools/tools/ovirt_tools/ovirt-engine-sdk-java/sdk/target/generated-sources
[INFO]with includes **/xml/*.java,**/util/*.java and excludes:null
[INFO] [INFO] Preparing exec:java
[INFO] [WARNING] Removing: java from forked lifecycle, to prevent recursive 
invocation.
[INFO] [INFO] No goals needed for project - skipping
[INFO] [INFO] [exec:java {execution: generate-code}]
[INFO] ERROR org.ovirt.api.metamodel.tool.Main - Error while executing the 
"run" method of tool class "org.ovirt.sdk.java.Tool".
[INFO] java.lang.reflect.InvocationTargetException
[INFO]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO]  at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[INFO]  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO]  at java.lang.reflect.Method.invoke(Method.java:498)
[INFO]  at org.ovirt.api.metamodel.tool.Main.main(Main.java:74)
[INFO]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO]  at

Re: [ovirt-users] Ovirt Java SDK

2016-12-22 Thread Roy Golan 
On 22 December 2016 at 11:21, TranceWorldLogic .  wrote:

> Hi,
>
> I want to try Java SDK to see its usability.
>
> Can someone help me how to checkout code and compile Java SDK ?
> or Install Java SDK ?
>
> I am using Eclipse-Java for IDE.
>


Start with the readme
https://github.com/oVirt/ovirt-engine-sdk-java/tree/master/sdk
and check out the examples
https://github.com/oVirt/ovirt-engine-sdk-java/tree/master/sdk/src/test/java/org/ovirt/engine/sdk4/examples


> Thanks,
> ~Rohit
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] BUG: "interface" field empty in "attach disk" windows Ovirt 4.0.5

2016-12-22 Thread Andrea Ghelardi 
Done as requested; filed https://bugzilla.redhat.com/show_bug.cgi?id=1408134

Thank you for your help!
Andrea


From: Fred Rolland [mailto:froll...@redhat.com]
Sent: Thursday, December 22, 2016 8:01 AM
To: Andrea Ghelardi 
Cc: users 
Subject: Re: [ovirt-users] BUG: "interface" field empty in "attach disk" 
windows Ovirt 4.0.5

Thanks for reporting.
Can you open a bug ?

https://www.ovirt.org/community/get-involved/report-a-bug/

On Wed, Dec 21, 2016 at 7:06 PM, Andrea Ghelardi 
> wrote:
Hello team,
FYI there is a minor, cosmetic bug in 4.0.5 GUI


1)  Select VM -> tab DISKS

2)  Click Attach -> “Attach” window pop-ups with list of available disks  
(attach PNG01)

3)  You can click and select interface type (attach PNG02)

4)  If you select disk to attach, Interface becomes blank (PNG03 and PNG04)

5)  If you move mouse up and down, correct entry is shown  (and just that 
one) PNG05 and PNG06

6)  Once selected, filed is still blank (in this case, Virtio-scsi) PNG07

7)  Disk is attached correctly, according to option “blindly” selected PNG08

Cheers
AG


Andrea Ghelardi

+39 050 2203 71 | www.iongroup.com | 
a.ghela...@iontrading.com
Via San Martino, 52 – 56125 Pisa - ITALY

This email and any attachments may contain information which is confidential 
and/or privileged. The information is intended exclusively for the addressee 
and the views expressed may not be official policy, but the personal views of 
the originator. If you are not the intended recipient, be aware that any 
disclosure, copying, distribution or use of the contents is prohibited. If you 
have received this email and any file transmitted with it in error, please 
notify the sender by telephone or return email immediately and delete the 
material from your computer. Internet communications are not secure and ION 
Trading is not responsible for their abuse by third parties, nor for any 
alteration or corruption in transmission, nor for any damage or loss caused by 
any virus or other defect. ION Trading accepts no liability or responsibility 
arising out of or in any way connected to this email.

[iON_HBlu_small]
Automation through innovation


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Ovirt Java SDK

2016-12-22 Thread TranceWorldLogic . 
Hi,

I want to try Java SDK to see its usability.

Can someone help me how to checkout code and compile Java SDK ?
or Install Java SDK ?

I am using Eclipse-Java for IDE.

Thanks,
~Rohit
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users