Ah - it found a oVirt VM called agent03 - that has nothing to do with the
engine VM.
I think I confused myself, and thought engine-setup did not like the engine
VM.
Actually it was complaining about an existing oVirt VM...Hmmm - this VM was
indeed set to 3.6.
Thank you!!
On Fri, Jul 5, 2019 at
This engine VM running as part of the oVirt cluster (not hosted engine/not
running under oVirt).
It is running on a separate libvirt/KVM server. This hypervisor is totally
separate and standalone: it is not a oVirt host.
This VM has been controlling the oVirt hosts since 3.6 days.
Inside this
On Fri, Jul 5, 2019 at 3:15 PM Simone Tiraboschi
wrote:
>
>
> On Fri, Jul 5, 2019 at 3:06 PM Richard Chan
> wrote:
>
>> In libvirt/virsh the VM is called "ovirt7"; here is the domain
>> definition. This VM has been upgraded from
>> 3.6->4.0->4.1->4.2. This is the first time engine-setup has
On Fri, Jul 5, 2019 at 3:06 PM Richard Chan
wrote:
> In libvirt/virsh the VM is called "ovirt7"; here is the domain
> definition. This VM has been upgraded from
> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
> about the "level" of the VM.
>
> libvirt domain definition:
In libvirt/virsh the VM is called "ovirt7"; here is the domain definition.
This VM has been upgraded from
3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
about the "level" of the VM.
libvirt domain definition:
ovirt7
cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
8388608
On Fri, Jul 5, 2019 at 2:48 PM Richard Chan
wrote:
> Hi,
>
> I am running 4.2 engine in a standalone libvirt KVM VM (running on a
> hypervisor that is not part of the oVirt infrastructure); i.e., I am not
> using hosted engine but still running engine in a VM.
>
> Now 4.3 won't upgrade inside
6 matches
Mail list logo
