Hi Alex,
Please provide Engine logs from when this is occurring and mention the
date/time we should focus at.
Thanks,
Edy.
On Mon, Feb 5, 2018 at 2:19 PM, Alex K wrote:
> Hi all,
>
> I have a 3 nodes ovirt 4.1 cluster, self hosted on top of glusterfs. The
> cluster
On Sun, Feb 4, 2018 at 10:01 PM, Vincent Royer
wrote:
> I had these types of issues as well my first time around, and after a
> failed engine install I haven't been able to get things cleaned up, so I
> will have to start over. I created a bonded interface on the host
On Mon, Feb 05, 2018 at 10:57:58PM +0100, Luca 'remix_tj' Lorenzetto wrote:
> On Fri, Feb 2, 2018 at 12:52 PM, Richard W.M. Jones wrote:
> > There is a section about this in the virt-v2v man page. I'm on
> > a train at the moment but you should be able to find it. Try to
> >
On Fri, Feb 2, 2018 at 12:52 PM, Richard W.M. Jones wrote:
> There is a section about this in the virt-v2v man page. I'm on
> a train at the moment but you should be able to find it. Try to
> run many conversions, at least 4 or 8 would be good places to start.
Hello Richard,
Do you have the guest agent installed?
On Mon, Feb 5, 2018 at 4:18 PM, maoz zadok wrote:
> Hi All,
> Is it possible that the "IP addresses" of the guest virtual machine will
> be shown? it currently empty.
>
> [image: Inline image 1]
>
>
>
>
>
Hi All,
Is it possible that the "IP addresses" of the guest virtual machine will be
shown? it currently empty.
[image: Inline image 1]
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Answering my own post... a restart of vdsmd on the affected blade has
fixed everything. Thanks everyone who helped.
On 02/05/2018 10:02 AM, Christopher Cox wrote:
Forgive the top post. I guess what I need to know now is whether there
is a recovery path that doesn't lead to total loss of the
Hi Luca,
Thank you for your interst in the Disaster Recovery ansible solution, it is
great to see users get familiar with it.
Please see my comments inline
Regards,
Maor
On Mon, Feb 5, 2018 at 7:54 PM, Yaniv Kaul wrote:
>
>
> On Feb 5, 2018 5:00 PM, "Luca 'remix_tj'
On Feb 5, 2018 5:00 PM, "Luca 'remix_tj' Lorenzetto" <
lorenzetto.l...@gmail.com> wrote:
Hello,
i'm starting the implementation of our disaster recovery site with RHV
4.1.latest for our production environment.
Our production setup is very easy, with self hosted engine on dc
KVMPDCA, and virtual
On Fri, Feb 2, 2018 at 9:10 PM, Thomas Davis wrote:
> Is this supported?
>
> I have a node, that centos 7.4 minimal is installed on, with an interface
> setup for an IP address.
>
> I've yum installed nothing else except the ovirt-4.2.1-pre rpm, run
> screen, and then do the
Forgive the top post. I guess what I need to know now is whether there
is a recovery path that doesn't lead to total loss of the VMs that are
currently in the "Unknown" "Not responding" state.
We are planning a total oVirt shutdown. I just would like to know if
we've effectively lot those
Following the minor release upgrade instructions on
https://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases/
solved this issue. Now we are bumping into an other issue, for which
I'll probably open an other thread.
frank
On 02/02/2018 05:33 PM, Chas
Hello,
i'm starting the implementation of our disaster recovery site with RHV
4.1.latest for our production environment.
Our production setup is very easy, with self hosted engine on dc
KVMPDCA, and virtual machines both in KVMPDCA and KVMPD dcs. All our
setup has an FC storage backend, which is
On Mon, Feb 5, 2018 at 3:08 PM, wrote:
> El 2018-02-05 14:03, Simone Tiraboschi escribió:
>
>> On Mon, Feb 5, 2018 at 2:46 PM, wrote:
>>
>> Hi,
>>>
>>> We're trying to upgrade from 4.1.9 to 4.2.x and we're bumping into
>>> an error we don't know how to
Hello,
i'm starting the implementation of our disaster recovery site with RHV
4.1.latest for our production environment.
Our production setup is very easy, with self hosted engine on dc
KVMPDCA, and virtual machines both in KVMPDCA and KVMPD dcs. All our
setup has an FC storage backend, which is
Hi Frank,
can you please send a vdsm logs? The 4.2 release added the little different
deployment from the engine.
Now the ansible is also called. Although I am not sure if this is your case.
I would go for entirely removing the vdsm and installing it from scratch if
it is possible for you.
This
El 2018-02-05 14:03, Simone Tiraboschi escribió:
On Mon, Feb 5, 2018 at 2:46 PM, wrote:
Hi,
We're trying to upgrade from 4.1.9 to 4.2.x and we're bumping into
an error we don't know how to solve. As per [1] we run the
'engine-setup' command and it fails with:
[ INFO ]
On Mon, Feb 5, 2018 at 2:46 PM, wrote:
> Hi,
>
> We're trying to upgrade from 4.1.9 to 4.2.x and we're bumping into an
> error we don't know how to solve. As per [1] we run the 'engine-setup'
> command and it fails with:
>
> [ INFO ] Rolling back to the previous PostgreSQL
Hi,
I'm currently stuck - after upgrading 4.1 to 4.2 I cannot start the
host-processes.
systemctl start vdsmd fails with following lines in journalctl:
Feb 05 14:40:15 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: vdsm: Running wait_for_network
Feb 05 14:40:15
Hi,
We're trying to upgrade from 4.1.9 to 4.2.x and we're bumping into an
error we don't know how to solve. As per [1] we run the 'engine-setup'
command and it fails with:
[ INFO ] Rolling back to the previous PostgreSQL instance (postgresql).
[ ERROR ] Failed to execute stage 'Misc
On Fri, Feb 2, 2018 at 12:13 PM, Jordan, Marcel
wrote:
> Hi,
>
> i have some NVIDIA Tesla P100 and V100 gpu in our oVirt 4.2 cluster and
> searching for a documentation how to use the new vGPU feature. Is there
> any documentation out there how i configure it
Hi,
I have experimented on the issue and figured out the reason for the
original issue.
You are right, that the vm1 is not properly stopped. This is due to the
known issue in the graceful shutdown introduced in the ovirt 4.2.
The vm on the host in shutdown are killed, but are not marked as
Hi all,
I have a 3 nodes ovirt 4.1 cluster, self hosted on top of glusterfs. The
cluster is used to host several VMs.
I have observed that when gateway is lost (say the gateway device is down)
the ovirt cluster goes down.
It seems a bit extreme behavior especially when one does not care if the
Hi,
i have some NVIDIA Tesla P100 and V100 gpu in our oVirt 4.2 cluster and
searching for a documentation how to use the new vGPU feature. Is there
any documentation out there how i configure it correctly?
--
Marcel Jordan
signature.asc
Description: OpenPGP digital signature
Dear Martin,
Um..Since i am going to use HPE ProLiant DL360 Gen10 Server to setup oVirt
Node(Hypervisor). HP G10 is using ilo5 rather than ilo4. Therefore, i would
like to ask whether oVirt power management support iLO5 or not.
If not, do you have any idea to setup power management with HP G10?
On Mon, Feb 5, 2018 at 9:09 AM, maoz zadok wrote:
> Hi All,
> What do you think about installing the host engine on a virtual machine
> hosted on the same cluster managing it?
> is it make sense?
> I don't like the alternative to install it on physical hardware, on the
> other
Hi All,
What do you think about installing the host engine on a virtual machine
hosted on the same cluster managing it?
is it make sense?
I don't like the alternative to install it on physical hardware, on the
other hand, if the host hosting the engine fall, there will be no access to
management.
27 matches
Mail list logo