HA OS not accessible from host

Installation
1

Hi
I have a old laptop with Ubuntu 16.04. I installed HA OS 12.0 as VM using KVM. The installation went fine and when the VM is booted, it comes up to the HA screen. When I checked the network info it resulted in 172.30.32.0/23 which is the internal docker address.
I am not able to access the localhost:8123 or ( my local Ip 192.168.. :8123) from my ubuntu desktop web browser. I cant access the docker ip as well from ubuntu…

From a config point of view
I havent connected to LAN . I am using Wifi. ( I tried to connect to LAN as well ) but still the same.
in my network setup of the HA VM, i tried using Virtual network ‘default’:NAT as the first option
second I changed it to Specify shared device name and gave my Bridge name br0.

Can someone help me point out where I am making the mistake in the network.

2

What hypervisor are you using. You don’t specify what your VM host is for anyone to assist that config.

3

But what KVM network configuration did you use when defining the VM?
This will define how to reach HA inside the VM

https://www.linux-kvm.org/page/Networking

4

For KVM try this guide, adjusting for whatever Linux OS you use.

5

QEMU_KVM
QEMU_KVM864×648 71.9 KB

ifconfig
ifconfig916×713 116 KB

attached is what I have now… If you see any immediate mistake pls let meknow. otherwise I am looking at the references given by you and others

6

This:
afbeelding

Nat will never be reachable, you need a bridge.

7

Yes… I have tried configuring the attached way as well…Still I am not able to access the HA

bridge
bridge867×353 49.6 KB

8

What did you try, exactly?
What is the IP the VM now gets?

9

When QEMU/KVM gets installed, it comes up with a few networking defaults which includes virbr0. I’m not sure it is really connected to the outside world, but to be honest, I never used it. I created my own bridge br0, which is a common practice, and you can find in several QEMU/KVM install guides including the one posted above how to create it, and make it master over your Ethernet interface which does connect to the outside world.

10

I changed the network from NAT to specify a shared drive name and chose the virbr0.
The entire IP range of all that is running is as below … the docker gets as usual 172 range…
docker0 Link encap:Ethernet HWaddr 02:42:f5:72:70:54
inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

enp0s25 Link encap:Ethernet HWaddr 10:1f:74:77:eb:2e
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:8252 errors:0 dropped:63 overruns:0 frame:0
TX packets:4237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1354286 (1.3 MB) TX bytes:519928 (519.9 KB)
Interrupt:17 Memory:d0700000-d0720000

enp0s26u1u5i6 Link encap:Ethernet HWaddr 02:15:e0:ec:01:00
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:9919268 errors:0 dropped:0 overruns:0 frame:0
TX packets:9919268 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1737792241 (1.7 GB) TX bytes:1737792241 (1.7 GB)

virbr0 Link encap:Ethernet HWaddr de:b3:b8:77:d4:13
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:128 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:13368 (13.3 KB)

virbr0-nic Link encap:Ethernet HWaddr 52:54:00:1f:96:d2
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vnet0 Link encap:Ethernet HWaddr de:b3:b8:77:d4:13
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vnet1 Link encap:Ethernet HWaddr fe:54:00:99:5c:d3
inet6 addr: fe80::fc54:ff:fe99:5cd3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:8746 (8.7 KB)

wlo1 Link encap:Ethernet HWaddr c8:f7:33:52:45:5e
inet addr:192.168.68.78 Bcast:192.168.71.255 Mask:255.255.252.0
inet6 addr: fd2b:68bc:8454:e581:fef3:13a6:2c55:fd67/64 Scope:Global
inet6 addr: fe80::565e:ae4:27e2:3d96/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1395741 errors:0 dropped:182 overruns:0 frame:0
TX packets:681013 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1739184263 (1.7 GB) TX bytes:70428945 (70.4 MB)

11

That’s on the host, isn’t it?
I was asking about the VM.

12

Generally in the KVM GUI it should display the Ipaddress and its not. ( atleast some videos shows that)
Once the VM boots I see only the HA prompt and it displays only the docker IP address.(172.*)
I googled a bit and tried with the Vrish list and it doesnt show any thing as well…

I think I am doing something terribly stupid…
In the meantime I tried to install HA as a docker in the host and and it works for now…