date:20160929

On Thu, Sep 29, 2016 at 5:26 PM, Chris Adams  wrote:

> Once upon a time, Simone Tiraboschi  said:
> > unfortunately moving an existing hosted-engine env from one storage kind
> to
> > another (without manually touching the engine DB) is currently not
> > supported. Please see:
> > http://lists.ovirt.org/pipermail/users/2016-July/041526.html
>
> I'm digging through this now, as I need to move my oVirt 3.5 setup from
> one storage array to another (both iSCSI), including the hosted engine.
>
> Reading this:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21
>
> it sounds like that's not currently possible (at least with 3.5).  Is
> that correct?  I was planning to follow this process:
>
> https://www.ovirt.org/documentation/admin-guide/hosted-engine-backup-and-
> restore/
>
> which says "point to the new shared storage" - will that not work?
>
>
The issue is that the engine DB backup you are going to restore already
contains a reference to the previous hosted-engine storage domain and to
the previous hosted-engine VM and so on and so the auto-import procedure to
have the engine VM looking up for its own infrastructure will not trigger.
You have to manually remove them form the DB you restored.


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

Re: [ovirt-users] Ovirt/Gluster replica 3 distributed-replicated problem

2016-09-29 Thread Ravishankar N


On 09/29/2016 08:03 PM, Davide Ferrari wrote:
It's strange, I've tried to trigger the error again by putting vm04 in 
maintenence and stopping the gluster service (from ovirt gui) and now 
the VM starts correctly. Maybe the arbiter indeed blamed the brick 
that was still up before, but how's that possible?


A write from the client on that file (vm image) could have succeeded 
only on vm04 even before you brought it down.


The only (maybe big) difference with the previous, erroneous 
situation, is that before I did maintenence (+ reboot) of 3 of my 4 
hosts, maybe I should have left more time between one reboot and another?


If you did not do anything from the previous run other than to bring the 
node up and things worked, then the file is not in split-brain. Split 
braine'd files need to be resolved before they can be accessed again, 
which apparently did not happen in your case.


-Ravi


2016-09-29 14:16 GMT+02:00 Ravishankar N >:


On 09/29/2016 05:18 PM, Sahina Bose wrote:

Yes, this is a GlusterFS problem. Adding gluster users ML

On Thu, Sep 29, 2016 at 5:11 PM, Davide Ferrari
> wrote:

Hello

maybe this is more glustefs then ovirt related but since
OVirt integrates Gluster management and I'm experiencing the
problem in an ovirt cluster, I'm writing here.

The problem is simple: I have a data domain mappend on a
replica 3 arbiter1 Gluster volume with 6 bricks, like this:

Status of volume: data_ssd
Gluster process TCP Port  RDMA Port  Online  Pid

--
Brick vm01.storage.billy:/gluster/ssd/data/
brick 49153 0  Y   19298
Brick vm02.storage.billy:/gluster/ssd/data/
brick 49153 0  Y   6146
Brick vm03.storage.billy:/gluster/ssd/data/
arbiter_brick 49153 0  Y   6552
Brick vm03.storage.billy:/gluster/ssd/data/
brick 49154 0  Y   6559
Brick vm04.storage.billy:/gluster/ssd/data/
brick 49152 0  Y   6077
Brick vm02.storage.billy:/gluster/ssd/data/
arbiter_brick 49154 0  Y   6153
Self-heal Daemon on localhost   N/A N/A   
Y   30746
Self-heal Daemon on vm01.storage.billy  N/A N/A   
Y   196058
Self-heal Daemon on vm03.storage.billy  N/A N/A   
Y   23205
Self-heal Daemon on vm04.storage.billy  N/A N/A   
Y   8246



Now, I've put in maintenance the vm04 host, from ovirt,
ticking the "Stop gluster" checkbox, and Ovirt didn't
complain about anything. But when I tried to run a new VM it
complained about "storage I/O problem", while the storage
data status was always UP.

Looking in the gluster logs I can see this:

[2016-09-29 11:01:01.556908] I
[glusterfsd-mgmt.c:1596:mgmt_getspec_cbk] 0-glusterfs: No
change in volfile, continuing
[2016-09-29 11:02:28.124151] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done]
0-data_ssd-replicate-1: Failing READ on gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain observed.
[Input/output error]
[2016-09-29 11:02:28.126580] W [MSGID: 108008]
[afr-read-txn.c:244:afr_read_txn] 0-data_ssd-replicate-1:
Unreadable subvolume -1 found with event generation 6 for
gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d. (Possible split-brain)
[2016-09-29 11:02:28.127374] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done]
0-data_ssd-replicate-1: Failing FGETXATTR on gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain observed.
[Input/output error]
[2016-09-29 11:02:28.128130] W [MSGID: 108027]
[afr-common.c:2403:afr_discover_done] 0-data_ssd-replicate-1:
no read subvols for (null)
[2016-09-29 11:02:28.129890] W
[fuse-bridge.c:2228:fuse_readv_cbk] 0-glusterfs-fuse: 8201:
READ => -1 gfid=bf5922b7-19f3-4ce3-98df-71e981ecca8d
fd=0x7f09b749d210 (Input/output error)
[2016-09-29 11:02:28.130824] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done]
0-data_ssd-replicate-1: Failing FSTAT on gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain observed.
[Input/output error]



Does `gluster volume heal data_ssd info split-brain` report that
the file is in split-brain, with vm04 still being down?
If yes, could you provide the extended attributes of this gfid
from all 3 bricks:
getfattr -d -m . -e hex
/path/to/brick/bf/59/bf5922b7-19f3-4ce3-98df-71e981ecca8d

If no, then I'm guessing that it is

[ovirt-users] quick way to see total RAM and CPU count on VM listing

2016-09-29 Thread Nelson Lameiras

Hello oVirt community, 

When listing virtual machines, is there a quick way to see how much RAM/CPU 
each machine has? 

In oVirt 4.0.4, I can see ram/cpu usage in a very nice way, but I can not 
access easily the total RAM and number of CPUs. 
The only way to find this information in GUI is to edit a vm and see the system 
tab (and that's when the "edit" context menu is available, which is not always) 

Am I missing something? 
This information is very usefull and sometimes critical (when migrating VM to 
hosts which are already low on free RAM, specially when balloning is involved) 

I would like to see this information always on screen, like a (un)checkable 
column... does it seem doable ? 
Maybe it would be possible to show it while hoovering the memory/cpu 
information with the mouse ? 

Please forgive me if this is not the rigth place to post this question/request. 

cordialement, regards, 
Nelson LAMEIRAS 

Lyra Network 
Service Projets et Processus 
Tel : +33 (0) 5 32 09 09 70 
109 rue de l’innovation 
31670 Labège - France 
www.lyra-network.com 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt/Gluster replica 3 distributed-replicated problem

It's strange, I've tried to trigger the error again by putting vm04 in
maintenence and stopping the gluster service (from ovirt gui) and now the
VM starts correctly. Maybe the arbiter indeed blamed the brick that was
still up before, but how's that possible?
The only (maybe big) difference with the previous, erroneous situation, is
that before I did maintenence (+ reboot) of 3 of my 4 hosts, maybe I should
have left more time between one reboot and another?

2016-09-29 14:16 GMT+02:00 Ravishankar N :

> On 09/29/2016 05:18 PM, Sahina Bose wrote:
>
> Yes, this is a GlusterFS problem. Adding gluster users ML
>
> On Thu, Sep 29, 2016 at 5:11 PM, Davide Ferrari 
> wrote:
>
>> Hello
>>
>> maybe this is more glustefs then ovirt related but since OVirt integrates
>> Gluster management and I'm experiencing the problem in an ovirt cluster,
>> I'm writing here.
>>
>> The problem is simple: I have a data domain mappend on a replica 3
>> arbiter1 Gluster volume with 6 bricks, like this:
>>
>> Status of volume: data_ssd
>> Gluster process TCP Port  RDMA Port  Online
>> Pid
>> 
>> --
>> Brick vm01.storage.billy:/gluster/ssd/data/
>> brick   49153 0  Y
>> 19298
>> Brick vm02.storage.billy:/gluster/ssd/data/
>> brick   49153 0  Y
>> 6146
>> Brick vm03.storage.billy:/gluster/ssd/data/
>> arbiter_brick   49153 0  Y
>> 6552
>> Brick vm03.storage.billy:/gluster/ssd/data/
>> brick   49154 0  Y
>> 6559
>> Brick vm04.storage.billy:/gluster/ssd/data/
>> brick   49152 0  Y
>> 6077
>> Brick vm02.storage.billy:/gluster/ssd/data/
>> arbiter_brick   49154 0  Y
>> 6153
>> Self-heal Daemon on localhost   N/A   N/AY
>> 30746
>> Self-heal Daemon on vm01.storage.billy  N/A   N/AY
>> 196058
>> Self-heal Daemon on vm03.storage.billy  N/A   N/AY
>> 23205
>> Self-heal Daemon on vm04.storage.billy  N/A   N/AY
>> 8246
>>
>>
>> Now, I've put in maintenance the vm04 host, from ovirt, ticking the "Stop
>> gluster" checkbox, and Ovirt didn't complain about anything. But when I
>> tried to run a new VM it complained about "storage I/O problem", while the
>> storage data status was always UP.
>>
>> Looking in the gluster logs I can see this:
>>
>> [2016-09-29 11:01:01.556908] I [glusterfsd-mgmt.c:1596:mgmt_getspec_cbk]
>> 0-glusterfs: No change in volfile, continuing
>> [2016-09-29 11:02:28.124151] E [MSGID: 108008]
>> [afr-read-txn.c:89:afr_read_txn_refresh_done] 0-data_ssd-replicate-1:
>> Failing READ on gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain
>> observed. [Input/output error]
>> [2016-09-29 11:02:28.126580] W [MSGID: 108008]
>> [afr-read-txn.c:244:afr_read_txn] 0-data_ssd-replicate-1: Unreadable
>> subvolume -1 found with event generation 6 for gfid
>> bf5922b7-19f3-4ce3-98df-71e981ecca8d. (Possible split-brain)
>> [2016-09-29 11:02:28.127374] E [MSGID: 108008]
>> [afr-read-txn.c:89:afr_read_txn_refresh_done] 0-data_ssd-replicate-1:
>> Failing FGETXATTR on gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d:
>> split-brain observed. [Input/output error]
>> [2016-09-29 11:02:28.128130] W [MSGID: 108027]
>> [afr-common.c:2403:afr_discover_done] 0-data_ssd-replicate-1: no read
>> subvols for (null)
>> [2016-09-29 11:02:28.129890] W [fuse-bridge.c:2228:fuse_readv_cbk]
>> 0-glusterfs-fuse: 8201: READ => -1 gfid=bf5922b7-19f3-4ce3-98df-71e981ecca8d
>> fd=0x7f09b749d210 (Input/output error)
>> [2016-09-29 11:02:28.130824] E [MSGID: 108008]
>> [afr-read-txn.c:89:afr_read_txn_refresh_done] 0-data_ssd-replicate-1:
>> Failing FSTAT on gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain
>> observed. [Input/output error]
>>
>
> Does `gluster volume heal data_ssd info split-brain` report that the file
> is in split-brain, with vm04 still being down?
> If yes, could you provide the extended attributes of this gfid from all 3
> bricks:
> getfattr -d -m . -e hex /path/to/brick/bf/59/bf5922b7-
> 19f3-4ce3-98df-71e981ecca8d
>
> If no, then I'm guessing that it is not in actual split-brain (hence the
> 'Possible split-brain' message). If the node you brought down contains the
> only good copy of the file (i.e the other data brick and arbiter are up,
> and the arbiter 'blames' this other brick), all I/O is failed with EIO to
> prevent file from getting into actual split-brain. The heals will happen
> when the good node comes up and I/O should be allowed again in that case.
>
> -Ravi
>
>
> [2016-09-29 11:02:28.133879] W [fuse-bridge.c:767:fuse_attr_cbk]
>> 0-glusterfs-fuse: 8202: FSTAT() /ba2bd397-9222-424d-aecc-eb652
>>

Re: [ovirt-users] VM pauses/hangs after migration

