Can anyone offer suggestions on how to figure out why when I create a
new VM and go to "Host" and try to select "Specific Host", although 2
nodes are listed it won't let me pick on of them?
No updates on the bug reported.
I tried ovirt-engine-4.0.2.7-1.el7.centos.noarch on both ovirt engine
On Fri, Aug 26, 2016 at 1:33 PM, InterNetX - Juergen Gotteswinter <
j...@internetx.com> wrote:
>
>
> Am 25.08.2016 um 15:53 schrieb Yaniv Kaul:
> >
> >
> > On Wed, Aug 24, 2016 at 6:15 PM, InterNetX - Juergen Gotteswinter
> > >
OVS is experimental and there is a open item on making migration work:
https://bugzilla.redhat.com/show_bug.cgi?id=1362495
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:
Is the VM very busy?
Did you apply the new cluster migration policies?
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 Fri, Aug 26, 2016 at
Le 26/08/2016 à 12:33, InterNetX - Juergen Gotteswinter a écrit :
Am 25.08.2016 um 15:53 schrieb Yaniv Kaul:
On Wed, Aug 24, 2016 at 6:15 PM, InterNetX - Juergen Gotteswinter
> wrote:
iSCSI & Ovirt is an
On Fri, Aug 26, 2016 at 12:06 PM, Gianluca Cecchi wrote:
> On Mon, Aug 22, 2016 at 2:04 PM, Sandro Bonazzola
> wrote:
>
>> The oVirt Project is pleased to announce the availability of an oVirt
>> 4.0.2 post release update, as of August 22nd,
one more thing, which i am sure that most ppl are not aware of.
when using thin provisioned disks for vms, hosted on iSCSI SAN Ovirt
uses a for me unusual way to do this.
Ovirt adds a new LVM LV for a vm, generates a Thin Qcow Image which is
written directly raw onto that LV. So for, ok, can be
On Fri, Aug 26, 2016 at 1:38 AM, Renout Gerrits wrote:
> Depends on your systemd configuration. ovirt-ha-agent and broker daemon's
> both log to stdout and it's own logfile. All messages to stdout will go to
> journald and be forwarded to /var/log/messages (ForwardToSyslog=yes in
Upgrade done. In my case, the engine was already updated to the latest
4.x release before the hosts.
Following marks 1 and 2 works fine.
After upgrading the cluster compatibility version, got message to reboot
all the VMs.
Don't know if I really have to do that.
On 08/23/2016 02:28 PM, Barak
Depends on your systemd configuration. ovirt-ha-agent and broker daemon's
both log to stdout and it's own logfile. All messages to stdout will go to
journald and be forwarded to /var/log/messages (ForwardToSyslog=yes in
/etc/systemd/journald.conf I think).
So the ovirt-ha-agent doesn't log to
10 matches
Mail list logo