10.02.2018 00:48, reznikov...@soskol.com пишет:
Simone Tiraboschi писал 2018-02-09 15:17:
It shouldn't happen.
I suspect that something went wrong creating the configuration volume
on the shared storage at the end of the deployment.
Alexei, can both of you attach you hosted-engine-setup logs?
All,
I was wondering if someone can point me in the direction of the
documentation related to defining custom network filters (nwfilter) in
4.2. I found the docs on assigning a network filter to a vNIC profile,
but I cannot find any mention of how you can create your own. Normally
you'd use
Hi folks,
Sorry it's taken me a while to get back to this! I've just updated to
4.2.1 and am still seeing the issue. I've collected the vdsm.log and
supervdsm.log from my SPM host after trying to start my broken VM: they
are available from:
2018-02-12 17:43 GMT+01:00 Gianluca Cecchi :
> On Mon, Feb 12, 2018 at 4:22 PM, Lev Veyde wrote:
>
>> The oVirt Project is pleased to announce the availability of the oVirt 4.
>> 2.1 Release, as of February 12th, 2018
>>
>> This update is a release
A little update:
I found out that I have to activate *Hostdev Passthrough* (is this really
necessary for USB devices?). Now I see all the devices and I can add also
an USB device.
But I'm still not able to disconnect the USB from the old VM.
-- Forwarded message --
From: Jon bae
On Mon, Feb 12, 2018 at 4:22 PM, Lev Veyde wrote:
> The oVirt Project is pleased to announce the availability of the oVirt 4.2
> .1 Release, as of February 12th, 2018
>
> This update is a release of the first in a series of stabilization
> updates to the 4.2
> series.
>
> This
Hi,
this should work according to my gluster colleagues.
The recommended way to install this would be by using one of the
"full" nodes and deploying hosted engine via cockpit there. The
gdeploy plugin in cockpit should allow you to configure the arbiter
node.
The documentation for deploying
Hi,
I'm trying to install oVirt 4.2 as 2-Node Hyperconverged System based on
glusterfs.
A third node should be used as glusterfs arbiter Node and to provide Quorum for
the Cluster.
The third node is a small PCEngines APU2 Host, so it is not usable as
Hypervisor.
My question is: Is this kind
The oVirt Project is pleased to announce the availability of the oVirt 4.2.1
Release, as of February 12th, 2018
This update is a release of the first in a series of stabilization updates
to the 4.2
series.
This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux
Hello,
I run oVirt 4.2.1, in 4.1 I added a USB device to a VM and now I wanted to
change this device to a different VM.
But I found out, that I'm not able to remove this device nor I'm able to
add any device to any VM. The device list is empty.
I found a bug report, what describe this error:
Am 2018-02-12 um 13:40 schrieb Idan Shaby:
On Mon, Feb 12, 2018 at 1:55 PM, Matthias Leopold
> wrote:
Hi Idan,
thanks for your answer. But i'm still confused, because i thought
that the content of
On Mon, Feb 12, 2018 at 1:55 PM, Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:
> Hi Idan,
>
> thanks for your answer. But i'm still confused, because i thought that the
> content of /sys/block/dm-X/queue/discard* in the VM OS should depend on the
> setting of the
09.02.2018 21:13, Alex K пишет:
Hi,
did you select "Deploy" when adding the new host?
See attached.
Inline image 2
Thanx,
Alex
On Fri, Feb 9, 2018 at 9:53 AM, Reznikov Alexei
> wrote:
Hi all!
After upgrade from ovirt 4.0 to
On Sun, Feb 11, 2018 at 9:33 AM, Yaniv Kaul wrote:
>
>
> On Sat, Feb 10, 2018 at 8:41 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Fri, Feb 9, 2018 at 4:32 PM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>>
>>>
>>> If I edit the VM, in
"no default route" bug was fixed only on 4.2.1
Your current version doesn't have the fix
On Mon, Feb 12, 2018 at 11:09 AM, wrote:
>
>
>
>
> Le 12-Feb-2018 08:06:43 +0100, jbe...@redhat.com a écrit:
>
> > This option relevant only for the upgrade from 3.6 to 4.0(engine had
Le 12-Feb-2018 08:06:43 +0100, jbe...@redhat.com a crit:
> This option relevant only for the upgrade from 3.6 to 4.0(engine had
> different OS major versions), it all other cases the upgrade flow very
> similar to upgrade flow of standard engine environment.
>
>
> 1. Put hosted-engine
I could not understand what you exactly have working now and what you are
looking to add.
Perhaps share a diagram or try to describe it in more details.
Thanks,
Edy.
On Sun, Feb 11, 2018 at 3:00 AM, Wesley Stewart wrote:
> This might be a stupid question. But I am testing
Hi, I have tried this but it didn't solved the problem. I removed the disk and
tried to boot with an ISO but no more success. As I need to work on what was
installed on this disk, I tried the most violent but efficient solution :
destroying the VM and recreating it, keeping its mac address.
Hi, This is the whole message. Here you get the whole output of the process. I
runned these commands on the node hosting the engine vm. But if there is a more
efficient workflow, I am interrested in it ! # yum -y update Modules
complmentaires chargs : fastestmirror
base | 3.6 kB 00:00:00
On Mon, Feb 12, 2018 at 8:22 AM, Russell Wecker
wrote:
> I have a hosted engine setup that when I ran the system updates for it,
> and it will not boot.
>
Did you set global maintenance mode at update time?
If not, ovirt-ha-agent could try to restart the engine VM for
20 matches
Mail list logo