Ok, what I said is not true :( I didn't try to migrate again to the same
host that gave the initial problem, and the problem is still there. The
destination host has no HW problem (at least nothing that the system
reports, maybe I should try with an extensive memtest86) and the source
problem now has no memory issues neither. So, my question is now: how can I
debug this problem? The only difference that this host (vmhost01) has is
that it was the first host installed in my self-hosted engine installation.
But I have already reinstalled it from GUI and menawhile I've upgraded to
4.0.4 from 4.0.3.

Any idea?

2016-09-29 13:59 GMT+02:00 Davide Ferrari :

> Hello
>
> Today I've the faulty DIMMs replaced, started the same VM again and did
> the same migration and this time worked, so it was 100% due to that.
>
> The problem that make me wonder a bit is: if it's the source host with
> memory problem the one which blocks the correct migration, a faulty DIMM
> will force you to stop the VMs running on that host, because you cannot
> simply migrate them away to do the maintenence tasks...
>
>
> 2016-09-29 13:53 GMT+02:00 Tomas Jelinek :
>
>>
>>
>> - Original Message -
>> > From: "Davide Ferrari" 
>> > To: "users" 
>> > Sent: Wednesday, September 28, 2016 2:59:59 PM
>> > Subject: [ovirt-users] VM pauses/hangs after migration
>> >
>> > Hello
>> >
>> > trying to migrate a VM from one host to another, a big VM with 96GB of
>> RAM, I
>> > found that when the migration completes, the VM goes to a paused satte
>> and
>> > cannot be resumed. The libvirt/qemu log it gives is this:
>> >
>> > 2016-09-28T12:18:15.679176Z qemu-kvm: error while loading state section
>> id
>> > 2(ram)
>> > 2016-09-28T12:18:15.680010Z qemu-kvm: load of migration failed:
>> Input/output
>> > error
>> > 2016-09-28 12:18:15.872+: shutting down
>> > 2016-09-28 12:22:21.467+: starting up libvirt version: 1.2.17,
>> package:
>> > 13.el7_2.5 (CentOS BuildSystem < http://bugs.centos.org >,
>> > 2016-06-23-14:23:27, worker1.bsys.centos.org ), qemu version: 2.3.0
>> > (qemu-kvm-ev-2.3.0-31.el7.16.1)
>> > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
>> > QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name
>> front04.billydomain.com -S
>> > -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu Haswell-noTSX -m
>> > size=100663296k,slots=16,maxmem=4294967296k -realtime mlock=off -smp
>> > 32,sockets=16,cores=1,threads=2 -numa node,nodeid=0,cpus=0-31,mem=98304
>> > -uuid 4511d1c0-6607-418f-ae75-34f605b2ad68 -smbios
>> > type=1,manufacturer=oVirt,product=oVirt
>> > Node,version=7-2.1511.el7.centos.2.10,serial=4C4C4544-004A-
>> 3310-8054-B2C04F474432,uuid=4511d1c0-6607-418f-ae75-34f605b2ad68
>> > -no-user-config -nodefaults -chardev
>> > socket,id=charmonitor,path=/var/lib/libvirt/qemu/
>> > domain-front04.billydomain.com/monitor.sock,server,nowait -mon
>> > chardev=charmonitor,id=monitor,mode=control -rtc
>> > base=2016-09-28T14:22:21,driftfix=slew -global
>> > kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
>> > -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
>> > virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x7 -device
>> > virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4
>> -drive
>> > if=none,id=drive-ide0-1-0,readonly=on,format=raw -device
>> > ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
>> > file=/rhev/data-center/0001-0001-0001-0001-03e3/
>> ba2bd397-9222-424d-aecc-eb652c0169d9/images/b5b49d5c-
>> 2378-4639-9469-362e37ae7473/24fd0d3c-309b-458d-9818-
>> 4321023afacf,if=none,id=drive-virtio-disk0,format=qcow2,
>> serial=b5b49d5c-2378-4639-9469-362e37ae7473,cache=none,
>> werror=stop,rerror=stop,aio=threads
>> > -device
>> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virti
>> o-disk0,id=virtio-disk0,bootindex=1
>> > -drive
>> > file=/rhev/data-center/0001-0001-0001-0001-03e3/
>> ba2bd397-9222-424d-aecc-eb652c0169d9/images/f02ac1ce-
>> 52cd-4b81-8b29-f8006d0469e0/ff4e49c6-3084-4234-80a1-
>> 18a67615c527,if=none,id=drive-virtio-disk1,format=raw,
>> serial=f02ac1ce-52cd-4b81-8b29-f8006d0469e0,cache=none,
>> werror=stop,rerror=stop,aio=threads
>> > -device
>> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virti
>> o-disk1,id=virtio-disk1
>> > -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device
>> > virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:
>> 56,bus=pci.0,addr=0x3
>> > -chardev
>> > socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/4
>> 511d1c0-6607-418f-ae75-34f605b2ad68.com.redhat.rhevm.vdsm,server,nowait
>> > -device
>> > virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel
>> 0,id=channel0,name=com.redhat.rhevm.vdsm
>> > -chardev
>> > socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/4
>> 511d1c0-6607-418f-ae75-34f605b2ad68.org.qemu.guest_agent.0,server,nowait
>> > -device
>> >

Re: [ovirt-users] [ANN] oVirt 4.0.5 First Release Candidate is now available

2016-09-29 Thread Kai Wagner


Am 29.09.2016 um 15:33 schrieb Sandro Bonazzola:



On Thu, Sep 29, 2016 at 3:24 PM, Kai Wagner > wrote:


Hi,

something is missing I guess :-)

[3] http://www.ovirt.org/release/4.0.5/
 -> Page not found



Please refresh your browser :-) for some reason from time to time the 
website is not serving newly created pages



Thanks :-)


Am 29.09.2016 um 15:19 schrieb Sandro Bonazzola:

The oVirt Project is pleased to announce the availability of
oVirt 4.0.5 first release candidate for testing, as of September
29th, 2016.

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

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later
* Fedora 23 (tech preview)
* oVirt Next Generation Node 4.0

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 fifth in a
series of
stabilization updates to the 4.0 series.
4.0.5 brings 7 enhancements and 51 bugfixes, including 20 high or
urgent
severity fixes, on top of oVirt 4.0 series
See the release notes [3] for installation / upgrade instructions
and a
list of new features and bugs fixed.

Notes:
* A new oVirt Live ISO is available. [4]
* A new oVirt Next Generation Node will be available soon [4]
(delay due to a huge load on build servers).
* A new oVirt Engine Appliance is available for Red Hat
Enterprise Linux and CentOS Linux (or similar)
* Mirrors[5] might need up to one day to synchronize.

Additional Resources:
* Read more about the oVirt 4.0.5 release
highlights:http://www.ovirt.org/release/4.0.5/

* 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.0.5/

[4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/

[5] http://www.ovirt.org/Repository_mirrors#Current_mirrors



-- 
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



it-novum GmbH i. A. Kai Wagner ●   Team Lead Support & Presales
openATTIC
 _
Unser Newsletter Service: Jetzt Business Open Source News
abonnieren! 


Folgen Sie uns:



Tel: +49 661 103-762
 Fax: +49 661 10317762
 Mail: kai.wag...@it-novum.com


it-novum GmbH • Edelzeller Straße 44 • 36043 Fulda •
http://www.it-novum.com/Handelsregister Amtsgericht Fulda, HRB
1934 • Geschäftsführer: Michael Kienle • Sitz der Gesellschaft:
Fulda Der Inhalt dieser E-Mail ist vertraulich. Wenn Sie nicht der
eigentliche Empfänger sein sollten, informieren Sie bitte sofort
den Absender oder vernichten umgehend diese Mail. Jegliche
unerlaubte Vervielfältigung oder Weiterleitung dieser Mail ist
strengstens verboten. This e-mail may contain confidential and/or
priviledged information. If you are not the intended recepient (or
have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorised copying,
disclosure or

[ovirt-users] Ansible modules supporting oVirt 4

Hi,

we have a great news regarding Ansible modules for oVirt 4 management. As
you may have already noticed in [1] and thanks to Ondra's hard work we were
able to push following modules into Ansible 2.2:

ovirt_auth
  - manages authentication against oVirt engine instance

ovirt_vms
  - manages VM lifecycle
  - manages VM's disks and NICs (more advanced disks and NICs management
will be provided by specialized modules)

ovirt_disks
  - manages VM's disks and floating disks

You can find more details about those modules at [2].

But this is not end of our effort, we are working on other modules that
should cover most of functionality provided by oVirt SDK and hopefully will
be included in Ansible 2.3 (more info also at [2]).

Any feedback on those modules would be very welcome.

Regards

Martin Perina

[1] http://www.ovirt.org/blog/2016/09/manage-ovirt-with-ansible-playbooks/
[2]
http://www.ovirt.org/develop/release-management/features/infra/ansible_modules/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ANN] oVirt 4.0.5 First Release Candidate is now available

2016-09-29 Thread Sandro Bonazzola

On Thu, Sep 29, 2016 at 3:24 PM, Kai Wagner  wrote:

> Hi,
>
> something is missing I guess :-)
>
> [3] http://www.ovirt.org/release/4.0.5/ -> Page not found
>
>
Please refresh your browser :-) for some reason from time to time the
website is not serving newly created pages




