On Thu, Feb 6, 2020 at 8:47 PM Strahil Nikolov wrote:
>
> On February 6, 2020 6:21:02 PM GMT+02:00, d...@bornfree.org wrote:
> >I'd like to update my hosted engine to version 4.3.8 from 4.3.7, but
> >have concerns.
> >
> >First, on the hosted engine, yum reports that several packages are
>
On Thu, Feb 6, 2020 at 5:39 PM wrote:
>
> Hi am trying to upgrade our ovirt hosts and engine in our Hyperconverged
> 4.3.6 environment to 4.3.7, we do not want to go to 4.3.8.
> Where can I find the correct repositories for 4.3.7 specific to the engine
> and the ones for the hosts?
We do
Same problem. Looks like the virtio rpm is now built with the new compression
method, but rpm for EL7 hasn't been updated to support it.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
Dear Amit.
That is not exactly the issue we're facing; I have two clusters an old
4.2 cluster and a fresh 4.3 cluster. The DC is set to 4.2 because of this.
I wish to bring the 4.3 cluster online and migrate everything to it,
then remove the 4.2 cluster.
This should be a path that can be taken
Hey folks,
quick question: If I would like to use specific versions (contained
within the host) and craft myself a specific environment for the hosts
am I correct to assume that only installing the ovirt repo and a gluster
version of my choice (cough, 7.0) would suffice? Then adding the host
FYI
This also fixed the previous issues I was having with 2k19 servers that I was
trying to migrate the disk image from Proxmox that was throwing the BSOD of
KMODE EXCEPTION.
From: Robert Webb
Sent: Saturday, February 8, 2020 11:30 AM
To: users
Subject: [ovirt-users] Re: Win Server 2k19
So I have been running Windows Server 2019 on Proxmox VE with Blue Iris NVR.
Tried to migrate the qcow disk over to oVirt, and like other Win2k19 servers,
they all give a BSOD with a KMODE error.
Last night I installed 2k19 from scratch, installed the latest drivers I could
find,
Update:
So after some digging, it seems this has been reported as an issue many times.
As a workaround, I added the an entry to the kvm.conf in modprobe.d directory
of ignore_msrs=1 and that allowed Blue Iris to boot.
Would be nice to have an actual fix for this instead of a workaround. Would
On January 30, 2020 4:28:38 PM GMT+02:00, Sandro Bonazzola
wrote:
>The oVirt Project is pleased to announce the availability of the oVirt
>4.3.9 First Release Candidate for testing, as of January 30th, 2020.
>
>This update is a release candidate of the nineth in a series of
>stabilization
I doubt if you can use 4.3.8 nodes with a 4.2 cluster without upgrading it
first. But myabe members of this list could say differently.
On Friday, February 7, 2020, Jorick Astrego wrote:
>
> On 2/6/20 6:22 PM, Amit Bawer wrote:
>
>
>
> On Thu, Feb 6, 2020 at 2:54 PM Jorick Astrego wrote:
>
>>
What does the event log and system logs say? Does the storage domain
give any indication why it wont activate?
Given you say using local storage, I assume you are mounting it via NFS
locally ? If so check NFS mounts etc.
Given it happened after a reboot im guessing it will be something
11 matches
Mail list logo
