> Can you share the engine and VDSM logs?
>
> On Wed, 12 May 2021 at 21:01, Patrick Lomakin wrote:
As I continued, I learned that a colleague had encountered this problem at
Proxmox. In this case, migrating the disk to the original storage helped start
the VM. In oVirt, this did not happen.
This looks to me like something I've been stumbling across several times...
When trying to redo a filed partial installation of HCI, I often stumbled
across volume setups not working, even if I had cleared "everything" via the
'cleanup partial install' button (I don't recall literally what it
It's better when you post distinct problems in distinct posts.
I'll answer on the CPU aspect, which may not be related to the networking topic
at all.
Sounds like you're adding Haswell parts to a farm that was built on Skylakes.
In order for VMs to remain mobile across hosts, oVirt needs to
Can you share the engine and VDSM logs?
On Wed, 12 May 2021 at 21:01, Patrick Lomakin
wrote:
> The weekend went horribly. I created a second storage domain in order to
> move all the virtual machines to a higher performance RAID array (From
> RAID6 to RAID10). My mistake was trying to move two
Can you share the engine and VDSM logs?
On Thu, 13 May 2021 at 20:05, Pavel Strzinek
wrote:
> Hello,
> I am having hard time migrating vms based on templates from existing 4.2.8
> instance to newly installed 4.4.6 HCI with different storage. When I export
> VMs and corresponding templates to
5 matches
Mail list logo