> Am 29.09.2016 um 15:19 schrieb Sandro Bonazzola:
>
> The oVirt Project is pleased to announce the availability of oVirt 4.0.5
> first release candidate for testing, as of September 29th, 2016.
>
> This release is available now for:
> * Fedora 23 (tech preview)
> * Red Hat Enterprise Linux 7.2 or later
> * CentOS Linux (or similar) 7.2 or later
>
> This release supports Hypervisor Hosts running:
> * Red Hat Enterprise Linux 7.2 or later
> * CentOS Linux (or similar) 7.2 or later
> * Fedora 23 (tech preview)
> * oVirt Next Generation Node 4.0
>
> 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 fifth in a series of
> stabilization updates to the 4.0 series.
> 4.0.5 brings 7 enhancements and 51 bugfixes, including 20 high or urgent
> severity fixes, on top of oVirt 4.0 series
> See the release notes [3] for installation / upgrade instructions and a
> list of new features and bugs fixed.
>
> Notes:
> * A new oVirt Live ISO is available. [4]
> * A new oVirt Next Generation Node will be available soon [4] (delay due
> to a huge load on build servers).
> * A new oVirt Engine Appliance is available for Red Hat Enterprise Linux
> and CentOS Linux (or similar)
> * Mirrors[5] might need up to one day to synchronize.
>
> Additional Resources:
> * Read more about the oVirt 4.0.5 release highlights:http://www.ovirt.
> org/release/4.0.5/
> * 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.0.5/
> [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/
> [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> it-novum GmbH
> i. A. Kai Wagner   ● Team Lead Support & Presales openATTIC
>  _
>   Unser Newsletter Service: Jetzt Business Open Source News abonnieren!
> 
> 
> Folgen Sie uns: 
>  
> 
> 
> 
> 
> 
>  Tel: +49 661 103-762
> Fax: +49 661 10317762
> Mail: kai.wag...@it-novum.com
> it-novum GmbH • Edelzeller Straße 44 • 36043 Fulda •
> http://www.it-novum.com/
> Handelsregister Amtsgericht Fulda, HRB 1934 • Geschäftsführer: Michael
> Kienle • Sitz der Gesellschaft: Fulda
>
> Der Inhalt dieser E-Mail ist vertraulich. Wenn Sie nicht der eigentliche
> Empfänger sein sollten, informieren Sie bitte sofort den Absender oder
> vernichten umgehend diese Mail. Jegliche unerlaubte Vervielfältigung oder
> Weiterleitung dieser Mail ist strengstens verboten.
> This e-mail may contain confidential and/or priviledged information. If
> you are not the intended recepient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorised copying, disclosure or distribution of material in this e-mail
> is strictly forbidden.
>
>
> ___
> 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

[ovirt-users] WG: High Database Load after updating to oVirt 4.0.4

2016-09-29 Thread Grundmann, Christian

Maybe an side effect off this bug?

https://bugzilla.redhat.com/1302752

I did a restore to 4.0.3 and the timeouts are gone

Von: Grundmann, Christian
Gesendet: Dienstag, 27. September 2016 10:33
An: users@ovirt.org
Betreff: High Database Load after updating to oVirt 4.0.4

After 4.0.4 Update we have a very high database load during startup of VMs
So high that the api calls getting timeouts

I attached the output of
select * from pg_stat_activity


is there a way to downgrade to 4.0.3?

Thx Christian



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

Re: [ovirt-users] [ANN] oVirt 4.0.5 First Release Candidate is now available

2016-09-29 Thread Kai Wagner

Hi,

something is missing I guess :-)

[3] http://www.ovirt.org/release/4.0.5/ -> Page not found

Am 29.09.2016 um 15:19 schrieb Sandro Bonazzola:
The oVirt Project is pleased to announce the availability of oVirt
4.0.5 first release candidate for testing, as of September 29th, 2016.

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

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later
* Fedora 23 (tech preview)
* oVirt Next Generation Node 4.0

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 fifth in a series of
stabilization updates to the 4.0 series.
4.0.5 brings 7 enhancements and 51 bugfixes, including 20 high or urgent
severity fixes, on top of oVirt 4.0 series
See the release notes [3] for installation / upgrade instructions and a
list of new features and bugs fixed.

Notes:
* A new oVirt Live ISO is available. [4]
* A new oVirt Next Generation Node will be available soon [4] (delay
due to a huge load on build servers).
* A new oVirt Engine Appliance is available for Red Hat Enterprise
Linux and CentOS Linux (or similar)

* Mirrors[5] might need up to one day to synchronize.

Additional Resources:
* Read more about the oVirt 4.0.5 release
highlights:http://www.ovirt.org/release/4.0.5/

* 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.0.5/
[4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/
[5] http://www.ovirt.org/Repository_mirrors#Current_mirrors

--
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

it-novum GmbH
i. A. Kai Wagner - Team Lead Support & Presales openATTIC
_

Tel: +49 661 103-762
Fax: +49 661 10317762
Mail: kai.wag...@it-novum.com

it-novum GmbH • Edelzeller Straße 44 • 36043 Fulda • http://www.it-novum.com/
Handelsregister Amtsgericht Fulda, HRB 1934 • Geschäftsführer: Michael Kienle • Sitz der Gesellschaft: Fulda

Der Inhalt dieser E-Mail ist vertraulich. Wenn Sie nicht der eigentliche Empfänger sein sollten, informieren Sie bitte sofort den Absender oder vernichten umgehend diese Mail. Jegliche unerlaubte Vervielfältigung oder Weiterleitung dieser Mail ist strengstens verboten.
This e-mail may contain confidential and/or priviledged information. If you are not the intended recepient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of material in this e-mail is strictly forbidden.

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

[ovirt-users] oVirt 3.6 and Fedora 24: How to change display resolution?

2016-09-29 Thread Richard Harmonson

I am unable to change the display for a Fedora 24 Workstation using Gnome
3.20 from its default 1024 x 768. I, also, tried a number of spins but the
behavior persist. Installing on a physical desktop does not reproduce the
symptom. Installing CentOS 7 does not reproduce the symptom.

Under the virtual machine "Applications" it shows:

kernel-4.7.4-200.fc24
ovirt-guest-agent-common-1.0.12-3.fc24
xorg-x11-drv-qxl-0.1.4-7.fc24
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.0.5 First Release Candidate is now available

2016-09-29 Thread Sandro Bonazzola

The oVirt Project is pleased to announce the availability of oVirt 4.0.5
first release candidate for testing, as of September 29th, 2016.

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

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later
* Fedora 23 (tech preview)
* oVirt Next Generation Node 4.0

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 fifth in a series of
stabilization updates to the 4.0 series.
4.0.5 brings 7 enhancements and 51 bugfixes, including 20 high or urgent
severity fixes, on top of oVirt 4.0 series
See the release notes [3] for installation / upgrade instructions and a
list of new features and bugs fixed.

Notes:
* A new oVirt Live ISO is available. [4]
* A new oVirt Next Generation Node will be available soon [4] (delay due to
a huge load on build servers).
* A new oVirt Engine Appliance is available for Red Hat Enterprise Linux
and CentOS Linux (or similar)
* Mirrors[5] might need up to one day to synchronize.

Additional Resources:
* Read more about the oVirt 4.0.5 release highlights:
http://www.ovirt.org/release/4.0.5/
* 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.0.5/
[4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/
[5] http://www.ovirt.org/Repository_mirrors#Current_mirrors


-- 
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 4.0.x - hosted-engine was not starting properly

2016-09-29 Thread Gervais de Montbrun

Hi Simone,

Thanks for the info. I'll look at the solution that you suggested.

Cheers,
Gervais



> On Sep 29, 2016, at 10:01 AM, Simone Tiraboschi  wrote:
> 
> 
> 
> On Thu, Sep 29, 2016 at 2:51 PM, Gervais de Montbrun  > wrote:
> Hi Martin,
> 
> The entropy was super low. Somewhere around 140. I installed and configured 
> haveged.service to start at bootup, reverted my apache changes... After a 
> reboot, my systemctl status still says that there are 7 services queued (note 
> that I erroneously said degraded in my previous email - the services are, in 
> fact, queued), but the oVirt GUI comes up almost immediately and everything 
> seems to be great.
> 
> 
> Take care that using havaged on a VM should not be considered a good source 
> of entropy and the oVirt PKi is managed by the engine.
> http://security.stackexchange.com/questions/34523/is-it-appropriate-to-use-haveged-as-a-source-of-entropy-on-virtual-machines
>  
> 
> 
> A better approach is the virtio-rng paravirtualised rng driver as for patch 
> https://gerrit.ovirt.org/#/c/62334/ 
> 
>  
> Thank you for the tip. You solved my issue.
> 
> Cheers,
> Gervais
> 
> 
> 
>> On Sep 29, 2016, at 7:47 AM, Martin Perina > > wrote:
>> 
>> Hi,
>> 
>> please take a look at my inline comments:
>> 
>> On Tue, Sep 27, 2016 at 7:23 PM, Gervais de Montbrun > > wrote:
>> Hey All,
>> 
>> Since updating to 4.0.x of oVirt, I have had an issue with my hosted engine. 
>> After a some poking around, I think I have figured out my issue and thought 
>> I would share to see what others think.
>> The issue has existed with 4.0, 4.0.1, 4.0.2, 4.0.3, and still exists in 
>> 4.0.4.
>> 
>> Description:
>> When my hosted engine starts it reports that it is in a degraded state with 
>> 7 or 8 services still not started when I run systemctl status. It takes 
>> about 6 or 7 minutes to eventually start all the services and come online. 
>> If I don't set my cluster to Global-Maintenance mode it eventually thinks 
>> that my hosted-engine needs to be rebooted and restarts it before it can 
>> start everything.
>> 
>> Could you please share with us logs gathered by ovirt-log-collector?
>> 
>> It's just a guess but could you please take a look if you HE VM has enough 
>> entropy?
>> 
>>   cat /proc/sys/kernel/random/entropy_avail
>> 
>> If the value is low (below or around 200),  you really need to install and 
>> configure some entropy generator such as haveged
>> 
>> 
>> Solution:
>> I realized that Apache was the culprit and found that the proxy to the 
>> ovirt-engine in /etc/httpd/conf.d/z-ovirt-engine-proxy.conf has a super long 
>> timeout with many retries. I changed the settings and now everything works 
>> for me.
>> 
>> -> Before change:
>> > ^/(ovirt-engine($|/)|api($|/)|RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|rhevm.ssh.key.txt$)>
>> ProxyPassMatch ajp://127.0.0.1:8702 <> timeout=3600 retry=5
>> 
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css text/html 
>> text/xml text/json application/xml application/json application/x-yaml
>> 
>> 
>> 
>> -> After change:
>> 
>> ProxyPassMatch ajp://127.0.0.1:8702 <> timeout=5 retry=2
>> 
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css text/html 
>> text/xml text/json application/xml application/json application/x-yaml
>> 
>> 
>> 
>> This one is correct for 4.0, not sure why it was not updated during 
>> upgrade from 3.6. @Simone?
>>  
>> 
>> If I read the timeout settings correctly, it will wait 60 minutes with 5 
>> retries. 5 hours is way too long for my little server to hold onto all those 
>> apache processes.
>> The change I made allows for there to be an error, and also releases 
>> apache's hold on the process. Once everything is ready, apache is ready to 
>> serve requests and everything/everyone is happy. Before making the change, I 
>> just get a whitescreen in my browser and then nothing works until I restart 
>> Apache (or I end up in an endless loop of ovirt-ha services restarting my 
>> hosted-engine.
>> 
>> Well, if you have an issue with too many apache processes waiting for 
>> engine to respond, then there's some issue in engine. As I wrote above 
>> please share the logs with us and check entropy.
>> 
>> Thanks
>> 
>> Martin Perina
>>  
>> 
>> I noticed that this setting reverts to the original setting, so oVirt must 
>> be writing this file. Perhaps these number can be changed in oVirt? If not, 
>> I will just setup and ansible play to revert the settings with working 
>> values and restart apache on my engine.
>> :-)
>> 
>>

Re: [ovirt-users] oVirt 4.0.x - hosted-engine was not starting properly

2016-09-29 Thread Gervais de Montbrun

Hi Simone,

Yes... I guess it was not clear in my original email. I changed the numbers 
myself to lower the timeout and retries. With them set as they were set by 
ovirt (timeout=3600 retry=5) things were not working for me. 

Cheers,
Gervais



> On Sep 29, 2016, at 10:04 AM, Simone Tiraboschi  wrote:
> 
> 
> 
> On Thu, Sep 29, 2016 at 12:47 PM, Martin Perina  > wrote:
> Hi,
> 
> please take a look at my inline comments:
> 
> On Tue, Sep 27, 2016 at 7:23 PM, Gervais de Montbrun  > wrote:
> Hey All,
> 
> Since updating to 4.0.x of oVirt, I have had an issue with my hosted engine. 
> After a some poking around, I think I have figured out my issue and thought I 
> would share to see what others think.
> The issue has existed with 4.0, 4.0.1, 4.0.2, 4.0.3, and still exists in 
> 4.0.4.
> 
> Description:
> When my hosted engine starts it reports that it is in a degraded state with 7 
> or 8 services still not started when I run systemctl status. It takes about 6 
> or 7 minutes to eventually start all the services and come online. If I don't 
> set my cluster to Global-Maintenance mode it eventually thinks that my 
> hosted-engine needs to be rebooted and restarts it before it can start 
> everything.
> 
> Could you please share with us logs gathered by ovirt-log-collector?
> 
> It's just a guess but could you please take a look if you HE VM has enough 
> entropy?
> 
>   cat /proc/sys/kernel/random/entropy_avail
> 
> If the value is low (below or around 200),  you really need to install and 
> configure some entropy generator such as haveged
> 
> 
> Solution:
> I realized that Apache was the culprit and found that the proxy to the 
> ovirt-engine in /etc/httpd/conf.d/z-ovirt-engine-proxy.conf has a super long 
> timeout with many retries. I changed the settings and now everything works 
> for me.
> 
> -> Before change:
>  ^/(ovirt-engine($|/)|api($|/)|RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|rhevm.ssh.key.txt$)>
> ProxyPassMatch ajp://127.0.0.1:8702 <> timeout=3600 retry=5
> 
> 
> AddOutputFilterByType DEFLATE text/javascript text/css text/html 
> text/xml text/json application/xml application/json application/x-yaml
> 
> 
> 
> -> After change:
> 
> ProxyPassMatch ajp://127.0.0.1:8702 <> timeout=5 retry=2
> 
> 
> AddOutputFilterByType DEFLATE text/javascript text/css text/html 
> text/xml text/json application/xml application/json application/x-yaml
> 
> 
> 
> This one is correct for 4.0, not sure why it was not updated during 
> upgrade from 3.6. @Simone?
> 
> 
> Honestly it's
> 
> ProxyPassMatch ajp://127.0.0.1:8702  
> timeout=3600 retry=5
> 
> 
> AddOutputFilterByType DEFLATE text/javascript text/css text/html 
> text/xml text/json application/xml application/json application/x-yaml
> 
> 
> also on a fresh 4.0 engine from our latest engine-appliance.
>  
> 
> If I read the timeout settings correctly, it will wait 60 minutes with 5 
> retries. 5 hours is way too long for my little server to hold onto all those 
> apache processes.
> The change I made allows for there to be an error, and also releases apache's 
> hold on the process. Once everything is ready, apache is ready to serve 
> requests and everything/everyone is happy. Before making the change, I just 
> get a whitescreen in my browser and then nothing works until I restart Apache 
> (or I end up in an endless loop of ovirt-ha services restarting my 
> hosted-engine.
> 
> Well, if you have an issue with too many apache processes waiting for engine 
> to respond, then there's some issue in engine. As I wrote above please share 
> the logs with us and check entropy.
> 
> Thanks
> 
> Martin Perina
>  
> 
> I noticed that this setting reverts to the original setting, so oVirt must be 
> writing this file. Perhaps these number can be changed in oVirt? If not, I 
> will just setup and ansible play to revert the settings with working values 
> and restart apache on my engine.
> :-)
> 
> Cheers,
> Gervais
> 
> 
> 
> 
> ___
> 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 4.0.x - hosted-engine was not starting properly

On Thu, Sep 29, 2016 at 3:04 PM, Simone Tiraboschi 
wrote:

>
>
> On Thu, Sep 29, 2016 at 12:47 PM, Martin Perina 
> wrote:
>
>> Hi,
>>
>> please take a look at my inline comments:
>>
>> On Tue, Sep 27, 2016 at 7:23 PM, Gervais de Montbrun <
>> gerv...@demontbrun.com> wrote:
>>
>>> Hey All,
>>>
>>> Since updating to 4.0.x of oVirt, I have had an issue with my hosted
>>> engine. After a some poking around, I think I have figured out my issue and
>>> thought I would share to see what others think.
>>> The issue has existed with 4.0, 4.0.1, 4.0.2, 4.0.3, and still exists in
>>> 4.0.4.
>>>
>>> Description:
>>> When my hosted engine starts it reports that it is in a degraded state
>>> with 7 or 8 services still not started when I run systemctl status. It
>>> takes about 6 or 7 minutes to eventually start all the services and come
>>> online. If I don't set my cluster to Global-Maintenance mode it eventually
>>> thinks that my hosted-engine needs to be rebooted and restarts it before it
>>> can start everything.
>>>
>>
>> Could you please share with us logs gathered by ovirt-log-collector?
>>
>> It's just a guess but could you please take a look if you HE VM has
>> enough entropy?
>>
>>   cat /proc/sys/kernel/random/entropy_avail
>>
>> If the value is low (below or around 200),  you really need to install
>> and configure some entropy generator such as haveged
>>
>>
>>> Solution:
>>> I realized that Apache was the culprit and found that the proxy to the
>>> ovirt-engine in /etc/httpd/conf.d/z-ovirt-engine-proxy.conf has a super
>>> long timeout with many retries. I changed the settings and now everything
>>> works for me.
>>>
>>> -> Before change:
>>>
>>> >> RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|
>>> rhevm.ssh.key.txt$)>
>>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5
>>>
>>> 
>>> AddOutputFilterByType DEFLATE text/javascript text/css
>>> text/html text/xml text/json application/xml application/json
>>> application/x-yaml
>>> 
>>> 
>>>
>>>
>>> -> After change:
>>>
>>> 
>>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=5 retry=2
>>>
>>> 
>>> AddOutputFilterByType DEFLATE text/javascript text/css
>>> text/html text/xml text/json application/xml application/json
>>> application/x-yaml
>>> 
>>> 
>>>
>>>
>> This one is correct for 4.0
>> , not sure why it was not updated during upgrade from 3.6. @Simone?
>> 
>>
>
> Honestly it's
> 
> ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5
>
> 
> AddOutputFilterByType DEFLATE text/javascript text/css
> text/html text/xml text/json application/xml application/json
> application/x-yaml
> 
> 
> also on a fresh 4.0 engine from our latest engine-appliance.
>

Right, I missed the timeout/retry option changes. But the important part
is why old configuration (with different LocationMatch) was not overwritten
during upgrade.


>
>>
>>> If I read the timeout settings correctly, it will wait 60 minutes with 5
>>> retries. 5 hours is way too long for my little server to hold onto all
>>> those apache processes.
>>>
>> The change I made allows for there to be an error, and also releases
>>> apache's hold on the process. Once everything is ready, apache is ready to
>>> serve requests and everything/everyone is happy. Before making the change,
>>> I just get a whitescreen in my browser and then nothing works until I
>>> restart Apache (or I end up in an endless loop of ovirt-ha services
>>> restarting my hosted-engine.
>>>
>>
>> Well, if you have an issue with too many apache processes waiting for
>> engine to respond, then there's some issue in engine. As I wrote above
>> please share the logs with us and check entropy.
>>
>> Thanks
>>
>> Martin Perina
>> 
>>
>>
>>>
>>> I noticed that this setting reverts to the original setting, so oVirt
>>> must be writing this file. Perhaps these number can be changed in oVirt? If
>>> not, I will just setup and ansible play to revert the settings with working
>>> values and restart apache on my engine.
>>> :-)
>>>
>>> Cheers,
>>> Gervais
>>>
>>>
>>>
>>>
>>> ___
>>> 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] VM incremental backup

2016-09-29 Thread Kai Wagner

Hey,

I don't wont to break into your discussion, but I also never heard about
virt-sparsfiy and the sparse option for dd.

I tested it and it works like a charm. I converted a block device 65GB
with dd sparse to 40GB raw image and afterwards I used virsh-sparsify to
reduce the size down to 6.8GB into a qcow2 image file.

Thanks a lot for that hint.

Kai

Am 27.09.2016 um 15:17 schrieb Sven Achtelik:

No, I never came across this approach. I didn’t know about virt-sparsify.

I’ll look into that and give it a try.

Thank you

*Von:*Yaniv Dary [mailto:yd...@redhat.com]
*Gesendet:* Dienstag, 27. September 2016 15:10
*An:* Sven Achtelik
*Cc:* Maton, Brett ;
vasily.lamy...@megafon.ru; Ovirt Users

*Betreff:* Re: [ovirt-users] VM incremental backup

As I see it you have two options:
- In backup use 'dd' with 'conv=sparse' (or similar tool that
allows sparse).

- After backup use virt-sparsify [1] to reduce the size to the real
used size prior to restore.

To make this extra efficient you can use virt-sparsify anyways after
backup to make the file even smaller.

Have you considered this approach?

[1] http://libguestfs.org/virt-sparsify.1.html

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary

On Tue, Sep 27, 2016 at 4:01 PM, Sven Achtelik
> wrote:

Hi Yaniv,

how can this be done with DD ? Since it doesn’t know if the block
is free space ? I’ve been looking for such a solution for a long
time now. Everything I could find out was that I have to use a
utility that understands the FS and therefore knows where the free
space is.

Thank you,

Sven

*Von:*users-boun...@ovirt.org
[mailto:users-boun...@ovirt.org ]
*Im Auftrag von *Yaniv Dary
*Gesendet:* Dienstag, 27. September 2016 14:38
*An:* Maton, Brett >
*Cc:* vasily.lamy...@megafon.ru
; Ovirt Users >
*Betreff:* Re: [ovirt-users] VM incremental backup

Full VM disk backup. If you use dd you can drop the 0 parts of the
disk.

Yaniv Dary

Technical Product Manager

Red Hat Israel Ltd.

34 Jerusalem Road

Building A, 4th floor

Ra'anana, Israel 4350109

Tel : +972 (9) 7692306

8272306

Email: yd...@redhat.com

IRC : ydary

2016-09-27 15:27 GMT+03:00 Maton, Brett >:

Is there a preferred or recommended backup method in the
meantime ?

2016-09-22 10:30 GMT+01:00 vasily.lamy...@megafon.ru
>:

Hello!

I would like to understand the existence of the
possibility of incremental VM backups.

And if it is, the means by which it is achieved.

While I was only able to achieve a complete backup of the
virtual machine (but it is a very large amount of
information and time) by cloning a snapshot of the VM and
export to data domain.

*Ламыкин Василий*

Старший инженер по эксплуатации сервисных платформ

Столичный ф-ал ПАО "МегаФон

+7 (926) 500-3308

МегаФон лого+знак РУС B2C

Информация в этом сообщении предназначена исключительно
для конкретных лиц, которым она адресована. В сообщении
может содержаться конфиденциальная информация, которая не
может быть раскрыта или использована кем-либо, кроме
адресатов. Если вы не адресат этого сообщения, то
использование, переадресация, копирование или
распространение содержания сообщения или его части
незаконно и запрещено. Если Вы получили это сообщение
ошибочно, пожалуйста, незамедлительно сообщите отправителю
об этом и удалите со всем содержимым само сообщение и
любые возможные его копии и приложения.

Re: [ovirt-users] oVirt 4.0.x - hosted-engine was not starting properly

On Thu, Sep 29, 2016 at 3:11 PM, Martin Perina  wrote:

>
>
> On Thu, Sep 29, 2016 at 3:04 PM, Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Thu, Sep 29, 2016 at 12:47 PM, Martin Perina 
>> wrote:
>>
>>> Hi,
>>>
>>> please take a look at my inline comments:
>>>
>>> On Tue, Sep 27, 2016 at 7:23 PM, Gervais de Montbrun <
>>> gerv...@demontbrun.com> wrote:
>>>
 Hey All,

 Since updating to 4.0.x of oVirt, I have had an issue with my hosted
 engine. After a some poking around, I think I have figured out my issue and
 thought I would share to see what others think.
 The issue has existed with 4.0, 4.0.1, 4.0.2, 4.0.3, and still exists
 in 4.0.4.

 Description:
 When my hosted engine starts it reports that it is in a degraded state
 with 7 or 8 services still not started when I run systemctl status. It
 takes about 6 or 7 minutes to eventually start all the services and come
 online. If I don't set my cluster to Global-Maintenance mode it eventually
 thinks that my hosted-engine needs to be rebooted and restarts it before it
 can start everything.

>>>
>>> Could you please share with us logs gathered by ovirt-log-collector?
>>>
>>> It's just a guess but could you please take a look if you HE VM has
>>> enough entropy?
>>>
>>>   cat /proc/sys/kernel/random/entropy_avail
>>>
>>> If the value is low (below or around 200),  you really need to install
>>> and configure some entropy generator such as haveged
>>>
>>>
 Solution:
 I realized that Apache was the culprit and found that the proxy to the
 ovirt-engine in /etc/httpd/conf.d/z-ovirt-engine-proxy.conf has a
 super long timeout with many retries. I changed the settings and now
 everything works for me.

 -> Before change:

 >>> RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|
 rhevm.ssh.key.txt$)>
 ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5

 
 AddOutputFilterByType DEFLATE text/javascript text/css
 text/html text/xml text/json application/xml application/json
 application/x-yaml
 
 


 -> After change:

 
 ProxyPassMatch ajp://127.0.0.1:8702 timeout=5 retry=2

 
 AddOutputFilterByType DEFLATE text/javascript text/css
 text/html text/xml text/json application/xml application/json
 application/x-yaml
 
 


