[ovirt-users] Graphics are turned upside down when install QXL in Windows

2017-03-06 Thread Karli Sjöberg 
Heya!

Just thought that I´d report something hilarious:)

After installing the QXL driver in Windows 7 and 2008R2, in the SPICE
HTML5 browser client, all of the graphics are turned 180 degrees. It´s
not that the entire screen is flipped either, but all of the individual
elements are. E.g. the trashcan that should be in the top right corner
is now located in the bottom right, flipped upside down with the text
"above" it and text also flipped. Opening an explorer windows still has
the location and search bar at the top, with location bar first and
search bar to the right, as it should be, but with the graphics turned
upside down, plus that the text is still printed from left to right,
but upside down. And the "favorites" pane is still located to the left
but listed from bottom the top, Windows has never looked this funny:)

A picture says a thousand words. Behold!
http://imgur.com/a/32P12

The native client displays as it should.

Just letting you know.

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

Re: [ovirt-users] [Gluster-users] Replicated Glusterfs on top of ZFS

2017-03-06 Thread Sahina Bose 
On Mon, Mar 6, 2017 at 3:21 PM, Arman Khalatyan  wrote:

>
>
> On Fri, Mar 3, 2017 at 7:00 PM, Darrell Budic 
> wrote:
>
>> Why are you using an arbitrator if all your HW configs are identical? I’d
>> use a true replica 3 in this case.
>>
>>
> This was just GIU suggestion when I was creating the cluster it was asking
> for the 3 Hosts , I did not knew even that an Arbiter does not keep the
> data.
> I am not so sure if I can change the type of the glusterfs to triplicated
> one in the running system, probably I need to destroy whole cluster.
>
>
>
>> Also in my experience with gluster and vm hosting, the ZIL/slog degrades
>> write performance unless it’s a truly dedicated disk. But I have 8 spinners
>> backing my ZFS volumes, so trying to share a sata disk wasn’t a good zil.
>> If yours is dedicated SAS, keep it, if it’s SATA, try testing without it.
>>
>>
> We  have also several huge systems running with zfs quite successful over
> the years. This was an idea to use zfs + glusterfs for the HA solutions.
>
>
>> You don’t have compression enabled on your zfs volume, and I’d recommend
>> enabling relatime on it. Depending on the amount of RAM in these boxes, you
>> probably want to limit your zfs arc size to 8G or so (1/4 total ram or
>> less). Gluster just works volumes hard during a rebuild, what’s the problem
>> you’re seeing? If it’s affecting your VMs, using shading and tuning client
>> & server threads can help avoid interruptions to your VMs while repairs are
>> running. If you really need to limit it, you can use cgroups to keep it
>> from hogging all the CPU, but it takes longer to heal, of course. There are
>> a couple older posts and blogs about it, if you go back a while.
>>
>
> Yes I saw that glusterfs is CPU/RAM hugry!!! 99% of all 16 cores used just
> for healing 500GB vm disks. It was taking almost infinity compare with nfs
> storage (single disk+zfs ssd cache, for sure one get an penalty for the
> HA:) )
>

Is your gluster volume configured to use sharding feature? Could you
provide output of gluster vol info?


>
>
>
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] How to enable tunnel migration

2017-03-06 Thread like...@cs2c.com.cn 
Hi,
 
I'm using oVirt 3.6.7 now. I want to enable tunnel migration feature. 
But when i set tunnel_migration value of vm as Ture through python
SDK(I can't find any place to enable tunnel migration on the web ui,
so i use SDK), then migrate the vm i got the following error message:
 
Thread-9417628::ERROR::2017-03-07 11:25:48,538::migration::310::virt.vm::(run) 
vmId=`08b4ccc1-c508-439b-a9ba-ca0d42a7072c`::Failed to migrate
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/migration.py", line 298, in run
self._startUnderlyingMigration(time.time())
  File "/usr/share/vdsm/virt/migration.py", line 364, in 
_startUnderlyingMigration
self._perform_migration(duri, muri)
  File "/usr/share/vdsm/virt/migration.py", line 403, in _perform_migration
self._vm._dom.migrateToURI3(duri, params, flags)
  File "/usr/share/vdsm/virt/virdomain.py", line 68, in f
ret = attr(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 124, 
in wrapper
ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 1313, in wrapper
return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1836, in 
migrateToURI3
if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', 
dom=self)
libvirtError: 不支持的参数：migration URI is not supported by tunnelled migration

So, i want to know how should i enable the tunnel migration feature. Can anyone 
help me?
Thanks
 
Regards.



like...@cs2c.com.cn
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Storage balancer project

2017-03-06 Thread nicolas 

Hi,

I implemented a storage domain balancer [1], i.e. a script that tries to 
keep all storage domains under a defined threshold. We use our oVirt 
infrastructure for teaching so have several hundreds of users and cca. 
800 VMs at this time, so something like this is really needed 
considering that when students create their VMs they tend to create 
their disks under the same storage domain (normally the first available 
one). This results in one or two heavily used SDs and the rest 
underused.


I tried to keep it as simple as possible and doesn't have many features, 
but it seems to work (I tried it under our conditions: About 10 SDs, 
relatively highly used). If someone want to improve something on it, 
pull requests are welcome.


Might also be an inspiration on [2].

Regards.

  [1]: https://github.com/nkovacne/ovirt-storage-balancer
  [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1331544
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Christophe TREFOIS 
Good question.

But I can assure you that not everything is golden goose.

Sometimes there is legacy, lack of knowledge, and so on, and there are many use 
cases where a full test env is not a given.
It is desired yes, but currently not an option.

By the way, to quote some famous people, everyone has a test environment, only 
few of us are lucky enough to have prod env as well.

And based on the problems we encountered recently, which were upgrade related, 
it would have been difficult to have a 1:1 test env anyway, as this issue for 
sure would not have been caught.

Cheers,

> On 6 Mar 2017, at 13:28, Sven Kieske  wrote:
> 
> On 06/03/17 10:48, Andrea Ghelardi wrote:
>> A)  there could be no test environment to check the upgraded version 
>> behavior and
>> 
>> B)  the upgrade itself may require more than a bit of effort when there 
>> are dozen hosts and multiple clusters involved,
>> this does not really encourage to always push the datacenter to the latest 
>> version available, especially if the in-production version is not 
>> misbehaving.
>> 
>> Please note I'm just sharing our company view and not blaming anyone.
>> 
>> Cheers
>> Andrea
> 
> As a side note:
> 
> What kind of data center do you run, that lacks any test environment?
> 
> If you don't have a testbed, than you have far worse problems than the
> number of bugfixes and things which might (not) work in a new ovirt version.
> 
> -- 
> Mit freundlichen Grüßen / Regards
> 
> Sven Kieske
> 
> Systemadministrator
> Mittwald CM Service GmbH & Co. KG
> Königsberger Straße 6
> 32339 Espelkamp
> T: +495772 293100
> F: +495772 29
> 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

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

