On Fri, 1 Feb 2019 17:37:30 -0500
Darin Schmidt wrote:
> [root@ovirt ~]# rpm -qa kernel
> [root@ovirt ~]# uname -a
> Linux ovirt 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018
Thank you for your reply :).
I don't think is the network filters, i have also created a new OVN network
to check but still the vm dont boot-up on the hosts that have been
On Fri, 1 Feb 2019, 21:56 Dominik Holler On Fri, 1 Feb 2019 15:31:18 +0200
> ada per wrote:
> > After
On Sat, 2 Feb 2019 12:53:13 +0200
ada per wrote:
> Thank you for your reply :).
> I don't think is the network filters, i have also created a new OVN
> network to check but still the vm dont boot-up on the hosts that have
> been upgraded.
Can you please share the vdsm.log from a host
We are happy oVirt users for some years now (we started with 3.6, now on 4.2)
and we manage most of our virtualization stacks with it. To provision and
manage our machines, we use the foreman (for bare metal and virtual machines)
on top of it. I made some little contributions to the
Thanks, that sort of helped. I've ran yum update a dozen times and not till
this morning was there a kernel update... lol
I'm able to startup the VM, but when it loads the ISO to install Windows 10
which I downloaded from Microsoft, Attached is what always happens. Perhaps
my ISO is corrupt?
No. As I said, ICMP is routed through correctly without any issue. The routing
is correct, and the machine at 1.13 is definitely forwarding requests
correctly. I've tested from another machine on my LAN, same setup except not
running Centos/ovirt and it's got no problem with communication.
How is an oVirt hyperconverged cluster supposed to come back to life after
a power outage to all 3 nodes?
Running ovirt-node (ovirt-node-ng-installer-4.2.0-2019013006.el7.iso) to
get things going, but I've run into multiple issues.
1. During the gluster setup, the volume sizes I specify, are not
Mail list logo