>>> This one is correct for 4.0
>>> , not sure why it was not updated during upgrade from 3.6. @Simone?
>>> 
>>>
>>
>> Honestly it's
>> 
>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5
>>
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css
>> text/html text/xml text/json application/xml application/json
>> application/x-yaml
>> 
>> 
>> also on a fresh 4.0 engine from our latest engine-appliance.
>>
>
> Right, I missed the timeout/retry option changes. But the important part
> is why old configuration (with different LocationMatch) was not overwritten
> during upgrade.
>
>
I suspect that it could got overwritten a second time to its 3.6 value in
our backup/restore procedure.
Adding Didi here.


>
>>
>>>
 If I read the timeout settings correctly, it will wait 60 minutes with
 5 retries. 5 hours is way too long for my little server to hold onto all
 those apache processes.

>>> The change I made allows for there to be an error, and also releases
 apache's hold on the process. Once everything is ready, apache is ready to
 serve requests and everything/everyone is happy. Before making the change,
 I just get a whitescreen in my browser and then nothing works until I
 restart Apache (or I end up in an endless loop of ovirt-ha services
 restarting my hosted-engine.

>>>
>>> Well, if you have an issue with too many apache processes waiting for
>>> engine to respond, then there's some issue in engine. As I wrote above
>>> please share the logs with us and check entropy.
>>>
>>> Thanks
>>>
>>> Martin Perina
>>> 
>>>
>>>

 I noticed that this setting reverts to the original setting, so oVirt
 must be writing this file. Perhaps these number can be changed in oVirt? If
 not, I will just setup and ansible play to revert the settings with working
 values and restart apache on my engine.
 :-)

 Cheers,
 Gervais




 ___
 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 4.0.x - hosted-engine was not starting properly

On Thu, Sep 29, 2016 at 12:47 PM, Martin Perina  wrote:

> Hi,
>
> please take a look at my inline comments:
>
> On Tue, Sep 27, 2016 at 7:23 PM, Gervais de Montbrun <
> gerv...@demontbrun.com> wrote:
>
>> Hey All,
>>
>> Since updating to 4.0.x of oVirt, I have had an issue with my hosted
>> engine. After a some poking around, I think I have figured out my issue and
>> thought I would share to see what others think.
>> The issue has existed with 4.0, 4.0.1, 4.0.2, 4.0.3, and still exists in
>> 4.0.4.
>>
>> Description:
>> When my hosted engine starts it reports that it is in a degraded state
>> with 7 or 8 services still not started when I run systemctl status. It
>> takes about 6 or 7 minutes to eventually start all the services and come
>> online. If I don't set my cluster to Global-Maintenance mode it eventually
>> thinks that my hosted-engine needs to be rebooted and restarts it before it
>> can start everything.
>>
>
> Could you please share with us logs gathered by ovirt-log-collector?
>
> It's just a guess but could you please take a look if you HE VM has enough
> entropy?
>
>   cat /proc/sys/kernel/random/entropy_avail
>
> If the value is low (below or around 200),  you really need to install and
> configure some entropy generator such as haveged
>
>
>> Solution:
>> I realized that Apache was the culprit and found that the proxy to the
>> ovirt-engine in /etc/httpd/conf.d/z-ovirt-engine-proxy.conf has a super
>> long timeout with many retries. I changed the settings and now everything
>> works for me.
>>
>> -> Before change:
>>
>> > RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|
>> rhevm.ssh.key.txt$)>
>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5
>>
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css
>> text/html text/xml text/json application/xml application/json
>> application/x-yaml
>> 
>> 
>>
>>
>> -> After change:
>>
>> 
>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=5 retry=2
>>
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css
>> text/html text/xml text/json application/xml application/json
>> application/x-yaml
>> 
>> 
>>
>>
> This one is correct for 4.0
> , not sure why it was not updated during upgrade from 3.6. @Simone?
> 
>

Honestly it's

ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5


AddOutputFilterByType DEFLATE text/javascript text/css
text/html text/xml text/json application/xml application/json
application/x-yaml


also on a fresh 4.0 engine from our latest engine-appliance.


>
>> If I read the timeout settings correctly, it will wait 60 minutes with 5
>> retries. 5 hours is way too long for my little server to hold onto all
>> those apache processes.
>>
> The change I made allows for there to be an error, and also releases
>> apache's hold on the process. Once everything is ready, apache is ready to
>> serve requests and everything/everyone is happy. Before making the change,
>> I just get a whitescreen in my browser and then nothing works until I
>> restart Apache (or I end up in an endless loop of ovirt-ha services
>> restarting my hosted-engine.
>>
>
> Well, if you have an issue with too many apache processes waiting for
> engine to respond, then there's some issue in engine. As I wrote above
> please share the logs with us and check entropy.
>
> Thanks
>
> Martin Perina
> 
>
>
>>
>> I noticed that this setting reverts to the original setting, so oVirt
>> must be writing this file. Perhaps these number can be changed in oVirt? If
>> not, I will just setup and ansible play to revert the settings with working
>> values and restart apache on my engine.
>> :-)
>>
>> Cheers,
>> Gervais
>>
>>
>>
>>
>> ___
>> 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 4.0.x - hosted-engine was not starting properly

On Thu, Sep 29, 2016 at 2:51 PM, Gervais de Montbrun  wrote:

> Hi Martin,
>
> The entropy was super low. Somewhere around 140. I installed and
> configured haveged.service to start at bootup, reverted my apache
> changes... After a reboot, my systemctl status still says that there are 7
> services queued (note that I erroneously said degraded in my previous email
> - the services are, in fact, queued), but the oVirt GUI comes up almost
> immediately and everything seems to be great.
>
>
Take care that using havaged on a VM should not be considered a good source
of entropy and the oVirt PKi is managed by the engine.
http://security.stackexchange.com/questions/34523/is-it-
appropriate-to-use-haveged-as-a-source-of-entropy-on-virtual-machines

A better approach is the virtio-rng paravirtualised rng driver as for patch
https://gerrit.ovirt.org/#/c/62334/



> Thank you for the tip. You solved my issue.
>
> Cheers,
> Gervais
>
>
>
> On Sep 29, 2016, at 7:47 AM, Martin Perina  wrote:
>
> Hi,
>
> please take a look at my inline comments:
>
> On Tue, Sep 27, 2016 at 7:23 PM, Gervais de Montbrun <
> gerv...@demontbrun.com> wrote:
>
>> Hey All,
>>
>> Since updating to 4.0.x of oVirt, I have had an issue with my hosted
>> engine. After a some poking around, I think I have figured out my issue and
>> thought I would share to see what others think.
>> The issue has existed with 4.0, 4.0.1, 4.0.2, 4.0.3, and still exists in
>> 4.0.4.
>>
>> Description:
>> When my hosted engine starts it reports that it is in a degraded state
>> with 7 or 8 services still not started when I run systemctl status. It
>> takes about 6 or 7 minutes to eventually start all the services and come
>> online. If I don't set my cluster to Global-Maintenance mode it eventually
>> thinks that my hosted-engine needs to be rebooted and restarts it before it
>> can start everything.
>>
>
> Could you please share with us logs gathered by ovirt-log-collector?
>
> It's just a guess but could you please take a look if you HE VM has enough
> entropy?
>
>   cat /proc/sys/kernel/random/entropy_avail
>
> If the value is low (below or around 200),  you really need to install and
> configure some entropy generator such as haveged
>
>
>> Solution:
>> I realized that Apache was the culprit and found that the proxy to the
>> ovirt-engine in /etc/httpd/conf.d/z-ovirt-engine-proxy.conf has a super
>> long timeout with many retries. I changed the settings and now everything
>> works for me.
>>
>> -> Before change:
>>
>> > RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|
>> rhevm.ssh.key.txt$)>
>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5
>>
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css
>> text/html text/xml text/json application/xml application/json
>> application/x-yaml
>> 
>> 
>>
>>
>> -> After change:
>>
>> 
>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=5 retry=2
>>
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css
>> text/html text/xml text/json application/xml application/json
>> application/x-yaml
>> 
>> 
>>
>>
> This one is correct for 4.0
> , not sure why it was not updated during upgrade from 3.6. @Simone?
> 
>
>
>>
>> If I read the timeout settings correctly, it will wait 60 minutes with 5
>> retries. 5 hours is way too long for my little server to hold onto all
>> those apache processes.
>>
> The change I made allows for there to be an error, and also releases
>> apache's hold on the process. Once everything is ready, apache is ready to
>> serve requests and everything/everyone is happy. Before making the change,
>> I just get a whitescreen in my browser and then nothing works until I
>> restart Apache (or I end up in an endless loop of ovirt-ha services
>> restarting my hosted-engine.
>>
>
> Well, if you have an issue with too many apache processes waiting for
> engine to respond, then there's some issue in engine. As I wrote above
> please share the logs with us and check entropy.
>
> Thanks
>
> Martin Perina
> 
>
>
>>
>> I noticed that this setting reverts to the original setting, so oVirt
>> must be writing this file. Perhaps these number can be changed in oVirt? If
>> not, I will just setup and ansible play to revert the settings with working
>> values and restart apache on my engine.
>> :-)
>>
>> Cheers,
>> Gervais
>>
>>
>>
>>
>> ___
>> 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 4.0.x - hosted-engine was not starting properly