[ovirt-users] oVirt Nodes Monitoring

2017-03-06 Thread FERNANDO FREDIANI 

Hi.

How do you guys monitor your hosts with Zabbix ?
I see the oVirt Nodes have snmpd service installed and could be used for 
basic things but ideally, for Zabbix is good to use its agent.


What would be the best way to install its zabbix-agent package and make 
it persistent ? Add its repository to the oVirt-Node in 
/etc/yum.repos.d/ and install it with yum or install using a .rpm directly ?


Thanks
Fernando

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

Re: [ovirt-users] [Gluster-users] Hot to force glusterfs to use RDMA?

2017-03-06 Thread Arman Khalatyan 
https://bugzilla.redhat.com/show_bug.cgi?id=1428851

On Mon, Mar 6, 2017 at 12:56 PM, Mohammed Rafi K C 
wrote:

> I will see what we can do from gluster side to fix this. I will get back
> to you .
>
>
> Regards
>
> Rafi KC
>
> On 03/06/2017 05:14 PM, Denis Chaplygin wrote:
>
> Hello!
>
> On Fri, Mar 3, 2017 at 12:18 PM, Arman Khalatyan < 
> arm2...@gmail.com> wrote:
>
>> I think there are some bug in the vdsmd checks;
>>
>> OSError: [Errno 2] Mount of `10.10.10.44:/GluReplica` at
>> `/rhev/data-center/mnt/glusterSD/10.10.10.44:_GluReplica` does not exist
>>
>
>
>>
>> 10.10.10.44:/GluReplica.rdma   3770662912 407818240 3362844672
>> <(336)%20284-4672>  11% /rhev/data-center/mnt/glusterSD/10.10.10.44:
>> _GluReplica
>>
>
> I suppose, that vdsm is not able to handle that .rdma suffix on volume
> path. Could you please file a bug for that issue to track it?
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Nested Virtualization

2017-03-06 Thread Sandro Bonazzola 
On Mon, Mar 6, 2017 at 9:20 AM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

> On Sun, Mar 5, 2017 at 2:43 PM, Barak Korren  wrote:
> > oVirt system tests are indeed using nested virtualization, but it is
> > done to run oVirt nested on top of a stand-alone KVM host, and not to
> > run nested stuff on top of oVirt.
> >
> > The steps Fred specified can be done manually on all hosts, but oVirt
> > offers a slightly more automated alternative. Simply install the
> > following vdsm hooks (available as packages) on all hosts:
> >
> > vdsm-hook-macspoof
> > vdsm-hook-nestedvt
> >
> > And then reboot the hosts (You will need to put hosts into maintenance
> > mode to do that).
> >
>
> Hello,
>
> the packages you're referring are not available through yum on hosts.
> I've seen that only specific packages are included from repos, does
> these packages are excluded?
>

ovirt-node is designed to just update itself as a firmware.
any additional packages is treated as 3rd party rpm which will be persisted
on upgrade.
In order to install the hooks on node you need to enable the ovirt
repositories in /etc/yum.repos.d

For installing the hooks on al new hosts during deploy you can do on the
engine host / vm:
# echo  vdsm-hook-macspoof >
/usr/share/ovirt-host-deploy/plugins/ovirt-host-deploy/vdsmhooks/packages.d/vdsm-hook-macspoof.centos
# echo  vdsm-hook-nestedvt >
/usr/share/ovirt-host-deploy/plugins/ovirt-host-deploy/vdsmhooks/packages.d/vdsm-hook-nestedvt.centos

And whenever you'll add a new node, those packages will be installed. Just
remember to enable the repository before adding the new host to the engine.
Packages and configuration will be persisted on upgrade.




>
> Luca
>
>
>
> --
> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
> calcoli che potrebbero essere affidati a chiunque se si usassero delle
> macchine"
> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>
> "Internet è la più grande biblioteca del mondo.
> Ma il problema è che i libri sono tutti sparsi sul pavimento"
> John Allen Paulos, Matematico (1945-vivente)
>
> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
> lorenzetto.l...@gmail.com>
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Sven Kieske 
On 06/03/17 10:48, Andrea Ghelardi wrote:
> A)  there could be no test environment to check the upgraded version 
> behavior and
> 
> B)  the upgrade itself may require more than a bit of effort when there 
> are dozen hosts and multiple clusters involved,
> this does not really encourage to always push the datacenter to the latest 
> version available, especially if the in-production version is not misbehaving.
> 
> Please note I'm just sharing our company view and not blaming anyone.
> 
> Cheers
> Andrea

As a side note:

What kind of data center do you run, that lacks any test environment?

If you don't have a testbed, than you have far worse problems than the
number of bugfixes and things which might (not) work in a new ovirt version.

-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +495772 293100
F: +495772 29
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



signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM Permissions (3.6)

2017-03-06 Thread Oved Ourfali 
Hi Alexis,

Permissions in oVirt consist of three parts:
1. The user/group
2. The role
3. The object

So, if you want a user to be able to "use" a VM, it should be enough to
grant him a UserRole on the VM object (no need to go to the system
preferences for that one).
If you want a user to be the owner of a VM (allows more actions on that VM
than UserRole), then you should grant him with UserVmManager on the VM
object.

The role itself consists of actions that are allowed to be done with it.
You can view these actions in the UI through the system preferences dialog.

When you grant permissions on the system preferences dialog, then it means
the "object" you grant on is the "system" object, which is in the higher
part of the objects tree.
Normally you won't need that for users.

As for managing permissions, it can be done either via the UI, or the API,
or one of the SDKs.
I guess it is a matter of preference and needs.

Cheers,
Oved


On Sun, Mar 5, 2017 at 1:51 PM, Alexis HAUSER <
alexis.hau...@imt-atlantique.fr> wrote:

> hi, I'm trying to figure out how to manage VM permissions with ovirt.
> From what I've understood, if you add a user to user role in the system
> preferences, this user can access every VM and resources on the cluster,
> with the associated permissions; right ?
> Now, if I want to control who has access to each VM : I musn't add this
> user to user role from the system tab; but instead add it on each resources
> (like on each VM) it should access ?
>
> Is there another way to manage permissions ? How you guys do personally
> manage this ? Do you automate it with scripts ?
>
> Thanks for you ideas and suggestions
>
> (using 3.6)
>
> ___
> 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] [Gluster-users] Hot to force glusterfs to use RDMA?

2017-03-06 Thread Mohammed Rafi K C 
I will see what we can do from gluster side to fix this. I will get back
to you .


Regards

Rafi KC


