Do these files exist on the hosted engine? I am a Ovirt newbie but it sounds
like file or disk corruption.
How much actual storage space is left on the volume with he prob files? Or the
hosted engine disk?
Can you ssh into the hosted engine and put it in global maintenance and rerun
On April 9, 2020 11:12:30 AM GMT+03:00, Shareef Jalloq
>OK, let's go through this. I'm looking at the node that at least still
>some VMs running. virsh also tells me that the HostedEngine VM is
>but it's unresponsive and I can't shut it down.
>1. All storage domains
oVirt 4.4.0 Beta release refresh is now available for testing
The oVirt Project is excited to announce the availability of the beta
release of oVirt 4.4.0 refresh for testing, as of April 9th, 2020
This release unleashes an altogether more powerful and flexible open source
OK, let's go through this. I'm looking at the node that at least still has
some VMs running. virsh also tells me that the HostedEngine VM is running
but it's unresponsive and I can't shut it down.
1. All storage domains exist and are mounted.
2. The ha_agent exists:
On Thu, Apr 9, 2020 at 7:46 AM Krutika Dhananjay
> On Tue, Apr 7, 2020 at 7:36 PM Gianluca Cecchi
>> OK. So I set log at least at INFO level on all subsystems and tried a
>> redeploy of Openshift with 3 mater nodes and 7 worker nodes.
>> One worker got the error and VM
for educational purposes I'm trying to access the QEMU monitor of oVirt
VMs. Can someone tell me how this can be done? Connecting to the unix
socket with socat doesn't work, probably because it's not started with
"server,nowait". Can the QEMU monitor be reached with the SPICE console?
Does anyone know how i can allow my Firewall VM cluster act as the default
gateway to VMs within the same network?
I've configured the GARP functionality on the OPNSENSE firewalls (PFSENSE fork).
VMs within the same network can ping the firewall IP addresses successfully but
not the GARP
On Thu, Apr 9, 2020 at 10:49 AM Sandro Bonazzola
> oVirt 4.4.0 Beta release refresh is now available for testing
> The oVirt Project is excited to announce the availability of the beta
> release of oVirt 4.4.0 refresh for testing, as of April 9th, 2020
> This release unleashes an
thank's for the reply.
In this case, the bounding, I think, is inapropriate.
The dell compellent has 2 "fault domain" with différent IP network
This is a iSCSI array with 8 front-end ports (4 per controller). The iSCSI
network is simple: two independant switches with a single VLAN,
It’s the same problem all over again.
iSCSI in oVirt/RHV is broken. For years.
Reported this a while: https://bugzilla.redhat.com/show_bug.cgi?id=1474904
iSCSI Multipath in the engine does not means a thing. It’s broken.
I don’t know why the oVirt team does not acknowledge this. I’m being an
Mail list logo