2016-09-29 Thread Gervais de Montbrun

Hi Martin,

The entropy was super low. Somewhere around 140. I installed and configured 
haveged.service to start at bootup, reverted my apache changes... After a 
reboot, my systemctl status still says that there are 7 services queued (note 
that I erroneously said degraded in my previous email - the services are, in 
fact, queued), but the oVirt GUI comes up almost immediately and everything 
seems to be great.

Thank you for the tip. You solved my issue.

Cheers,
Gervais



> On Sep 29, 2016, at 7:47 AM, Martin Perina  wrote:
> 
> Hi,
> 
> please take a look at my inline comments:
> 
> On Tue, Sep 27, 2016 at 7:23 PM, Gervais de Montbrun  > wrote:
> Hey All,
> 
> Since updating to 4.0.x of oVirt, I have had an issue with my hosted engine. 
> After a some poking around, I think I have figured out my issue and thought I 
> would share to see what others think.
> The issue has existed with 4.0, 4.0.1, 4.0.2, 4.0.3, and still exists in 
> 4.0.4.
> 
> Description:
> When my hosted engine starts it reports that it is in a degraded state with 7 
> or 8 services still not started when I run systemctl status. It takes about 6 
> or 7 minutes to eventually start all the services and come online. If I don't 
> set my cluster to Global-Maintenance mode it eventually thinks that my 
> hosted-engine needs to be rebooted and restarts it before it can start 
> everything.
> 
> Could you please share with us logs gathered by ovirt-log-collector?
> 
> It's just a guess but could you please take a look if you HE VM has enough 
> entropy?
> 
>   cat /proc/sys/kernel/random/entropy_avail
> 
> If the value is low (below or around 200),  you really need to install and 
> configure some entropy generator such as haveged
> 
> 
> Solution:
> I realized that Apache was the culprit and found that the proxy to the 
> ovirt-engine in /etc/httpd/conf.d/z-ovirt-engine-proxy.conf has a super long 
> timeout with many retries. I changed the settings and now everything works 
> for me.
> 
> -> Before change:
>  ^/(ovirt-engine($|/)|api($|/)|RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|rhevm.ssh.key.txt$)>
> ProxyPassMatch ajp://127.0.0.1:8702 <> timeout=3600 retry=5
> 
> 
> AddOutputFilterByType DEFLATE text/javascript text/css text/html 
> text/xml text/json application/xml application/json application/x-yaml
> 
> 
> 
> -> After change:
> 
> ProxyPassMatch ajp://127.0.0.1:8702 <> timeout=5 retry=2
> 
> 
> AddOutputFilterByType DEFLATE text/javascript text/css text/html 
> text/xml text/json application/xml application/json application/x-yaml
> 
> 
> 
> This one is correct for 4.0, not sure why it was not updated during 
> upgrade from 3.6. @Simone?
>  
> 
> If I read the timeout settings correctly, it will wait 60 minutes with 5 
> retries. 5 hours is way too long for my little server to hold onto all those 
> apache processes.
> The change I made allows for there to be an error, and also releases apache's 
> hold on the process. Once everything is ready, apache is ready to serve 
> requests and everything/everyone is happy. Before making the change, I just 
> get a whitescreen in my browser and then nothing works until I restart Apache 
> (or I end up in an endless loop of ovirt-ha services restarting my 
> hosted-engine.
> 
> Well, if you have an issue with too many apache processes waiting for engine 
> to respond, then there's some issue in engine. As I wrote above please share 
> the logs with us and check entropy.
> 
> Thanks
> 
> Martin Perina
>  
> 
> I noticed that this setting reverts to the original setting, so oVirt must be 
> writing this file. Perhaps these number can be changed in oVirt? If not, I 
> will just setup and ansible play to revert the settings with working values 
> and restart apache on my engine.
> :-)
> 
> Cheers,
> Gervais
> 
> 
> 
> 
> ___
> 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] vioscsi.sys BSOD with Win 7

2016-09-29 Thread Ladi Prosek

On Wed, May 11, 2016 at 5:45 PM, Ladi Prosek  wrote:
> On Wed, May 11, 2016 at 1:46 PM, Cam Mac  wrote:
>> Hi Ladi,
>>
>>>
>>>
>>> We will try just the win 7 drivers that shipped with 3.6.3 rather than the
>>> SHA-2 signed FC23 drivers and I'll get back to you. I have a question:
>>> if I try to build a Win2k12 server via WDS, I assume I will have to add
>>> the 2k12 drivers and then remove them again if I go to build a Win 7 VM
>>> as Win 7 will presumably try to pick up the 2k12 driver? Or can they
>>> co-exist?
>>> WDS has a build process whenever drivers are added (e.g., for KVM, VMWare
>>> etc) for available drivers. Do you know when the fix will be available?
>>>
>>
>> Sorry for replying to my own post, but it turns out that there should be a
>> way in WDS to
>> set separate build directories for Win 7 and 2012, so please disregard that
>> question.
>>
>> The build appears to be going well so far, no BSODs.
>>
>> Thanks very much for the help Ladi!
>
> No worries, I'm glad that you're not blocked anymore.
>
>> Any ideas on when the newly signed drivers will be available?
>
> Shouldn't take more than a few weeks, I'll keep you posted.

Just a quick update, hope it's ok to reply to this old thread.

It took longer than expected but virtio-win-0.1.126-1.noarch has just
been released and it fixes both the signing issue (no more SHA-2
signatures) and the versioning issue (minimum target Windows version
is now declared by all drivers which should prevent the version
mixups).

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

Re: [ovirt-users] Clone and export VM by ovirt-shell

2016-09-29 Thread Juan Hernández

On 09/29/2016 01:38 PM, vasily.lamy...@megafon.ru wrote:
> I use ovirt 3.6.
> 
> How can I clone vm from snapshot.
> 
> I want to do it by ovirt-shell.
> 
> And after this I want to export VM.
> 
>  
> 
> I can’t get information help for vm clone.
> 
> And I don’t understand help action export.
> 
>  
> 
> Give me please example for this command’s.
> 

In the oVirt API what you intend to do is achieved adding a virtual
machine, and specifying the identifier of the snapshot that you want to use:

  add vm --name myvm --cluster-name  mycluster --snapshots-snapshot
"snapshot.id=935d92a0-2f04-4ab6-ab71-f578a22ca788"

Once you have created that virtual machine you can export it like this:

 action vm myvm export --storage_domain-name myexport

>  
> 
> help action vm clone
> 
>  
> 
>  
> 
> ERROR
> ==
> 
> vm
> clone does not exist.
> 
>  
> =
> 
>  
> 
>  
> 
> *Ламыкин Василий*
> 
> Старший инженер по эксплуатации сервисных платформ
> 
> Столичный ф-ал ПАО "МегаФон
> 
>  
> 
> +7 (926) 500-3308
> 
> МегаФон лого+знак РУС B2C
> 
>  
> 
> 
> 
> 
> Информация в этом сообщении предназначена исключительно для конкретных
> лиц, которым она адресована. В сообщении может содержаться
> конфиденциальная информация, которая не может быть раскрыта или
> использована кем-либо, кроме адресатов. Если вы не адресат этого
> сообщения, то использование, переадресация, копирование или
> распространение содержания сообщения или его части незаконно и
> запрещено. Если Вы получили это сообщение ошибочно, пожалуйста,
> незамедлительно сообщите отправителю об этом и удалите со всем
> содержимым само сообщение и любые возможные его копии и приложения.
> 
> The information contained in this communication is intended solely for
> the use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally
> privileged information. The contents may not be disclosed or used by
> anyone other than the addressee. If you are not the intended
> recipient(s), any use, disclosure, copying, distribution or any action
> taken or omitted to be taken in reliance on it is prohibited and may be
> unlawful. If you have received this communication in error please notify
> us immediately by responding to this email and then delete the e-mail
> and all attachments and any copies thereof.
> 
> (c)20mf50
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 


-- 
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] can't import vm from KVM host

2016-09-29 Thread Shahar Havivi

On 29.09.16 14:22, Nelson Lameiras wrote:
> Shahar,
> 
> I took the liberty to try to patch our test setup with the fix I took from 
> https://gerrit.ovirt.org/#/c/64272/4/ (lib/vdsm/v2v.py)
> I restarted vdsm afterwards
> 
> Result :
> In the GUI import page, now when clicking on "load" button (just before 
> guetting the list of vm to import on source), an error occurs : "Failed to 
> communicate with the external provider, see log for additional details."
> 
> Error on engine log :
> 
> "
> 2016-09-29 14:13:48,637 ERROR 
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
>  (default task-30) [] Failed in 'GetVmsFromExternalProviderVDS' method, for 
> vds: 'virtintelan01.lbg.office.lyra'; host: 'virtintelan01.lbg.office.lyra': 
> null
> 2016-09-29 14:13:48,637 ERROR 
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
>  (default task-30) [] Command 'GetVmsFromExternalProviderVDSCommand(HostName 
> = virtintelan01.lbg.office.lyra, 
> GetVmsFromExternalProviderParameters:{runAsync='true', 
> hostId='20b59a24-0098-461a-b4a3-7d6213b96c52', 
> url='qemu+ssh://root@192.168.210.140/system', username='null', 
> originType='KVM'})' execution failed: null
> 2016-09-29 14:13:48,637 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
>  (default task-30) [] FINISH, GetVmsFromExternalProviderVDSCommand, log id: 
> 6e062276
> 2016-09-29 14:13:48,637 ERROR 
> [org.ovirt.engine.core.bll.GetVmsFromExternalProviderQuery] (default task-30) 
> [] Query 'GetVmsFromExternalProviderQuery' failed: EngineException: 
> java.lang.NumberFormatException: null (Failed with error ENGINE and code 5001)
> 2016-09-29 14:13:48,637 ERROR 
> [org.ovirt.engine.core.bll.GetVmsFromExternalProviderQuery] (default task-30) 
> [] Exception: org.ovirt.engine.core.common.errors.EngineException: 
> EngineException: java.lang.NumberFormatException: null (Failed with error 
> ENGINE and code 5001)
> at 
> org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:114) 
> [bll.jar:]
> at 
> org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.runVdsCommand(VDSBrokerFrontendImpl.java:33)
>  [bll.jar:]
> at 
> org.ovirt.engine.core.bll.QueriesCommandBase.runVdsCommand(QueriesCommandBase.java:257)
>  [bll.jar:]
> ...
> "
> 
> In the host, I can see the following errors on /var/log/messages : 
> 
> "
> Sep 29 14:11:39 virtintelan01 journal: vdsm root ERROR Error getting disk 
> size#012Traceback (most recent call last):#012  File 
> "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 931, in 
> _add_disk_info#012vol = conn.storageVolLookupByPath(disk['alias'])#012  
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4596, in 
> storageVolLookupByPath#012if ret is None:raise 
> libvirtError('virStorageVolLookupByPath() failed', 
> conn=self)#012libvirtError: Volume de stockage introuvable : no storage vol 
> with matching path '/dev/mapper/vg_00-lv_sys'
> Sep 29 14:11:39 virtintelan01 journal: vdsm root ERROR Error getting disk 
> size#012Traceback (most recent call last):#012  File 
> "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 931, in 
> _add_disk_info#012vol = conn.storageVolLookupByPath(disk['alias'])#012  
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4596, in 
> storageVolLookupByPath#012if ret is None:raise 
> libvirtError('virStorageVolLookupByPath() failed', 
> conn=self)#012libvirtError: Volume de stockage introuvable : no storage vol 
> with matching path '/dev/sdc'
> "
> 
> FYI "Volume de stockage introuvable" (french) = "storage volume not found" 
> 
> This error did not appear before patching with the fix.
> 
> I repeated the operation 2 times with a clean setup + patch. Same behaviour. 
> Maybe I'm doing something wrong?
I need to check,
Thanks for the info.

> 
> my setup :
> ovirt-engine : centos 7.2 + ovirt 4.0.4
> hosts : centos 7.2 + ovirt 4.0.4 + fix
> 
> cordialement, regards, 
> Nelson LAMEIRAS 
> 
> Lyra Network 
> Service Projets et Processus 
> Tel : +33 (0) 5 32 09 09 70 
> 109 rue de l’innovation 
> 31670 Labège - France 
> www.lyra-network.com
> 
> - Original Message -
> From: "Nelson Lameiras" 
> To: "Shahar Havivi" 
> Cc: users@ovirt.org
> Sent: Friday, September 23, 2016 11:55:08 AM
> Subject: Re: [ovirt-users] can't import vm from KVM host
> 
> Shahar,
> 
> Thanks!
> I'll keep an eye on this bug and try to be helpfull when testing the fix.
> 
> nelson
> 
> - Original Message -
> From: "Shahar Havivi" 
> To: "Nelson Lameiras" 
> Cc: "Nisim Simsolo" , users@ovirt.org
> Sent: Thursday, September 22, 2016 10:14:33 AM
> Subject: Re: [ovirt-users] can't import vm from KVM host
> 
> Nelson,
> I opened a bug regarding your issue
> https://bugzilla.redhat.com/show_bug.cgi?id=1378340
> 
> And send a fix:

Re: [ovirt-users] Ovirt/Gluster replica 3 distributed-replicated problem

2016-09-29 Thread Ravishankar N


On 09/29/2016 05:18 PM, Sahina Bose wrote:

Yes, this is a GlusterFS problem. Adding gluster users ML

On Thu, Sep 29, 2016 at 5:11 PM, Davide Ferrari > wrote:


Hello

maybe this is more glustefs then ovirt related but since OVirt
integrates Gluster management and I'm experiencing the problem in
an ovirt cluster, I'm writing here.

The problem is simple: I have a data domain mappend on a replica 3
arbiter1 Gluster volume with 6 bricks, like this:

Status of volume: data_ssd
Gluster process TCP Port  RDMA Port  Online  Pid

--
Brick vm01.storage.billy:/gluster/ssd/data/
brick 49153 0  Y   19298
Brick vm02.storage.billy:/gluster/ssd/data/
brick 49153 0  Y   6146
Brick vm03.storage.billy:/gluster/ssd/data/
arbiter_brick 49153 0  Y   6552
Brick vm03.storage.billy:/gluster/ssd/data/
brick 49154 0  Y   6559
Brick vm04.storage.billy:/gluster/ssd/data/
brick 49152 0  Y   6077
Brick vm02.storage.billy:/gluster/ssd/data/
arbiter_brick 49154 0  Y   6153
Self-heal Daemon on localhost N/A   N/AY   30746
Self-heal Daemon on vm01.storage.billy N/A   N/A   
Y   196058
Self-heal Daemon on vm03.storage.billy N/A   N/A   
Y   23205
Self-heal Daemon on vm04.storage.billy N/A   N/A   
Y   8246



Now, I've put in maintenance the vm04 host, from ovirt, ticking
the "Stop gluster" checkbox, and Ovirt didn't complain about
anything. But when I tried to run a new VM it complained about
"storage I/O problem", while the storage data status was always UP.

Looking in the gluster logs I can see this:

[2016-09-29 11:01:01.556908] I
[glusterfsd-mgmt.c:1596:mgmt_getspec_cbk] 0-glusterfs: No change
in volfile, continuing
[2016-09-29 11:02:28.124151] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done]
0-data_ssd-replicate-1: Failing READ on gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain observed.
[Input/output error]
[2016-09-29 11:02:28.126580] W [MSGID: 108008]
[afr-read-txn.c:244:afr_read_txn] 0-data_ssd-replicate-1:
Unreadable subvolume -1 found with event generation 6 for gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d. (Possible split-brain)
[2016-09-29 11:02:28.127374] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done]
0-data_ssd-replicate-1: Failing FGETXATTR on gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain observed.
[Input/output error]
[2016-09-29 11:02:28.128130] W [MSGID: 108027]
[afr-common.c:2403:afr_discover_done] 0-data_ssd-replicate-1: no
read subvols for (null)
[2016-09-29 11:02:28.129890] W [fuse-bridge.c:2228:fuse_readv_cbk]
0-glusterfs-fuse: 8201: READ => -1
gfid=bf5922b7-19f3-4ce3-98df-71e981ecca8d fd=0x7f09b749d210
(Input/output error)
[2016-09-29 11:02:28.130824] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done]
0-data_ssd-replicate-1: Failing FSTAT on gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain observed.
[Input/output error]



Does `gluster volume heal data_ssd info split-brain` report that the 
file is in split-brain, with vm04 still being down?
If yes, could you provide the extended attributes of this gfid from all 
3 bricks:
getfattr -d -m . -e hex 
/path/to/brick/bf/59/bf5922b7-19f3-4ce3-98df-71e981ecca8d


If no, then I'm guessing that it is not in actual split-brain (hence the 
'Possible split-brain' message). If the node you brought down contains 
the only good copy of the file (i.e the other data brick and arbiter are 
up, and the arbiter 'blames' this other brick), all I/O is failed with 
EIO to prevent file from getting into actual split-brain. The heals will 
happen when the good node comes up and I/O should be allowed again in 
that case.


-Ravi



[2016-09-29 11:02:28.133879] W [fuse-bridge.c:767:fuse_attr_cbk]
0-glusterfs-fuse: 8202: FSTAT()

/ba2bd397-9222-424d-aecc-eb652c0169d9/images/f02ac1ce-52cd-4b81-8b29-f8006d0469e0/ff4e49c6-3084-4234-80a1-18a67615c527
=> -1 (Input/output error)
The message "W [MSGID: 108008] [afr-read-txn.c:244:afr_read_txn]
0-data_ssd-replicate-1: Unreadable subvolume -1 found with event
generation 6 for gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d.
(Possible split-brain)" repeated 11 times between [2016-09-29
11:02:28.126580] and [2016-09-29 11:02:28.517744]
[2016-09-29 11:02:28.518607] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done]
0-data_ssd-replicate-1: Failing STAT on gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain observed.
[Input/output error]

Now, how is it possible to have a split brain if I stopped just

Re: [ovirt-users] Replacing Certificates in hosted-engine cluster

On Thu, Sep 29, 2016 at 1:09 PM, Joshua Doll  wrote:

> If I have two CAs both claiming to be the root CA for a given Domain,
> essentially both claiming to be the same CA, this won't cause issues with
> communication between the engine and the two hosts? Does the CA used for
> communication between the hosts and the engine only exist in some protected
> trust store that is the only consulted source for this communication?
>

No, if you want to use custom CA for HTTPS, it will not change anyhting on
internal CA used for engine-hosts communications. Custom CA can be used
only for HTTPS certificates and when custom CA is configured properly we
use different truststore for HTTPS than for engine-host communication.



> Thanks, Josh
>
> On Thu, Sep 29, 2016, 6:53 AM Martin Perina  wrote:
>
>> Hi,
>>
>> by default engine uses its own CA to sign certificates for HTTPS access
>> and for engine-host communications. You can use your own CA only for HTTS
>> certification.
>> So if you are using oVirt 4.0 and you want to start to use custom CA for
>> HTTPS certificates please take a look at Doc Text in:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1336838
>> https://bugzilla.redhat.com/show_bug.cgi?id=1313379
>>
>> @Didi, are there any other steps required for hosted engine regarding
>> custom CA?
>>
>> Thanks
>>
>> Martin Perina
>>
>>
>>
>> On Wed, Sep 28, 2016 at 1:07 PM, Joshua Doll 
>> wrote:
>>
>>> Hi, I have a two node cluster running a hosted-engine setup. I have
>>> stood up an enterprise CA and would like to replace the ovirt self signed
>>> certificates. I can't find a list of all the certificates online. Is there
>>> a list, or can someone point me in the right direction?
>>>
>>> Thanks, Josh
>>>
>>> ___
>>> 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] VM pauses/hangs after migration

2016-09-29 Thread Michal Skrivanek


> On 29 Sep 2016, at 13:59, Davide Ferrari  wrote:
> 
> Hello
> 
> Today I've the faulty DIMMs replaced, started the same VM again and did the 
> same migration and this time worked, so it was 100% due to that.
> 
> The problem that make me wonder a bit is: if it's the source host with memory 
> problem the one which blocks the correct migration, a faulty DIMM will force 
> you to stop the VMs running on that host, because you cannot simply migrate 
> them away to do the maintenence tasks…

if you have a faulty hw you should do that ASAP as you never know where it is 
going to affect you. It’s like with disk errors…you may think it’s ok when you 
rarely write to certain places, but once you try to copy it off the problematic 
storage and you read every single byte/location you’re screwed…

Thanks,
michal

> 
> 
> 2016-09-29 13:53 GMT+02:00 Tomas Jelinek  >:
> 
> 
> - Original Message -
> > From: "Davide Ferrari" >
> > To: "users" >
> > Sent: Wednesday, September 28, 2016 2:59:59 PM
> > Subject: [ovirt-users] VM pauses/hangs after migration
> >
> > Hello
> >
> > trying to migrate a VM from one host to another, a big VM with 96GB of RAM, 
> > I
> > found that when the migration completes, the VM goes to a paused satte and
> > cannot be resumed. The libvirt/qemu log it gives is this:
> >
> > 2016-09-28T12:18:15.679176Z qemu-kvm: error while loading state section id
> > 2(ram)
> > 2016-09-28T12:18:15.680010Z qemu-kvm: load of migration failed: Input/output
> > error
> > 2016-09-28 12:18:15.872+: shutting down
> > 2016-09-28 12:22:21.467+: starting up libvirt version: 1.2.17, package:
> > 13.el7_2.5 (CentOS BuildSystem < http://bugs.centos.org 
> >  >,
> > 2016-06-23-14 :23:27, worker1.bsys.centos.org 
> >  ), qemu version: 2.3.0
> > (qemu-kvm-ev-2.3.0-31.el7.16.1)
> > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> > QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name front04.billydomain.com 
> >  -S
> > -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu Haswell-noTSX -m
> > size=100663296k,slots=16,maxmem=4294967296k -realtime mlock=off -smp
> > 32,sockets=16,cores=1,threads=2 -numa node,nodeid=0,cpus=0-31,mem=98304
> > -uuid 4511d1c0-6607-418f-ae75-34f605b2ad68 -smbios
> > type=1,manufacturer=oVirt,product=oVirt
> > Node,version=7-2.1511.el7.centos.2.10,serial=4C4C4544-004A-3310-8054-B2C04F474432,uuid=4511d1c0-6607-418f-ae75-34f605b2ad68
> > -no-user-config -nodefaults -chardev
> > socket,id=charmonitor,path=/var/lib/libvirt/qemu/
> > domain-front04.billydomain.com/monitor.sock,server,nowait 
> >  -mon
> > chardev=charmonitor,id=monitor,mode=control -rtc
> > base=2016-09-28T14:22:21,driftfix=slew -global
> > kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
> > -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> > virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x7 -device
> > virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4 -drive
> > if=none,id=drive-ide0-1-0,readonly=on,format=raw -device
> > ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> > file=/rhev/data-center/0001-0001-0001-0001-03e3/ba2bd397-9222-424d-aecc-eb652c0169d9/images/b5b49d5c-2378-4639-9469-362e37ae7473/24fd0d3c-309b-458d-9818-4321023afacf,if=none,id=drive-virtio-disk0,format=qcow2,serial=b5b49d5c-2378-4639-9469-362e37ae7473,cache=none,werror=stop,rerror=stop,aio=threads
> > -device
> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> > -drive
> > file=/rhev/data-center/0001-0001-0001-0001-03e3/ba2bd397-9222-424d-aecc-eb652c0169d9/images/f02ac1ce-52cd-4b81-8b29-f8006d0469e0/ff4e49c6-3084-4234-80a1-18a67615c527,if=none,id=drive-virtio-disk1,format=raw,serial=f02ac1ce-52cd-4b81-8b29-f8006d0469e0,cache=none,werror=stop,rerror=stop,aio=threads
> > -device
> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk1,id=virtio-disk1
> > -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device
> > virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:56,bus=pci.0,addr=0x3
> > -chardev
> > socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/4511d1c0-6607-418f-ae75-34f605b2ad68.com.redhat.rhevm.vdsm,server,nowait
> > -device
> > virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> > -chardev
> > socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/4511d1c0-6607-418f-ae75-34f605b2ad68.org.qemu.guest_agent.0,server,nowait
> > -device
> > virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> > -chardev spicevmc,id=charchannel2,name=vdagent -device

Re: [ovirt-users] VM pauses/hangs after migration

Hello

Today I've the faulty DIMMs replaced, started the same VM again and did the
same migration and this time worked, so it was 100% due to that.

The problem that make me wonder a bit is: if it's the source host with
memory problem the one which blocks the correct migration, a faulty DIMM
will force you to stop the VMs running on that host, because you cannot
simply migrate them away to do the maintenence tasks...


2016-09-29 13:53 GMT+02:00 Tomas Jelinek :

