On 21.07.16 16:24, Cam Mac wrote:
> Bug ID 1358828. I can do another for the direct import of the OVF (without
Thanks,
Please attach the ovf and ova (no need for the disk inside the ova) to the
bug.
> virt-v2v) if needed.
>
> Cheers,
>
> Cam
>
> On Thu, Jul 21, 2016 at 2:56 PM, Shahar Havivi wr
dear friends:
recently i meet some problem:My company meeted interruption of power
supply,which cause my server power off directly.when i start the server,it
adviced to user fsck comnmand to repair FS.I did it and know my system had some
bad block.And then i enter the ovirt's WEB administrat
Hello oVirt guru`s !I have problem with initial deploy of ovirt 4.0 hosted engine.My environment :* Two servers HP ProLiant DL 360 G5 with Qlogic FC HBA connected (with multipathd) to storage HP 3PAR 7200* On each server installed CentOS 7.2 Linux (3.10.0-327.22.2.el7.x8
Opened a bug on the issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1359489
Should be addressed for the upcoming builds.
On Thu, Jul 21, 2016 at 5:43 PM, Alessandro De Salvo <
alessandro.desa...@roma1.infn.it> wrote:
> Hi Daniel,
>
> On Thu, 2016-07-21 at 17:34 +0300, Daniel Erez wrote:
> >
>
Hi,
It was indeed NetApp, and as you say I can remember something like it
but I'm not 200% sure.
For some host that I wasn't able to remove I needed hosted-engine
--reinitialize-lockspace indeed, figured that out.
dd over the same went well, didn't see anyone complaining about that either.
Than
On Wed, Jul 20, 2016 at 12:00 AM, Groten, Ryan
wrote:
> Hey Ansible users,
>
>
>
> I wrote a module for storage management and created a pull request to have
> it added as an Extra module in Ansible. It can be used to
> create/delete/attach/destroy pool disks.
>
>
>
> https://github.com/ansible/
Hi all,
I wrote a blog post that summarizes the recent improvements in the code that
monitors virtual machines in oVirt.
It describes the changes that were done and shows a comparison of different
aspects of oVirt with these changes
(based on the master branch) vs oVirt 3.6 without these changes
Hi guys,
On a 4.0.1 install where I use an hosted engine the engine itself
starts very quick, this works great.
The issue I see happening is that when the engine is started it can
take up to minutes before you can visit the GUI of the engine.
Is this known and also happening on 3.6 ?
Thanks!
M
On Sun, Jul 24, 2016 at 8:56 PM, Matt . wrote:
> Hi guys,
>
> On a 4.0.1 install where I use an hosted engine the engine itself
> starts very quick, this works great.
>
> The issue I see happening is that when the engine is started it can
> take up to minutes before you can visit the GUI of the e
Hi,
I could be Rdns at the moment as I'm having strange Virtio issues on
4.0, nics are doing strange on Linux VM's ??
If it's started it's just fine and fast
I will update this thread when DNS is up again as I needed to
reference this a little but... at the other end... I thought it
happened
Hi Matt,
I noticed a similar issue with oVirt 4.0 that I did not see in 3.6. In
this particular environment, I don't run the DNS resolvers so I can't speak
to as whether that was a problem at the time (I doubt it, but you never
know).
One thing that seemed to help for me was to increase availabl
Hi, all:
I tried to deploy an hosted engine, but I got an error:
[root@node ~]# hosted-engine --deploy
..
--== CONFIGURATION PREVIEW ==--
Bridge interface : enp6s0f0
Engine FQDN: engine.horebdata.cn
Bridg
Simone, there is something interesting in the vdsm.log?
22.07.2016, 19:36, "aleksey.maksi...@it-kb.ru" :
> Simone, thanks for link.
> vdsm.log attached
>
> 22.07.2016, 19:28, "Simone Tiraboschi" :
>> On Fri, Jul 22, 2016 at 5:59 PM, wrote:
>>> Thank you for your response, Simone.
>>>
>>> Log
Hi,
Thanks for the logs. So I have identified one issue from the logs for which
the fix is this: http://review.gluster.org/#/c/14669/. Because of a bug in
the code, ENOENT was getting converted to EPERM and being propagated up the
stack causing the reads to bail out early with 'Operation not permi
14 matches
Mail list logo