On 03/06/2017 05:14 PM, Denis Chaplygin wrote:
> Hello!
>
> On Fri, Mar 3, 2017 at 12:18 PM, Arman Khalatyan  > wrote:
>
> I think there are some bug in the vdsmd checks;
>
> OSError: [Errno 2] Mount of `10.10.10.44:/GluReplica` at
> `/rhev/data-center/mnt/glusterSD/10.10.10.44:_GluReplica` does not
> exist
>
>  
>
>
> 10.10.10.44:/GluReplica.rdma   3770662912 407818240 3362844672 
> 11% /rhev/data-center/mnt/glusterSD/10.10.10.44:_GluReplica
>
>
> I suppose, that vdsm is not able to handle that .rdma suffix on volume
> path. Could you please file a bug for that issue to track it?

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

Re: [ovirt-users] [Gluster-users] Hot to force glusterfs to use RDMA?

2017-03-06 Thread Denis Chaplygin 
Hello!

On Fri, Mar 3, 2017 at 12:18 PM, Arman Khalatyan  wrote:

> I think there are some bug in the vdsmd checks;
>
> OSError: [Errno 2] Mount of `10.10.10.44:/GluReplica` at
> `/rhev/data-center/mnt/glusterSD/10.10.10.44:_GluReplica` does not exist
>


>
> 10.10.10.44:/GluReplica.rdma   3770662912 407818240 3362844672  11%
> /rhev/data-center/mnt/glusterSD/10.10.10.44:_GluReplica
>

I suppose, that vdsm is not able to handle that .rdma suffix on volume
path. Could you please file a bug for that issue to track it?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Andrea Ghelardi 
I somehow agree to this statement
While ovirt team is really doing an awesome job and ovirt is getting more and 
more polished at every release, a +100 critical bugfixes statement in a minor 
release tends to underline the flaws of 4.1.0 rather than the good things of 
4.1.1

Considering that

A)  there could be no test environment to check the upgraded version 
behavior and

B)  the upgrade itself may require more than a bit of effort when there are 
dozen hosts and multiple clusters involved,
this does not really encourage to always push the datacenter to the latest 
version available, especially if the in-production version is not misbehaving.

Please note I'm just sharing our company view and not blaming anyone.

Cheers
Andrea

From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
Christophe TREFOIS
Sent: Monday, March 6, 2017 12:18 AM
To: Sandro Bonazzola 
Cc: users 
Subject: Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

Hi,

Is 4.1.0 still recommneded an upgrade from 4.0.6 in production or should we 
wait for 4.1.1 to comee out?

100+ critical bugs fixed sounds good but doesnt really encourage upgrading to 
4.1.0

thoughts?

Christophe

On 3 Mar 2017, at 14:48, Sandro Bonazzola 
mailto:sbona...@redhat.com>> wrote:

The oVirt Project is pleased to announce the availability of the First
Release Candidate of oVirt 4.1.1 for testing, as of March 3rd, 2017

This is pre-release software. Please take a look at our community page[1]
to know how to ask questions and interact with developers and users.
All issues or bugs should be reported via oVirt Bugzilla[2].
This pre-release should not to be used in production.

This update is the first release candidate of the first in a series of
stabilization updates to the 4.1 series.
4.1.1 brings 26 enhancements and more than 350 bugfixes,
including more than 130 high or urgent
severity fixes, on top of oVirt 4.1 series

This release is available now for:
* Fedora 24 (tech preview)
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 24 (tech preview)

See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Live has been already built [4]
- oVirt Node and Appliance has not been built for this release due to build 
issues we're still investigating.

Additional Resources:
* Read more about the oVirt 4.1.1 release 
highlights:http://www.ovirt.org/release/4.1.1/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1.1/
[4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/



--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
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] VM Permissions (3.6)

2017-03-06 Thread Alexis HAUSER 
hi, I'm trying to figure out how to manage VM permissions with ovirt. 
>From what I've understood, if you add a user to user role in the system 
>preferences, this user can access every VM and resources on the cluster, with 
>the associated permissions; right ? 
Now, if I want to control who has access to each VM : I musn't add this user to 
user role from the system tab; but instead add it on each resources (like on 
each VM) it should access ? 

Is there another way to manage permissions ? How you guys do personally manage 
this ? Do you automate it with scripts ? 

Thanks for you ideas and suggestions 

(using 3.6) 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Sandro Bonazzola 
On Mon, Mar 6, 2017 at 10:09 AM, Maton, Brett 
wrote:

> Hi Sandro,
>
>   I just took a look at the updated release notes, the upgrade existing HE
> links return a 404 page not found error.
>
> If you're upgrading an existing Hosted Engine setup, please follow
> Hosted_Engine_Howto#Upgrade_Hosted_Engine
> 
> guide or the corresponding section within the Upgrade Guide
> 
>

Yes, sadly while still in github the links doesn't work very well.
I'm working with infra engineers to get the website back to an updated
status.

Hosted Engine Howto:
https://www.ovirt.org/documentation/how-to/hosted-engine/
Upgrade guide:
http://www.ovirt.org/documentation/upgrade-guide/upgrade-guide/




>
>
> Regards,
> Brett
>
> On 6 March 2017 at 08:55, Sandro Bonazzola  wrote:
>
>>
>>
>> On Mon, Mar 6, 2017 at 9:49 AM, Christophe TREFOIS <
>> christophe.tref...@uni.lu> wrote:
>>
>>> Hi Sandro,
>>>
>>> We upgraded now to 4.1.0, just have to upgrade now the hosts.
>>>
>>> We don’t have test env, so we’re in prod.
>>>
>>> If we encounter some bugs fixed in 4.1.1, how could get to 4.1.1 RC?
>>>
>>
>> For some reason the website has not been updated (I already opened a
>> github issue about that).
>> You can find updated release notes with instructions here.
>> https://github.com/oVirt/ovirt-site/blob/b24c3f60f26cf
>> 27054bd7dfcd9cc4d6d52005a19/source/release/4.1.1/index.html.md
>>
>>
>>
>>
>>>
>>> Thanks,
>>>
>>> --
>>>
>>> Dr Christophe Trefois, Dipl.-Ing.
>>> Technical Specialist / Post-Doc
>>>
>>> UNIVERSITÉ DU LUXEMBOURG
>>>
>>> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
>>> Campus Belval | House of Biomedicine
>>> 6, avenue du Swing
>>> L-4367 Belvaux
>>> T: +352 46 66 44 6124 <+352%2046%2066%2044%206124>
>>> F: +352 46 66 44 6949 <+352%2046%2066%2044%206949>
>>> http://www.uni.lu/lcsb
>>>
>>> [image: Facebook]   [image: Twitter]
>>>   [image: Google Plus]
>>>   [image: Linkedin]
>>>   [image: skype]
>>> 
>>>
>>> 
>>> This message is confidential and may contain privileged information.
>>> It is intended for the named recipient only.
>>> If you receive it in error please notify me and permanently delete the
>>> original message and any copies.
>>> 
>>>
>>>
>>> On 6 Mar 2017, at 09:47, Sandro Bonazzola  wrote:
>>>
>>>
>>>
>>> On Mon, Mar 6, 2017 at 9:46 AM, Sandro Bonazzola 
>>> wrote:
>>>


 On Mon, Mar 6, 2017 at 12:18 AM, Christophe TREFOIS <
 christophe.tref...@uni.lu> wrote:

> Hi,
>
> Is 4.1.0 still recommneded an upgrade from 4.0.6 in production or
> should we wait for 4.1.1 to comee out?
>
> 100+ critical bugs fixed sounds good but doesnt really encourage
> upgrading to 4.1.0
>
> thoughts?
>

 Note that between 4.0.6 and 4.1.0 there were ~1100 bugfix+enanchement
 fixed and in 4.1.1 there will be other ~400 bugfix+enhancements
 Being the 4.1.1 release scheduled in ~1 week, I would wait for it.

>>>
>>> Or you can upgrade right now to the release candidate and help us
>>> testing it :-)
>>>
>>>
>>>



>
> Christophe
>
> On 3 Mar 2017, at 14:48, Sandro Bonazzola  wrote:
>
>
> The oVirt Project is pleased to announce the availability of the First
> Release Candidate of oVirt 4.1.1 for testing, as of March 3rd, 2017
>
> This is pre-release software. Please take a look at our community
> page[1]
> to know how to ask questions and interact with developers and users.
> All issues or bugs should be reported via oVirt Bugzilla[2].
> This pre-release should not to be used in production.
>
> This update is the first release candidate of the first in a series of
> stabilization updates to the 4.1 series.
> 4.1.1 brings 26 enhancements and more than 350 bugfixes,
> including more than 130 high or urgent
> severity fixes, on top of oVirt 4.1 series
>
> This release is available now for:
> * Fedora 24 (tech preview)
> * Red Hat Enterprise Linux 7.3 or later
> * CentOS Linux (or similar) 7.3 or later
>
> This release supports Hypervisor Hosts running:
> * Red Hat Enterprise Linux 7.3 or later
> * CentOS Linux (or similar) 7.3 or later
> * Fedora 24 (tech preview)
>
> See the release notes draft [3] for installation / upgrade
> instructions and
> a list of new features and bugs fixed.
>
> Notes:
> - oVirt Live has been already built [4]
> - oVirt Node and Appliance has not been built for this release due to
> build issues we're still investigating.

Re: [ovirt-users] oVirt Nested Virtualization

2017-03-06 Thread Nir Soffer 
On Mon, Mar 6, 2017 at 11:56 AM, Barak Korren  wrote:
> On 6 March 2017 at 10:20, Luca 'remix_tj' Lorenzetto
>  wrote:
>>> The steps Fred specified can be done manually on all hosts, but oVirt
>>> offers a slightly more automated alternative. Simply install the
>>> following vdsm hooks (available as packages) on all hosts:
>>>
>>> vdsm-hook-macspoof
>>> vdsm-hook-nestedvt
>>>
>>> And then reboot the hosts (You will need to put hosts into maintenance
>>> mode to do that).
>>>
>>
>> Hello,
>>
>> the packages you're referring are not available through yum on hosts.
>> I've seen that only specific packages are included from repos, does
>> these packages are excluded?
>
> Those packages should be available from the oVirt repos as they are
> built together with the vdsm package. Perhaps node has special
> exclusions. Referring again to the node maintainers. Sandro? Fabian?

+Ryan (working now on node)

>
>
> --
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
> ___
> 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] Ovirt importing VM

2017-03-06 Thread Alex 
That was sneaky!
Thank you Arik.

cheers,
Alex

On March 5, 2017 1:46:04 PM GMT+02:00, Arik Hadas  wrote:
>On Thu, Mar 2, 2017 at 10:48 AM, rightkicktech.gmail.com <
>rightkickt...@gmail.com> wrote:
>
>> Hi,
>>
>> I am using Virt4.1 on top glusterfs.
>> I have defined two data domains, one for engine and one for vms. Also
>> export and iso domains are on separate dedicated gluster volumes.
>>
>> When I try to import a VM from the export domain the VM is imported
>in the
>> engine data domain. I would expect to be able to select on which data
>> domain to import it. Am I missing sth?
>>
>
>Yeah, you missed the disks subtab at the import dialog :)
>When pressing on one of the VMs to be imported subtabs appear and you
>can
>configure the destination data domain per-disk (see the screenshot
>attached).
>
>
>>
>> Thanx,
>> Alex
>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Nested Virtualization

2017-03-06 Thread Barak Korren 
On 6 March 2017 at 10:20, Luca 'remix_tj' Lorenzetto
 wrote:
>> The steps Fred specified can be done manually on all hosts, but oVirt
>> offers a slightly more automated alternative. Simply install the
>> following vdsm hooks (available as packages) on all hosts:
>>
>> vdsm-hook-macspoof
>> vdsm-hook-nestedvt
>>
>> And then reboot the hosts (You will need to put hosts into maintenance
>> mode to do that).
>>
>
> Hello,
>
> the packages you're referring are not available through yum on hosts.
> I've seen that only specific packages are included from repos, does
> these packages are excluded?

Those packages should be available from the oVirt repos as they are
built together with the vdsm package. Perhaps node has special
exclusions. Referring again to the node maintainers. Sandro? Fabian?


-- 
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Replicated Glusterfs on top of ZFS

2017-03-06 Thread Arman Khalatyan 
On Fri, Mar 3, 2017 at 7:00 PM, Darrell Budic 
wrote:

> Why are you using an arbitrator if all your HW configs are identical? I’d
> use a true replica 3 in this case.
>
>
This was just GIU suggestion when I was creating the cluster it was asking
for the 3 Hosts , I did not knew even that an Arbiter does not keep the
data.
I am not so sure if I can change the type of the glusterfs to triplicated
one in the running system, probably I need to destroy whole cluster.



> Also in my experience with gluster and vm hosting, the ZIL/slog degrades
> write performance unless it’s a truly dedicated disk. But I have 8 spinners
> backing my ZFS volumes, so trying to share a sata disk wasn’t a good zil.
> If yours is dedicated SAS, keep it, if it’s SATA, try testing without it.
>
>
We  have also several huge systems running with zfs quite successful over
the years. This was an idea to use zfs + glusterfs for the HA solutions.