>
>
> - Original Message -
> > From: "Davide Ferrari" 
> > To: "users" 
> > Sent: Wednesday, September 28, 2016 2:59:59 PM
> > Subject: [ovirt-users] VM pauses/hangs after migration
> >
> > Hello
> >
> > trying to migrate a VM from one host to another, a big VM with 96GB of
> RAM, I
> > found that when the migration completes, the VM goes to a paused satte
> and
> > cannot be resumed. The libvirt/qemu log it gives is this:
> >
> > 2016-09-28T12:18:15.679176Z qemu-kvm: error while loading state section
> id
> > 2(ram)
> > 2016-09-28T12:18:15.680010Z qemu-kvm: load of migration failed:
> Input/output
> > error
> > 2016-09-28 12:18:15.872+: shutting down
> > 2016-09-28 12:22:21.467+: starting up libvirt version: 1.2.17,
> package:
> > 13.el7_2.5 (CentOS BuildSystem < http://bugs.centos.org >,
> > 2016-06-23-14:23:27, worker1.bsys.centos.org ), qemu version: 2.3.0
> > (qemu-kvm-ev-2.3.0-31.el7.16.1)
> > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> > QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name front04.billydomain.com
> -S
> > -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu Haswell-noTSX -m
> > size=100663296k,slots=16,maxmem=4294967296k -realtime mlock=off -smp
> > 32,sockets=16,cores=1,threads=2 -numa node,nodeid=0,cpus=0-31,mem=98304
> > -uuid 4511d1c0-6607-418f-ae75-34f605b2ad68 -smbios
> > type=1,manufacturer=oVirt,product=oVirt
> > Node,version=7-2.1511.el7.centos.2.10,serial=4C4C4544-
> 004A-3310-8054-B2C04F474432,uuid=4511d1c0-6607-418f-ae75-34f605b2ad68
> > -no-user-config -nodefaults -chardev
> > socket,id=charmonitor,path=/var/lib/libvirt/qemu/
> > domain-front04.billydomain.com/monitor.sock,server,nowait -mon
> > chardev=charmonitor,id=monitor,mode=control -rtc
> > base=2016-09-28T14:22:21,driftfix=slew -global
> > kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
> > -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> > virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x7 -device
> > virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4
> -drive
> > if=none,id=drive-ide0-1-0,readonly=on,format=raw -device
> > ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> > file=/rhev/data-center/0001-0001-0001-0001-
> 03e3/ba2bd397-9222-424d-aecc-eb652c0169d9/images/
> b5b49d5c-2378-4639-9469-362e37ae7473/24fd0d3c-309b-
> 458d-9818-4321023afacf,if=none,id=drive-virtio-disk0,
> format=qcow2,serial=b5b49d5c-2378-4639-9469-362e37ae7473,
> cache=none,werror=stop,rerror=stop,aio=threads
> > -device
> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-
> virtio-disk0,id=virtio-disk0,bootindex=1
> > -drive
> > file=/rhev/data-center/0001-0001-0001-0001-
> 03e3/ba2bd397-9222-424d-aecc-eb652c0169d9/images/
> f02ac1ce-52cd-4b81-8b29-f8006d0469e0/ff4e49c6-3084-
> 4234-80a1-18a67615c527,if=none,id=drive-virtio-disk1,
> format=raw,serial=f02ac1ce-52cd-4b81-8b29-f8006d0469e0,
> cache=none,werror=stop,rerror=stop,aio=threads
> > -device
> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-
> virtio-disk1,id=virtio-disk1
> > -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device
> > virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:
> 16:01:56,bus=pci.0,addr=0x3
> > -chardev
> > socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/
> 4511d1c0-6607-418f-ae75-34f605b2ad68.com.redhat.rhevm.vdsm,server,nowait
> > -device
> > virtserialport,bus=virtio-serial0.0,nr=1,chardev=
> charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> > -chardev
> > socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/
> 4511d1c0-6607-418f-ae75-34f605b2ad68.org.qemu.guest_agent.0,server,nowait
> > -device
> > virtserialport,bus=virtio-serial0.0,nr=2,chardev=
> charchannel1,id=channel1,name=org.qemu.guest_agent.0
> > -chardev spicevmc,id=charchannel2,name=vdagent -device
> > virtserialport,bus=virtio-serial0.0,nr=3,chardev=
> charchannel2,id=channel2,name=com.redhat.spice.0
> > -vnc 192.168.10.225:1 ,password -k es -spice
> > tls-port=5902,addr=192.168.10.225,x509-dir=/etc/pki/vdsm/
> libvirt-spice,tls-channel=default,tls-channel=main,tls-
> channel=display,tls-channel=inputs,tls-channel=cursor,tls-
> channel=playback,tls-channel=record,tls-channel=smartcard,
> tls-channel=usbredir,seamless-migration=on
> > -k es -device
> > qxl-vga,id=video0,ram_size=67108864,vram_size=8388608,
> vgamem_mb=16,bus=pci.0,addr=0x2
> > -incoming tcp: 0.0.0.0:49156 -device
> >

Re: [ovirt-users] VM pauses/hangs after migration

2016-09-29 Thread Tomas Jelinek



- Original Message -
> From: "Davide Ferrari" 
> To: "users" 
> Sent: Wednesday, September 28, 2016 2:59:59 PM
> Subject: [ovirt-users] VM pauses/hangs after migration
> 
> Hello
> 
> trying to migrate a VM from one host to another, a big VM with 96GB of RAM, I
> found that when the migration completes, the VM goes to a paused satte and
> cannot be resumed. The libvirt/qemu log it gives is this:
> 
> 2016-09-28T12:18:15.679176Z qemu-kvm: error while loading state section id
> 2(ram)
> 2016-09-28T12:18:15.680010Z qemu-kvm: load of migration failed: Input/output
> error
> 2016-09-28 12:18:15.872+: shutting down
> 2016-09-28 12:22:21.467+: starting up libvirt version: 1.2.17, package:
> 13.el7_2.5 (CentOS BuildSystem < http://bugs.centos.org >,
> 2016-06-23-14:23:27, worker1.bsys.centos.org ), qemu version: 2.3.0
> (qemu-kvm-ev-2.3.0-31.el7.16.1)
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name front04.billydomain.com -S
> -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu Haswell-noTSX -m
> size=100663296k,slots=16,maxmem=4294967296k -realtime mlock=off -smp
> 32,sockets=16,cores=1,threads=2 -numa node,nodeid=0,cpus=0-31,mem=98304
> -uuid 4511d1c0-6607-418f-ae75-34f605b2ad68 -smbios
> type=1,manufacturer=oVirt,product=oVirt
> Node,version=7-2.1511.el7.centos.2.10,serial=4C4C4544-004A-3310-8054-B2C04F474432,uuid=4511d1c0-6607-418f-ae75-34f605b2ad68
> -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/
> domain-front04.billydomain.com/monitor.sock,server,nowait -mon
> chardev=charmonitor,id=monitor,mode=control -rtc
> base=2016-09-28T14:22:21,driftfix=slew -global
> kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x7 -device
> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4 -drive
> if=none,id=drive-ide0-1-0,readonly=on,format=raw -device
> ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> file=/rhev/data-center/0001-0001-0001-0001-03e3/ba2bd397-9222-424d-aecc-eb652c0169d9/images/b5b49d5c-2378-4639-9469-362e37ae7473/24fd0d3c-309b-458d-9818-4321023afacf,if=none,id=drive-virtio-disk0,format=qcow2,serial=b5b49d5c-2378-4639-9469-362e37ae7473,cache=none,werror=stop,rerror=stop,aio=threads
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> -drive
> file=/rhev/data-center/0001-0001-0001-0001-03e3/ba2bd397-9222-424d-aecc-eb652c0169d9/images/f02ac1ce-52cd-4b81-8b29-f8006d0469e0/ff4e49c6-3084-4234-80a1-18a67615c527,if=none,id=drive-virtio-disk1,format=raw,serial=f02ac1ce-52cd-4b81-8b29-f8006d0469e0,cache=none,werror=stop,rerror=stop,aio=threads
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk1,id=virtio-disk1
> -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:56,bus=pci.0,addr=0x3
> -chardev
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/4511d1c0-6607-418f-ae75-34f605b2ad68.com.redhat.rhevm.vdsm,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/4511d1c0-6607-418f-ae75-34f605b2ad68.org.qemu.guest_agent.0,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -chardev spicevmc,id=charchannel2,name=vdagent -device
> virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
> -vnc 192.168.10.225:1 ,password -k es -spice
> tls-port=5902,addr=192.168.10.225,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
> -k es -device
> qxl-vga,id=video0,ram_size=67108864,vram_size=8388608,vgamem_mb=16,bus=pci.0,addr=0x2
> -incoming tcp: 0.0.0.0:49156 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
> Domain id=5 is tainted: hook-script
> red_dispatcher_loadvm_commands:
> KVM: entry failed, hardware error 0x8
> RAX=ffed RBX=8817ba00c000 RCX=0100
> RDX=
> RSI= RDI=0046 RBP=8817ba00fe98
> RSP=8817ba00fe98
> R8 = R9 = R10=
> R11=
> R12=0006 R13=8817ba00c000 R14=8817ba00c000
> R15=
> RIP=81058e96 RFL=00010286 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =   
> CS =0010   00a09b00 DPL=0 CS64 [-RA]
> SS =0018

Re: [ovirt-users] Ovirt/Gluster replica 3 distributed-replicated problem

2016-09-29 Thread Sahina Bose

Yes, this is a GlusterFS problem. Adding gluster users ML

On Thu, Sep 29, 2016 at 5:11 PM, Davide Ferrari  wrote:

> Hello
>
> maybe this is more glustefs then ovirt related but since OVirt integrates
> Gluster management and I'm experiencing the problem in an ovirt cluster,
> I'm writing here.
>
> The problem is simple: I have a data domain mappend on a replica 3
> arbiter1 Gluster volume with 6 bricks, like this:
>
> Status of volume: data_ssd
> Gluster process TCP Port  RDMA Port  Online
> Pid
> 
> --
> Brick vm01.storage.billy:/gluster/ssd/data/
> brick   49153 0  Y
> 19298
> Brick vm02.storage.billy:/gluster/ssd/data/
> brick   49153 0  Y
> 6146
> Brick vm03.storage.billy:/gluster/ssd/data/
> arbiter_brick   49153 0  Y
> 6552
> Brick vm03.storage.billy:/gluster/ssd/data/
> brick   49154 0  Y
> 6559
> Brick vm04.storage.billy:/gluster/ssd/data/
> brick   49152 0  Y
> 6077
> Brick vm02.storage.billy:/gluster/ssd/data/
> arbiter_brick   49154 0  Y
> 6153
> Self-heal Daemon on localhost   N/A   N/AY
> 30746
> Self-heal Daemon on vm01.storage.billy  N/A   N/AY
> 196058
> Self-heal Daemon on vm03.storage.billy  N/A   N/AY
> 23205
> Self-heal Daemon on vm04.storage.billy  N/A   N/AY
> 8246
>
>
> Now, I've put in maintenance the vm04 host, from ovirt, ticking the "Stop
> gluster" checkbox, and Ovirt didn't complain about anything. But when I
> tried to run a new VM it complained about "storage I/O problem", while the
> storage data status was always UP.
>
> Looking in the gluster logs I can see this:
>
> [2016-09-29 11:01:01.556908] I [glusterfsd-mgmt.c:1596:mgmt_getspec_cbk]
> 0-glusterfs: No change in volfile, continuing
> [2016-09-29 11:02:28.124151] E [MSGID: 108008] 
> [afr-read-txn.c:89:afr_read_txn_refresh_done]
> 0-data_ssd-replicate-1: Failing READ on gfid 
> bf5922b7-19f3-4ce3-98df-71e981ecca8d:
> split-brain observed. [Input/output error]
> [2016-09-29 11:02:28.126580] W [MSGID: 108008]
> [afr-read-txn.c:244:afr_read_txn] 0-data_ssd-replicate-1: Unreadable
> subvolume -1 found with event generation 6 for gfid 
> bf5922b7-19f3-4ce3-98df-71e981ecca8d.
> (Possible split-brain)
> [2016-09-29 11:02:28.127374] E [MSGID: 108008] 
> [afr-read-txn.c:89:afr_read_txn_refresh_done]
> 0-data_ssd-replicate-1: Failing FGETXATTR on gfid 
> bf5922b7-19f3-4ce3-98df-71e981ecca8d:
> split-brain observed. [Input/output error]
> [2016-09-29 11:02:28.128130] W [MSGID: 108027] 
> [afr-common.c:2403:afr_discover_done]
> 0-data_ssd-replicate-1: no read subvols for (null)
> [2016-09-29 11:02:28.129890] W [fuse-bridge.c:2228:fuse_readv_cbk]
> 0-glusterfs-fuse: 8201: READ => -1 gfid=bf5922b7-19f3-4ce3-98df-71e981ecca8d
> fd=0x7f09b749d210 (Input/output error)
> [2016-09-29 11:02:28.130824] E [MSGID: 108008] 
> [afr-read-txn.c:89:afr_read_txn_refresh_done]
> 0-data_ssd-replicate-1: Failing FSTAT on gfid 
> bf5922b7-19f3-4ce3-98df-71e981ecca8d:
> split-brain observed. [Input/output error]
> [2016-09-29 11:02:28.133879] W [fuse-bridge.c:767:fuse_attr_cbk]
> 0-glusterfs-fuse: 8202: FSTAT() /ba2bd397-9222-424d-aecc-
> eb652c0169d9/images/f02ac1ce-52cd-4b81-8b29-f8006d0469e0/
> ff4e49c6-3084-4234-80a1-18a67615c527 => -1 (Input/output error)
> The message "W [MSGID: 108008] [afr-read-txn.c:244:afr_read_txn]
> 0-data_ssd-replicate-1: Unreadable subvolume -1 found with event generation
> 6 for gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d. (Possible split-brain)"
> repeated 11 times between [2016-09-29 11:02:28.126580] and [2016-09-29
> 11:02:28.517744]
> [2016-09-29 11:02:28.518607] E [MSGID: 108008] 
> [afr-read-txn.c:89:afr_read_txn_refresh_done]
> 0-data_ssd-replicate-1: Failing STAT on gfid 
> bf5922b7-19f3-4ce3-98df-71e981ecca8d:
> split-brain observed. [Input/output error]
>
> Now, how is it possible to have a split brain if I stopped just ONE server
> which had just ONE of six bricks, and it was cleanly shut down with
> maintenance mode from ovirt?
>
> I created the volume originally this way:
> # gluster volume create data_ssd replica 3 arbiter 1
> vm01.storage.billy:/gluster/ssd/data/brick 
> vm02.storage.billy:/gluster/ssd/data/brick
> vm03.storage.billy:/gluster/ssd/data/arbiter_brick
> vm03.storage.billy:/gluster/ssd/data/brick 
> vm04.storage.billy:/gluster/ssd/data/brick
> vm02.storage.billy:/gluster/ssd/data/arbiter_brick
> # gluster volume set data_ssd group virt
> # gluster volume set data_ssd storage.owner-uid 36 && gluster volume set
> data_ssd storage.owner-gid 36
> # gluster volume start data_ssd
>
>
> --
> Davide Ferrari
> Senior Systems Engineer
>
>

[ovirt-users] Ovirt/Gluster replica 3 distributed-replicated problem

Hello

maybe this is more glustefs then ovirt related but since OVirt integrates
Gluster management and I'm experiencing the problem in an ovirt cluster,
I'm writing here.

The problem is simple: I have a data domain mappend on a replica 3 arbiter1
Gluster volume with 6 bricks, like this:

