4:40 p.m.
Hi Jakov,
The oVirt architecture basics:
- The self-host engine is a VM running on a KVM host.
To deploy a self-hosted engine, you must have a shared storage like a NFS share or iSCSI
LUN.
- Running the engine-setup command will deploy the stand-alone engine.
The host running a stand-alone engine cannot act as a hypervisor at the same time.
Acting as an Administration server and a Hypervisor at the same time is not allowed.
Marcos
-----Original Message-----
From: jakov.jelinic(a)adriatic.hr <jakov.jelinic(a)adriatic.hr>
Sent: Friday, July 12, 2024 4:14 AM
To: users(a)ovirt.org
Subject: [External] : [ovirt-users] Network issue - self-hosted engine on a single host
Hi,
I'm confused about installing ovirt as a self-hosted engine on a single host with
local storage.
I have one server which I have connected to 2 switches (which are in "Cisco
stack"). I have connected the server with 2 UTP cables in master switch and 2 UTP
cables in slave.
I have installed on server Rocky Linux 9.4. And now i have 4 network interfaces (4 ip
addresses) which i can ping from my computer.
After that I installed ovirt engine 4.5.6-1.el9 with the next commands:
dnf install centos-release-ovirt45
dnf install ovirt-engine
engine-setup
Next step, I want to add a new host through my engine (Compute -> Hosts ->
New). I started installing a new host. I choose my hostname to be my one and only
server.
After installation, I can no longer connect to my server:
https://urldefense.com/v3/__https://vhost01.testing.local/ovirt-engine/__...
because the ip address behind the dns name can no longer be pinged. Out of my 4 IP
addresses, I can now ping only one from my computer. And then, of course, I change the DNS
record and set it to that one-onlyworking IP address. So I think after adding the host my
network is messed up. It even makes sense to me since everything is done on one host, and
it seems to me that if I had separated the engine, it would not have these problems.
This was my network before adding new host:
ens13f0np0: connected to ens13f0np0
"Broadcom and subsidiaries BCM57454 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb"
ethernet (bnxt_en), 14:23:F2:5A:B8:E4, hw, mtu 1500 ip4 default
inet4 192.168.50.60/24
route4 192.168.50.0/24 metric 100
route4 default via 192.168.50.2 metric 100
inet6 fe80::1623:f2ff:fe5a:b8e4/64
route6 fe80::/64 metric 1024
ens13flnpl: connected to ens13flnpl
"Broadcom and subsidiaries BCM57454 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb"
ethernet (bnxt_en), 14:23:F2:5A:B8:E5, hw, mtu 1500
inet4 192.168.50.54/24
route4 192.168.50.0/24 metric 101
route4 default via 192.168.50.2 metric 101
inet6 fe80::1623:f2ff:fe5a:b8e5/64
route6 fe80::/64 metric 1024
ens13f2np2: connected to ens13f2np2
"Broadcom and subsidiaries BCM57454 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb"
ethernet (bnxt_en), 14:23:F2:5A:B8:E6, hw, mtu 1500
inet4 192.168.50.78/24
route4 192.168.50.0/24 metric 102
route4 default via 192.168.50.2 metric 102
inet6 fe80::1623:f2ff:fe5a:b8e6/64
route6 fe80::/64 metric 1024
ens13f3np3: connected to ens13f3np3
"Broadcom and subsidiaries BCM57454 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb"
ethernet (bnxt_en), 14:23:F2:5A:B8: E7, hw, mtu 1500
inet4 192.168.50.109/24
route4 192.168.50.0/24 metric 103
route4 default via 192.168.50.2 metric 103
inet6 fe80::1623:f2ff:fe5a:b8e7/64
route6 fe80::/64 metric 1024
lo: connected (externally) to lo
"10"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 inet4 127.0.0.1/8
inet6
::1/128
route6:1/128 metric 256
virbro: connected (externally) to virbro "virbro"
bridge, 52:54:00:11:F7:8C, sw, mtu 1500
inet4 192.168.122.1/24
route4 192.168.122.0/24 metric 0
and this is after adding new host:
ens13f1np1: connected to ens13f1np1
"Broadcom and subsidiaries BCM57454 NetXtreme-E
10Gb/25Gb/40Gb/50Gb/100Gb"
ethernet (bnxt_en), 14:23:F2:5A:B8:E5, hw, mtu 1500
ip4 default
inet4 192.168.50.54/24
route4 192.168.50.0/24 metric 100
route4 default via 192.168.50.2 metric 100
inet6 fe80::1623:f2ff:fe5a:b8e5/64
route6 fe80::/64 metric 1024
ovirtmgmt: connected to ovirtmgmt
"ovirtmgmt"
bridge, 14:23:F2:5A:B8:E4, sw, mtu 1500
inet4 192.168.50.60/24
route4 192.168.50.0/24 metric 425
inet6 fe80::1623:f2ff:fe5a:b8e4/64
route6 fe80::/64 metric 1024
ens13f2np2: connected to ens13f2np2
"Broadcom and subsidiaries BCM57454 NetXtreme-E
10Gb/25Gb/40Gb/50Gb/100Gb"
ethernet (bnxt_en), 14:23:F2:5A:B8:E6, hw, mtu 1500
inet4 192.168.50.78/24
route4 192.168.50.0/24 metric 101
route4 default via 192.168.50.2 metric 101
inet6 fe80::1623:f2ff:fe5a:b8e6/64
route6 fe80::/64 metric 1024
ens13f3np3: connected to ens13f3np3
"Broadcom and subsidiaries BCM57454 NetXtreme-E
10Gb/25Gb/40Gb/50Gb/100Gb"
ethernet (bnxt_en), 14:23:F2:5A:B8:E7, hw, mtu 1500
inet4 192.168.50.109/24
route4 192.168.50.0/24 metric 102
route4 default via 192.168.50.2 metric 102
inet6 fe80::1623:f2ff:fe5a:b8e7/64
route6 fe80::/64 metric 1024
ens13f0np0: connected to ens13f0np0
"Broadcom and subsidiaries BCM57454 NetXtreme-E
10Gb/25Gb/40Gb/50Gb/100Gb"
ethernet (bnxt_en), 14:23:F2:5A:B8:E4, hw, mtu 1500
master ovirtmgmt
lo: connected (externally) to lo
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
inet4 127.0.0.1/8
inet6 ::1/128
route6 ::1/128 metric 256
br-int: disconnected
"br-int"
ovs-interface (openvswitch), 12:47:1C:18:8F:E2, sw, mtu 1500
Can you plese help?
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement:
https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!...
oVirt Code of Conduct:
https://urldefense.com/v3/__https://www.ovirt.org/community/about/communi...
List Archives:
https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@o...