> You don’t have compression enabled on your zfs volume, and I’d recommend
> enabling relatime on it. Depending on the amount of RAM in these boxes, you
> probably want to limit your zfs arc size to 8G or so (1/4 total ram or
> less). Gluster just works volumes hard during a rebuild, what’s the problem
> you’re seeing? If it’s affecting your VMs, using shading and tuning client
> & server threads can help avoid interruptions to your VMs while repairs are
> running. If you really need to limit it, you can use cgroups to keep it
> from hogging all the CPU, but it takes longer to heal, of course. There are
> a couple older posts and blogs about it, if you go back a while.
>

Yes I saw that glusterfs is CPU/RAM hugry!!! 99% of all 16 cores used just
for healing 500GB vm disks. It was taking almost infinity compare with nfs
storage (single disk+zfs ssd cache, for sure one get an penalty for the
HA:) )
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Maton, Brett 
Hi Sandro,

  I just took a look at the updated release notes, the upgrade existing HE
links return a 404 page not found error.

If you're upgrading an existing Hosted Engine setup, please follow
Hosted_Engine_Howto#Upgrade_Hosted_Engine

guide or the corresponding section within the Upgrade Guide


Regards,
Brett

On 6 March 2017 at 08:55, Sandro Bonazzola  wrote:

>
>
> On Mon, Mar 6, 2017 at 9:49 AM, Christophe TREFOIS <
> christophe.tref...@uni.lu> wrote:
>
>> Hi Sandro,
>>
>> We upgraded now to 4.1.0, just have to upgrade now the hosts.
>>
>> We don’t have test env, so we’re in prod.
>>
>> If we encounter some bugs fixed in 4.1.1, how could get to 4.1.1 RC?
>>
>
> For some reason the website has not been updated (I already opened a
> github issue about that).
> You can find updated release notes with instructions here.
> https://github.com/oVirt/ovirt-site/blob/b24c3f60f26cf27054bd7dfcd9cc4d
> 6d52005a19/source/release/4.1.1/index.html.md
>
>
>
>
>>
>> Thanks,
>>
>> --
>>
>> Dr Christophe Trefois, Dipl.-Ing.
>> Technical Specialist / Post-Doc
>>
>> UNIVERSITÉ DU LUXEMBOURG
>>
>> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
>> Campus Belval | House of Biomedicine
>> 6, avenue du Swing
>> L-4367 Belvaux
>> T: +352 46 66 44 6124 <+352%2046%2066%2044%206124>
>> F: +352 46 66 44 6949 <+352%2046%2066%2044%206949>
>> http://www.uni.lu/lcsb
>>
>> [image: Facebook]   [image: Twitter]
>>   [image: Google Plus]
>>   [image: Linkedin]
>>   [image: skype]
>> 
>>
>> 
>> This message is confidential and may contain privileged information.
>> It is intended for the named recipient only.
>> If you receive it in error please notify me and permanently delete the
>> original message and any copies.
>> 
>>
>>
>> On 6 Mar 2017, at 09:47, Sandro Bonazzola  wrote:
>>
>>
>>
>> On Mon, Mar 6, 2017 at 9:46 AM, Sandro Bonazzola 
>> wrote:
>>
>>>
>>>
>>> On Mon, Mar 6, 2017 at 12:18 AM, Christophe TREFOIS <
>>> christophe.tref...@uni.lu> wrote:
>>>
 Hi,

 Is 4.1.0 still recommneded an upgrade from 4.0.6 in production or
 should we wait for 4.1.1 to comee out?

 100+ critical bugs fixed sounds good but doesnt really encourage
 upgrading to 4.1.0

 thoughts?