Status of volume: data_ssd
Gluster process TCP Port  RDMA Port  Online  Pid
--
Brick vm01.storage.billy:/gluster/ssd/data/
brick   49153 0  Y
19298
Brick vm02.storage.billy:/gluster/ssd/data/
brick   49153 0  Y
6146
Brick vm03.storage.billy:/gluster/ssd/data/
arbiter_brick   49153 0  Y
6552
Brick vm03.storage.billy:/gluster/ssd/data/
brick   49154 0  Y
6559
Brick vm04.storage.billy:/gluster/ssd/data/
brick   49152 0  Y
6077
Brick vm02.storage.billy:/gluster/ssd/data/
arbiter_brick   49154 0  Y
6153
Self-heal Daemon on localhost   N/A   N/AY
30746
Self-heal Daemon on vm01.storage.billy  N/A   N/AY
196058
Self-heal Daemon on vm03.storage.billy  N/A   N/AY
23205
Self-heal Daemon on vm04.storage.billy  N/A   N/AY
8246


Now, I've put in maintenance the vm04 host, from ovirt, ticking the "Stop
gluster" checkbox, and Ovirt didn't complain about anything. But when I
tried to run a new VM it complained about "storage I/O problem", while the
storage data status was always UP.

Looking in the gluster logs I can see this:

[2016-09-29 11:01:01.556908] I [glusterfsd-mgmt.c:1596:mgmt_getspec_cbk]
0-glusterfs: No change in volfile, continuing
[2016-09-29 11:02:28.124151] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done] 0-data_ssd-replicate-1:
Failing READ on gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain
observed. [Input/output error]
[2016-09-29 11:02:28.126580] W [MSGID: 108008]
[afr-read-txn.c:244:afr_read_txn] 0-data_ssd-replicate-1: Unreadable
subvolume -1 found with event generation 6 for gfid
bf5922b7-19f3-4ce3-98df-71e981ecca8d. (Possible split-brain)
[2016-09-29 11:02:28.127374] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done] 0-data_ssd-replicate-1:
Failing FGETXATTR on gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain
observed. [Input/output error]
[2016-09-29 11:02:28.128130] W [MSGID: 108027]
[afr-common.c:2403:afr_discover_done] 0-data_ssd-replicate-1: no read
subvols for (null)
[2016-09-29 11:02:28.129890] W [fuse-bridge.c:2228:fuse_readv_cbk]
0-glusterfs-fuse: 8201: READ => -1
gfid=bf5922b7-19f3-4ce3-98df-71e981ecca8d fd=0x7f09b749d210 (Input/output
error)
[2016-09-29 11:02:28.130824] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done] 0-data_ssd-replicate-1:
Failing FSTAT on gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain
observed. [Input/output error]
[2016-09-29 11:02:28.133879] W [fuse-bridge.c:767:fuse_attr_cbk]
0-glusterfs-fuse: 8202: FSTAT()
/ba2bd397-9222-424d-aecc-eb652c0169d9/images/f02ac1ce-52cd-4b81-8b29-f8006d0469e0/ff4e49c6-3084-4234-80a1-18a67615c527
=> -1 (Input/output error)
The message "W [MSGID: 108008] [afr-read-txn.c:244:afr_read_txn]
0-data_ssd-replicate-1: Unreadable subvolume -1 found with event generation
6 for gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d. (Possible split-brain)"
repeated 11 times between [2016-09-29 11:02:28.126580] and [2016-09-29
11:02:28.517744]
[2016-09-29 11:02:28.518607] E [MSGID: 108008]
[afr-read-txn.c:89:afr_read_txn_refresh_done] 0-data_ssd-replicate-1:
Failing STAT on gfid bf5922b7-19f3-4ce3-98df-71e981ecca8d: split-brain
observed. [Input/output error]

Now, how is it possible to have a split brain if I stopped just ONE server
which had just ONE of six bricks, and it was cleanly shut down with
maintenance mode from ovirt?

I created the volume originally this way:
# gluster volume create data_ssd replica 3 arbiter 1
vm01.storage.billy:/gluster/ssd/data/brick
vm02.storage.billy:/gluster/ssd/data/brick
vm03.storage.billy:/gluster/ssd/data/arbiter_brick
vm03.storage.billy:/gluster/ssd/data/brick
vm04.storage.billy:/gluster/ssd/data/brick
vm02.storage.billy:/gluster/ssd/data/arbiter_brick
# gluster volume set data_ssd group virt
# gluster volume set data_ssd storage.owner-uid 36 && gluster volume set
data_ssd storage.owner-gid 36
# gluster volume start data_ssd


-- 
Davide Ferrari
Senior Systems Engineer
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Clone and export VM by ovirt-shell

2016-09-29 Thread vasily.lamy...@megafon.ru

I use ovirt 3.6.
How can I clone vm from snapshot.
I want to do it by ovirt-shell.
And after this I want to export VM.

I can't get information help for vm clone.
And I don't understand help action export.

Give me please example for this command's.

help action vm clone

ERROR ==
vm clone
does not exist.

Ламыкин Василий
Старший инженер по эксплуатации сервисных платформ
Столичный ф-ал ПАО "МегаФон

+7 (926) 500-3308
[МегаФон лого+знак РУС B2C]

Информация в этом сообщении предназначена исключительно для конкретных лиц,
которым она адресована. В сообщении может содержаться конфиденциальная
информация, которая не может быть раскрыта или использована кем-либо, кроме
адресатов. Если вы не адресат этого сообщения, то использование, переадресация,
копирование или распространение содержания сообщения или его части незаконно и
запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно
сообщите отправителю об этом и удалите со всем содержимым само сообщение и
любые возможные его копии и приложения.

The information contained in this communication is intended solely for the use
of the individual or entity to whom it is addressed and others authorized to
receive it. It may contain confidential or legally privileged information. The
contents may not be disclosed or used by anyone other than the addressee. If
you are not the intended recipient(s), any use, disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this communication in
error please notify us immediately by responding to this email and then delete
the e-mail and all attachments and any copies thereof.

Re: [ovirt-users] Windows VDI Licensing

2016-09-29 Thread Maxence Sartiaux

Actually i plan to go for  1 W7Pro VM per User.

On Thu, 2016-09-29 at 12:31 +0200, Frank Rothenstein wrote:
> Hi Maxence,
> 
> the answer is clear: it depends
> > If you want to use Terminal-Server I guess you have to swallow the
bitter pill and go the MS AD way.
> > If you go the 1 User - 1 VM way like Win7Pro I would say you can stay
on Samba.
> Am Donnerstag, den 29.09.2016, 11:35 +0200 schrieb Maxence Sartiaux:
> > Hello,
> > 
> > > > > > I currently work on a Windows VDI infrastructure based on ovirt,
i'm looking for informations or experiences about Windows/Office
VDI Licensing.
> > 
> > My pool is stateless and the domain controller is a Samba 4.5.
> > 
> > > > > > I called Microsoft for informations they told me i need a Windows
Server Active Directory because it's impossible to activate the
Windows with a Samba 4 AD.
> > 
> > Can someone confirm ?
> > 
> > > > If it's possible with a Samba AD, what license do i need for
Windows and for Office ?
> > 
> > I don't know which one is better, SA / VDA / RDS CAL / ...
> > 
> > Thank you.
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> 
>  
> 
> > _
_
> BODDEN-KLINIKEN Ribnitz-Damgarten GmbH
> Sandhufe 2
> 18311 Ribnitz-Damgarten
> 
> Telefon: 03821-700-0
> Fax:   03821-700-240
> 
> > E-Mail: i...@bodden-kliniken.de   Internet: http://www.bodden-
kliniken.de
> 
> > Sitz: Ribnitz-Damgarten, Amtsgericht: Stralsund, HRB 2919, Steuer-
Nr.: 079/133/40188
> > Aufsichtsratsvorsitzende: Carmen Schröter, Geschäftsführer: Dr. Falko
 Milski
> 
> > > Der Inhalt dieser E-
Mail ist ausschließlich für den bezeichneten Adressaten bestimmt. Wen
n Sie nicht der vorge- 
> > > sehene Adressat dieser E-
Mail oder dessen Vertreter sein sollten, beachten Sie bitte, dass jed
e Form der Veröf- 
> > fentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser E-
Mail unzulässig ist. Wir bitten Sie, sofort den 
> Absender zu informieren und die E-Mail zu löschen. 
> 
> 
>  Bodden-Kliniken Ribnitz-Damgarten GmbH 2016
> *** Virenfrei durch Kerio Mail Server und Sophos Antivirus ***___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Replacing Certificates in hosted-engine cluster

2016-09-29 Thread Joshua Doll

If I have two CAs both claiming to be the root CA for a given Domain,
essentially both claiming to be the same CA, this won't cause issues with
communication between the engine and the two hosts? Does the CA used for
communication between the hosts and the engine only exist in some protected
trust store that is the only consulted source for this communication?

Thanks, Josh

On Thu, Sep 29, 2016, 6:53 AM Martin Perina  wrote:

> Hi,
>
> by default engine uses its own CA to sign certificates for HTTPS access
> and for engine-host communications. You can use your own CA only for HTTS
> certification.
> So if you are using oVirt 4.0 and you want to start to use custom CA for
> HTTPS certificates please take a look at Doc Text in:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1336838
> https://bugzilla.redhat.com/show_bug.cgi?id=1313379
>
> @Didi, are there any other steps required for hosted engine regarding
> custom CA?
>
> Thanks
>
> Martin Perina
>
>
>
> On Wed, Sep 28, 2016 at 1:07 PM, Joshua Doll 
> wrote:
>
>> Hi, I have a two node cluster running a hosted-engine setup. I have stood
>> up an enterprise CA and would like to replace the ovirt self signed
>> certificates. I can't find a list of all the certificates online. Is there
>> a list, or can someone point me in the right direction?
>>
>> Thanks, Josh
>>
>> ___
>> 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 4.0.x - hosted-engine was not starting properly

2016-09-29 Thread Artyom Lukianov

We have the same configuration under the file
/etc/httpd/conf.d/z-ovirt-engine-proxy.conf  for the regular engine under
3.6 and 4.0, so I do not sure if it relates to the problem.
About entropy level check the bug
https://bugzilla.redhat.com/show_bug.cgi?id=1357246.
Best Regards

On Thu, Sep 29, 2016 at 1:47 PM, Martin Perina  wrote:

> Hi,
>
> please take a look at my inline comments:
>
> On Tue, Sep 27, 2016 at 7:23 PM, Gervais de Montbrun <
> gerv...@demontbrun.com> wrote:
>
>> Hey All,
>>
>> Since updating to 4.0.x of oVirt, I have had an issue with my hosted
>> engine. After a some poking around, I think I have figured out my issue and
>> thought I would share to see what others think.
>> The issue has existed with 4.0, 4.0.1, 4.0.2, 4.0.3, and still exists in
>> 4.0.4.
>>
>> Description:
>> When my hosted engine starts it reports that it is in a degraded state
>> with 7 or 8 services still not started when I run systemctl status. It
>> takes about 6 or 7 minutes to eventually start all the services and come
>> online. If I don't set my cluster to Global-Maintenance mode it eventually
>> thinks that my hosted-engine needs to be rebooted and restarts it before it
>> can start everything.
>>
>
> Could you please share with us logs gathered by ovirt-log-collector?
>
> It's just a guess but could you please take a look if you HE VM has enough
> entropy?
>
>   cat /proc/sys/kernel/random/entropy_avail
>
> If the value is low (below or around 200),  you really need to install and
> configure some entropy generator such as haveged
>
>
>> Solution:
>> I realized that Apache was the culprit and found that the proxy to the
>> ovirt-engine in /etc/httpd/conf.d/z-ovirt-engine-proxy.conf has a super
>> long timeout with many retries. I changed the settings and now everything
>> works for me.
>>
>> -> Before change:
>>
>> > RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|
>> rhevm.ssh.key.txt$)>
>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5
>>
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css
>> text/html text/xml text/json application/xml application/json
>> application/x-yaml
>> 
>> 
>>
>>
>> -> After change:
>>
>> 
>> ProxyPassMatch ajp://127.0.0.1:8702 timeout=5 retry=2
>>
>> 
>> AddOutputFilterByType DEFLATE text/javascript text/css
>> text/html text/xml text/json application/xml application/json
>> application/x-yaml
>> 
>> 
>>
>>
> This one is correct for 4.0
> , not sure why it was not updated during upgrade from 3.6. @Simone?
> 
>
>
>>
>> If I read the timeout settings correctly, it will wait 60 minutes with 5
>> retries. 5 hours is way too long for my little server to hold onto all
>> those apache processes.
>>
> The change I made allows for there to be an error, and also releases
>> apache's hold on the process. Once everything is ready, apache is ready to
>> serve requests and everything/everyone is happy. Before making the change,
>> I just get a whitescreen in my browser and then nothing works until I
>> restart Apache (or I end up in an endless loop of ovirt-ha services
>> restarting my hosted-engine.
>>
>
> Well, if you have an issue with too many apache processes waiting for
> engine to respond, then there's some issue in engine. As I wrote above
> please share the logs with us and check entropy.
>
> Thanks
>
> Martin Perina
> 
>
>
>>
>> I noticed that this setting reverts to the original setting, so oVirt
>> must be writing this file. Perhaps these number can be changed in oVirt? If
>> not, I will just setup and ansible play to revert the settings with working
>> values and restart apache on my engine.
>> :-)
>>
>> Cheers,
>> Gervais
>>
>>
>>
>>
>> ___
>> 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
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Replacing Certificates in hosted-engine cluster

Hi,

by default engine uses its own CA to sign certificates for HTTPS access and
for engine-host communications. You can use your own CA only for HTTS
certification.
So if you are using oVirt 4.0 and you want to start to use custom CA for
HTTPS certificates please take a look at Doc Text in:

https://bugzilla.redhat.com/show_bug.cgi?id=1336838
https://bugzilla.redhat.com/show_bug.cgi?id=1313379

@Didi, are there any other steps required for hosted engine regarding
custom CA?

Thanks

Martin Perina

On Wed, Sep 28, 2016 at 1:07 PM, Joshua Doll  wrote:

> Hi, I have a two node cluster running a hosted-engine setup. I have stood
> up an enterprise CA and would like to replace the ovirt self signed
> certificates. I can't find a list of all the certificates online. Is there
> a list, or can someone point me in the right direction?
>
> Thanks, Josh
>
> ___
> 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 4.0.x - hosted-engine was not starting properly