>>>
>>> Note that between 4.0.6 and 4.1.0 there were ~1100 bugfix+enanchement
>>> fixed and in 4.1.1 there will be other ~400 bugfix+enhancements
>>> Being the 4.1.1 release scheduled in ~1 week, I would wait for it.
>>>
>>
>> Or you can upgrade right now to the release candidate and help us testing
>> it :-)
>>
>>
>>
>>>
>>>
>>>

 Christophe

 On 3 Mar 2017, at 14:48, Sandro Bonazzola  wrote:


 The oVirt Project is pleased to announce the availability of the First
 Release Candidate of oVirt 4.1.1 for testing, as of March 3rd, 2017

 This is pre-release software. Please take a look at our community
 page[1]
 to know how to ask questions and interact with developers and users.
 All issues or bugs should be reported via oVirt Bugzilla[2].
 This pre-release should not to be used in production.

 This update is the first release candidate of the first in a series of
 stabilization updates to the 4.1 series.
 4.1.1 brings 26 enhancements and more than 350 bugfixes,
 including more than 130 high or urgent
 severity fixes, on top of oVirt 4.1 series

 This release is available now for:
 * Fedora 24 (tech preview)
 * Red Hat Enterprise Linux 7.3 or later
 * CentOS Linux (or similar) 7.3 or later

 This release supports Hypervisor Hosts running:
 * Red Hat Enterprise Linux 7.3 or later
 * CentOS Linux (or similar) 7.3 or later
 * Fedora 24 (tech preview)

 See the release notes draft [3] for installation / upgrade instructions
 and
 a list of new features and bugs fixed.

 Notes:
 - oVirt Live has been already built [4]
 - oVirt Node and Appliance has not been built for this release due to
 build issues we're still investigating.

 Additional Resources:
 * Read more about the oVirt 4.1.1 release highlights:
 http://www.ovirt.org/release/4.1.1/
 * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
 * Check out the latest project news on the oVirt blog:
 http://www.ovirt.org/blog/

 [1] https://www.ovirt.org/community/
 [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
 [3] http://www.ovirt.org/release/4.1.1/
 [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
>>

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Sandro Bonazzola 
On Mon, Mar 6, 2017 at 9:49 AM, Christophe TREFOIS <
christophe.tref...@uni.lu> wrote:

> Hi Sandro,
>
> We upgraded now to 4.1.0, just have to upgrade now the hosts.
>
> We don’t have test env, so we’re in prod.
>
> If we encounter some bugs fixed in 4.1.1, how could get to 4.1.1 RC?
>

For some reason the website has not been updated (I already opened a github
issue about that).
You can find updated release notes with instructions here.
https://github.com/oVirt/ovirt-site/blob/b24c3f60f26cf27054bd7dfcd9cc4d6d52005a19/source/release/4.1.1/index.html.md




>
> Thanks,
>
> --
>
> Dr Christophe Trefois, Dipl.-Ing.
> Technical Specialist / Post-Doc
>
> UNIVERSITÉ DU LUXEMBOURG
>
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine
> 6, avenue du Swing
> L-4367 Belvaux
> T: +352 46 66 44 6124 <+352%2046%2066%2044%206124>
> F: +352 46 66 44 6949 <+352%2046%2066%2044%206949>
> http://www.uni.lu/lcsb
>
> [image: Facebook]   [image: Twitter]
>   [image: Google Plus]
>   [image: Linkedin]
>   [image: skype]
> 
>
> 
> This message is confidential and may contain privileged information.
> It is intended for the named recipient only.
> If you receive it in error please notify me and permanently delete the
> original message and any copies.
> 
>
>
> On 6 Mar 2017, at 09:47, Sandro Bonazzola  wrote:
>
>
>
> On Mon, Mar 6, 2017 at 9:46 AM, Sandro Bonazzola 
> wrote:
>
>>
>>
>> On Mon, Mar 6, 2017 at 12:18 AM, Christophe TREFOIS > uni.lu> wrote:
>>
>>> Hi,
>>>
>>> Is 4.1.0 still recommneded an upgrade from 4.0.6 in production or should
>>> we wait for 4.1.1 to comee out?
>>>
>>> 100+ critical bugs fixed sounds good but doesnt really encourage
>>> upgrading to 4.1.0
>>>
>>> thoughts?
>>>
>>
>> Note that between 4.0.6 and 4.1.0 there were ~1100 bugfix+enanchement
>> fixed and in 4.1.1 there will be other ~400 bugfix+enhancements
>> Being the 4.1.1 release scheduled in ~1 week, I would wait for it.
>>
>
> Or you can upgrade right now to the release candidate and help us testing
> it :-)
>
>
>
>>
>>
>>
>>>
>>> Christophe
>>>
>>> On 3 Mar 2017, at 14:48, Sandro Bonazzola  wrote:
>>>
>>>
>>> The oVirt Project is pleased to announce the availability of the First
>>> Release Candidate of oVirt 4.1.1 for testing, as of March 3rd, 2017
>>>
>>> This is pre-release software. Please take a look at our community page[1]
>>> to know how to ask questions and interact with developers and users.
>>> All issues or bugs should be reported via oVirt Bugzilla[2].
>>> This pre-release should not to be used in production.
>>>
>>> This update is the first release candidate of the first in a series of
>>> stabilization updates to the 4.1 series.
>>> 4.1.1 brings 26 enhancements and more than 350 bugfixes,
>>> including more than 130 high or urgent
>>> severity fixes, on top of oVirt 4.1 series
>>>
>>> This release is available now for:
>>> * Fedora 24 (tech preview)
>>> * Red Hat Enterprise Linux 7.3 or later
>>> * CentOS Linux (or similar) 7.3 or later
>>>
>>> This release supports Hypervisor Hosts running:
>>> * Red Hat Enterprise Linux 7.3 or later
>>> * CentOS Linux (or similar) 7.3 or later
>>> * Fedora 24 (tech preview)
>>>
>>> See the release notes draft [3] for installation / upgrade instructions
>>> and
>>> a list of new features and bugs fixed.
>>>
>>> Notes:
>>> - oVirt Live has been already built [4]
>>> - oVirt Node and Appliance has not been built for this release due to
>>> build issues we're still investigating.
>>>
>>> Additional Resources:
>>> * Read more about the oVirt 4.1.1 release highlights:http://www.ovirt.or
>>> g/release/4.1.1/
>>> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
>>> * Check out the latest project news on the oVirt blog:
>>> http://www.ovirt.org/blog/
>>>
>>> [1] https://www.ovirt.org/community/
>>> [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
>>> [3] http://www.ovirt.org/release/4.1.1/
>>> [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
>>>
>>>
>>>
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at redhat.com
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://l

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Christophe TREFOIS 
Hi Sandro,

We upgraded now to 4.1.0, just have to upgrade now the hosts.

We don’t have test env, so we’re in prod.

If we encounter some bugs fixed in 4.1.1, how could get to 4.1.1 RC?

Thanks,

--

Dr Christophe Trefois, Dipl.-Ing.
Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine
6, avenue du Swing
L-4367 Belvaux
T: +352 46 66 44 6124
F: +352 46 66 44 6949
http://www.uni.lu/lcsb

[Facebook]  [Twitter] 
   [Google Plus] 
   [Linkedin] 
   [skype] 



This message is confidential and may contain privileged information.
It is intended for the named recipient only.
If you receive it in error please notify me and permanently delete the original 
message and any copies.




On 6 Mar 2017, at 09:47, Sandro Bonazzola 
mailto:sbona...@redhat.com>> wrote:



On Mon, Mar 6, 2017 at 9:46 AM, Sandro Bonazzola 
mailto:sbona...@redhat.com>> wrote:


On Mon, Mar 6, 2017 at 12:18 AM, Christophe TREFOIS 
mailto:christophe.tref...@uni.lu>> wrote:
Hi,

Is 4.1.0 still recommneded an upgrade from 4.0.6 in production or should we 
wait for 4.1.1 to comee out?

100+ critical bugs fixed sounds good but doesnt really encourage upgrading to 
4.1.0

thoughts?

Note that between 4.0.6 and 4.1.0 there were ~1100 bugfix+enanchement fixed and 
in 4.1.1 there will be other ~400 bugfix+enhancements
Being the 4.1.1 release scheduled in ~1 week, I would wait for it.

Or you can upgrade right now to the release candidate and help us testing it :-)





Christophe

On 3 Mar 2017, at 14:48, Sandro Bonazzola 
mailto:sbona...@redhat.com>> wrote:


The oVirt Project is pleased to announce the availability of the First
Release Candidate of oVirt 4.1.1 for testing, as of March 3rd, 2017

This is pre-release software. Please take a look at our community page[1]
to know how to ask questions and interact with developers and users.
All issues or bugs should be reported via oVirt Bugzilla[2].
This pre-release should not to be used in production.

This update is the first release candidate of the first in a series of
stabilization updates to the 4.1 series.
4.1.1 brings 26 enhancements and more than 350 bugfixes,
including more than 130 high or urgent
severity fixes, on top of oVirt 4.1 series

This release is available now for:
* Fedora 24 (tech preview)
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 24 (tech preview)

See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Live has been already built [4]
- oVirt Node and Appliance has not been built for this release due to build 
issues we're still investigating.

Additional Resources:
* Read more about the oVirt 4.1.1 release 
highlights:http://www.ovirt.org/release/4.1.1/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1.1/
[4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/



--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com



--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

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

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Sandro Bonazzola 
On Mon, Mar 6, 2017 at 9:46 AM, Sandro Bonazzola 
wrote:

>
>
> On Mon, Mar 6, 2017 at 12:18 AM, Christophe TREFOIS <
> christophe.tref...@uni.lu> wrote:
>
>> Hi,
>>
>> Is 4.1.0 still recommneded an upgrade from 4.0.6 in production or should
>> we wait for 4.1.1 to comee out?
>>
>> 100+ critical bugs fixed sounds good but doesnt really encourage
>> upgrading to 4.1.0
>>
>> thoughts?
>>
>
> Note that between 4.0.6 and 4.1.0 there were ~1100 bugfix+enanchement
> fixed and in 4.1.1 there will be other ~400 bugfix+enhancements
> Being the 4.1.1 release scheduled in ~1 week, I would wait for it.
>

Or you can upgrade right now to the release candidate and help us testing
it :-)



>
>
>
>>
>> Christophe
>>
>> On 3 Mar 2017, at 14:48, Sandro Bonazzola  wrote:
>>
>>
>> The oVirt Project is pleased to announce the availability of the First
>> Release Candidate of oVirt 4.1.1 for testing, as of March 3rd, 2017
>>
>> This is pre-release software. Please take a look at our community page[1]
>> to know how to ask questions and interact with developers and users.
>> All issues or bugs should be reported via oVirt Bugzilla[2].
>> This pre-release should not to be used in production.
>>
>> This update is the first release candidate of the first in a series of
>> stabilization updates to the 4.1 series.
>> 4.1.1 brings 26 enhancements and more than 350 bugfixes,
>> including more than 130 high or urgent
>> severity fixes, on top of oVirt 4.1 series
>>
>> This release is available now for:
>> * Fedora 24 (tech preview)
>> * Red Hat Enterprise Linux 7.3 or later
>> * CentOS Linux (or similar) 7.3 or later
>>
>> This release supports Hypervisor Hosts running:
>> * Red Hat Enterprise Linux 7.3 or later
>> * CentOS Linux (or similar) 7.3 or later
>> * Fedora 24 (tech preview)
>>
>> See the release notes draft [3] for installation / upgrade instructions
>> and
>> a list of new features and bugs fixed.
>>
>> Notes:
>> - oVirt Live has been already built [4]
>> - oVirt Node and Appliance has not been built for this release due to
>> build issues we're still investigating.
>>
>> Additional Resources:
>> * Read more about the oVirt 4.1.1 release highlights:http://www.ovirt.or
>> g/release/4.1.1/
>> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
>> * Check out the latest project news on the oVirt blog:
>> http://www.ovirt.org/blog/
>>
>> [1] https://www.ovirt.org/community/
>> [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
>> [3] http://www.ovirt.org/release/4.1.1/
>> [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
>>
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ANN] oVirt 4.1.1 First Release Candidate

2017-03-06 Thread Sandro Bonazzola 
On Mon, Mar 6, 2017 at 12:18 AM, Christophe TREFOIS <
christophe.tref...@uni.lu> wrote:

> Hi,
>
> Is 4.1.0 still recommneded an upgrade from 4.0.6 in production or should
> we wait for 4.1.1 to comee out?
>
> 100+ critical bugs fixed sounds good but doesnt really encourage upgrading
> to 4.1.0
>
> thoughts?
>

Note that between 4.0.6 and 4.1.0 there were ~1100 bugfix+enanchement fixed
and in 4.1.1 there will be other ~400 bugfix+enhancements
Being the 4.1.1 release scheduled in ~1 week, I would wait for it.



>
> Christophe
>
> On 3 Mar 2017, at 14:48, Sandro Bonazzola  wrote:
>
>
> The oVirt Project is pleased to announce the availability of the First
> Release Candidate of oVirt 4.1.1 for testing, as of March 3rd, 2017
>
> This is pre-release software. Please take a look at our community page[1]
> to know how to ask questions and interact with developers and users.
> All issues or bugs should be reported via oVirt Bugzilla[2].
> This pre-release should not to be used in production.
>
> This update is the first release candidate of the first in a series of
> stabilization updates to the 4.1 series.
> 4.1.1 brings 26 enhancements and more than 350 bugfixes,
> including more than 130 high or urgent
> severity fixes, on top of oVirt 4.1 series
>
> This release is available now for:
> * Fedora 24 (tech preview)
> * Red Hat Enterprise Linux 7.3 or later
> * CentOS Linux (or similar) 7.3 or later
>
> This release supports Hypervisor Hosts running:
> * Red Hat Enterprise Linux 7.3 or later
> * CentOS Linux (or similar) 7.3 or later
> * Fedora 24 (tech preview)
>
> See the release notes draft [3] for installation / upgrade instructions and
> a list of new features and bugs fixed.
>
> Notes:
> - oVirt Live has been already built [4]
> - oVirt Node and Appliance has not been built for this release due to
> build issues we're still investigating.
>
> Additional Resources:
> * Read more about the oVirt 4.1.1 release highlights:http://www.ovirt.
> org/release/4.1.1/
> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
> * Check out the latest project news on the oVirt blog:
> http://www.ovirt.org/blog/
>
> [1] https://www.ovirt.org/community/
> [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
> [3] http://www.ovirt.org/release/4.1.1/
> [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Nested Virtualization

2017-03-06 Thread Luca 'remix_tj' Lorenzetto 
On Sun, Mar 5, 2017 at 2:43 PM, Barak Korren  wrote:
> oVirt system tests are indeed using nested virtualization, but it is
> done to run oVirt nested on top of a stand-alone KVM host, and not to
> run nested stuff on top of oVirt.
>
> The steps Fred specified can be done manually on all hosts, but oVirt
> offers a slightly more automated alternative. Simply install the
> following vdsm hooks (available as packages) on all hosts:
>
> vdsm-hook-macspoof
> vdsm-hook-nestedvt
>
> And then reboot the hosts (You will need to put hosts into maintenance
> mode to do that).
>

Hello,

the packages you're referring are not available through yum on hosts.
I've seen that only specific packages are included from repos, does
these packages are excluded?

Luca



-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] lvscan on rhv host

2017-03-06 Thread Nir Soffer 
On Mon, Mar 6, 2017 at 1:03 AM, Marcin Kruk  wrote:

Please reply to the list, other users may find this discussion valuable.

> 1. perfect and clear explanation
> 2. Could you explain "These are probably OVF_STORE volumes, used to keep vms
> ovs.", what is vms ovs,
> and what valuable information is in te ovf file which you extracted?

OVF is standard format for describing a VM:
https://en.wikipedia.org/wiki/Open_Virtualization_Format

All the VM that have a disk on a storage domain are stored in
the OVF_STORE disks using OVF format, so you can restore
all the VM from storage if you lost your engine database.

Or, if you want to move entire storage domain from one setup to another,
you can detach the storage domain from one setup, attach to the other
setup, and import all the VMs.

The OVF is also used by hosted engine to obtain engine vm setup from
storage, and start the engine vm after a host is rebooted.

> 3. perfect and clear
> Thank you
>
> 2017-03-05 12:32 GMT+01:00 Nir Soffer :
>>
>> On Sun, Mar 5, 2017 at 10:08 AM, Marcin Kruk 
>> wrote:
>> > VDSM side, means RHV HOST side, right?
>> > I missed LVM tags, so the command:
>> > lvs -o vg_name,name,lv_tags is very helpful, thanks.
>> >
>> > 1. Is it a tool in command line to show: disk ID, alias, atached to
>> > fields?
>>
>> No, you need to extract this info manually.
>>
>> Here is an example
>>
>> # lvs -o lv_name,size,attr,tags aed577ea-d1ca-4ebe-af80-f852c7ce59bb
>>   LV   LSize   Attr   LV Tags
>>   91799827-85b8-450d-a521-42de12fa08e6   1.00g -wi-ao
>>
>> IU_db343be2-f709-4835-b1c5-a1bbdb650b2a,MD_8,PU_93331705-46be-4cb8-9dc2-c1559843fd4a
>>   93331705-46be-4cb8-9dc2-c1559843fd4a   3.00g -wi-ao
>>
>> IU_239d9e96-ad7d-4a7d-83af-d593877db11b,MD_7,PU_----
>>   dfbf69fc-3371-42d4-8298-415a6ad4244a 128.00m -wi---
>>
>> IU_7324cafc-905f-475e-8217-1a919bcca9e9,MD_5,PU_----
>>   ea556b30-e62b-4d66-b832-459a5dd01890 128.00m -wi---
>>
>> IU_aab45dbc-c016-4990-b834-ce455bbc4fef,MD_4,PU_----
>>   ids  128.00m -wi-ao
>>   inbox128.00m -wi-a-
>>   leases 2.00g -wi-a-
>>   master 1.00g -wi-ao
>>   metadata 512.00m -wi-a-
>>   outbox   128.00m -wi-a-
>>   xleases1.00g -wi-a-
>>
>> What is dfbf69fc-3371-42d4-8298-415a6ad4244a?
>>
>> MD_5 means this volume metadata is at offset 5 * 512 in
>> 143dc2d0-8e1a-4b95-a306-2a26a7b4832f metadata
>>
>> # dd if=/dev/aed577ea-d1ca-4ebe-af80-f852c7ce59bb/metadata bs=512 count=1
>> skip=5
>>
>> # dd if=/dev/aed577ea-d1ca-4ebe-af80-f852c7ce59bb/metadata bs=512 count=1
>> skip=5
>> DOMAIN=aed577ea-d1ca-4ebe-af80-f852c7ce59bb
>> CTIME=1487525999
>> FORMAT=RAW
>> DISKTYPE=2
>> LEGALITY=LEGAL
>> SIZE=262144
>> VOLTYPE=LEAF
>> DESCRIPTION={"Updated":true,"Size":30720,"Last Updated":"Fri Feb 24
>> 20:49:24 EST 2017","Storage
>> Domains":[{"uuid":"aed577ea-d1ca-4ebe-af80-f852c7ce59bb"}],"Disk
>> Description":"OVF_STORE"}
>> IMAGE=7324cafc-905f-475e-8217-1a919bcca9e9
>> PUUID=----
>> MTIME=0
>> POOL_UUID=
>> TYPE=PREALLOCATED
>> GEN=0
>> EOF
>> 1+0 records in
>> 1+0 records out
>> 512 bytes (512 B) copied, 0.00146441 s, 350 kB/s
>>
>> So this is OVF_STORE disk, see bellow
>>
>> >
>> > 2. I found information about metadata, outbox etc volumes,
>> > but I can not find info about lvm volumes with 128 MiB size.
>> > Are these any metadata volumes? ex: from lvscan:
>> > ACTIVE
>> >
>> > '/dev/b41214a0-4748-47a8-85f2-9ad1e573ab10/57e904c5-3267-4d94-a52c-babb06912d90'
>> > [128.00 MiB] inherit' [128.00 MiB] inherit?
>>
>> These are probably OVF_STORE volumes, used to keep vms ovs.
>>
>> You can extract the data from these volumes like this:
>>
>> lvchange -ay
>> aed577ea-d1ca-4ebe-af80-f852c7ce59bb/dfbf69fc-3371-42d4-8298-415a6ad4244a
>>
>> # tar tvf
>> /dev/aed577ea-d1ca-4ebe-af80-f852c7ce59bb/dfbf69fc-3371-42d4-8298-415a6ad4244a
>> -rw-r--r-- 0/0 138 2017-02-25 03:49 info.json
>> -rw-r--r-- 0/0   11068 2017-02-25 03:49
>> 55e347d5-4074-4408-b782-c43011483845.ovf
>> -rw-r--r-- 0/0   10306 2017-02-25 03:49
>> bcb03d22-0799-4b0e-bcb3-f69954e6f5eb.ovf
>>
>> # tar xvf
>> /dev/aed577ea-d1ca-4ebe-af80-f852c7ce59bb/dfbf69fc-3371-42d4-8298-415a6ad4244a
>> bcb03d22-0799-4b0e-bcb3-f69954e6f5eb.ovf
>> bcb03d22-0799-4b0e-bcb3-f69954e6f5eb.ovf
>>
>> # dd if=bcb03d22-0799-4b0e-bcb3-f69954e6f5eb.ovf bs=512 count=1
>> > xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1/";
>>
>> xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData";
>>
>> xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData";
>> xmlns:xsi="http://www.w3.org/2001/XMLSc

[ovirt-users] Ubuntu VM does not complete reboot cycle without Console Open

2017-03-06 Thread Anantha Raghava 

Hi,

I have been observing that Ubuntu Precise VM, if restarted using a 
crontab at a given time, stops at the OS / Kernel Selection screen and 
does not complete the reboot. If we issue the reboot command with 
Console open, the same command works without any issues and the VM boots 
properly. This issue happens only with Ubuntu Precise and not with 
Trusty or Xeniel or even with any of Rehat distributions or CentOS.


Interestingly, it doesn't happen with VMWare ESXi.

I also read somewhere that this issue is with VDSM 3.6 and it seems to 
continue with VDSM 4 as well.


Any suggestions in this regard.

--

Thanks & Regards,


Anantha Raghava

eXzaTech Consulting And Services Pvt. Ltd.

DISCLAIMER:
This e-mail communication and any attachments may be privileged and 
confidential to eXza Technology Consulting & Services, and are intended 
only for the use of the recipients named above If you are not the 
addressee you may not copy, forward, disclose or use any part of it. If 
you have received this message in error, please delete it and all copies 
from your system and notify the sender immediately by return e-mail. 
Internet communications cannot be guaranteed to be timely, secure, error 
or virus-free. The sender does not accept liability for any errors or 
omissions.



Do not print this e-mail unless required. Save Paper & trees.

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