Homeassistant virtual machine

Installation
34

Can you scroll down so we can a actually see an error?
Even better would be to see the whole file :thinking:

Whant you meamt is. you created MAC reservations on you routers DHCP ( in which the D stands for dynamic, so not static :thinking:)

What IP’s did you reserve for HA? 192.168.1.150:8?

And some more questions:

  • What is the IP address of ypur router?
  • What netmask do you use on the router?
  • What is the IP address of the host now?
  • From the host, can you ping 192.168.1.150:8 ?
35

The log file is 30 pages.

Yes

192.168.1…245

192.168.1.1

255.255.255.0

192.168.1.247

HAVM error11

36

HAVM error12

I had to wait, due to the limitations of the forum for new users, to be able to insert this other screenshot.

37

You pinged the host from the host…that should always work,
I find it a bit weird though it is more than 10ms ??
Since this is the local address, that should be less then 1ms…
This is my local ping, even less than 0.1 ms :thinking:

aceindy@CND6346CXY:~$ ping 192.168.101.9
PING 192.168.101.9 (192.168.101.9) 56(84) bytes of data.
64 bytes from 192.168.101.9: icmp_seq=1 ttl=64 time=0.075 ms
64 bytes from 192.168.101.9: icmp_seq=2 ttl=64 time=0.054 ms
64 bytes from 192.168.101.9: icmp_seq=3 ttl=64 time=0.067 ms
64 bytes from 192.168.101.9: icmp_seq=4 ttl=64 time=0.088 ms

Are you sure 247 is the host?

Can you ping HA [192.168.1.245??] from the host [192.168.1.247??] (or from any other machine in your network that is)

And how about opening http://192.168.1.245:4357 (which should give you the status of the supervisor:

image
image774×273 7.93 KB

38

Ping from 192.168.1.247 (Host) to 192.168.1.245 (VM)

HAVM error13

39

HAVM error14
HAVM error14777×270 24.2 KB

40

From minipc (192.168.1.247) to notebook connected via wifi on the same network (192.168.1.3)

HAVM error15

41

From the notebook connected via wifi to the same network (192.168.1.3) to the minipc (192.168.1.247) and to the VM (192.168.1.245).

In fact, from the minipc I see the notebook online and on the contrary NO.

HAVM error16

42

HAVM error17
HAVM error17798×880 197 KB

43

Do you have any idea?

44

If http://192.168.1.245:4357 works, it is very weird http://192.168.1.245:8123 doesn’t.
Can you try http://192.168.1.245:8123 once more the host?

It is also weird that from your [email protected] you cannot ping [email protected] nor [email protected] :thinking:
But that is not THE problem at the moment (might just be a simple firewall issue.
Let’s first focus on Host–>VM :wink:

45

I don’t use virtualbox so really no idea, but I noticed from your screenshot that your “Virtualbox host-only ethernet adapter” is on 192.168.56.0/24, while you are trying to communicate on 192.168.1.0/24. Is that related to your issues? Those networks won’t talk to each other unless you configure it.

46

Done, it doesn’t work

HAVM error18
HAVM error18686×828 135 KB

47

HAVM error19
HAVM error19652×558 81 KB

This is the IP of the Virtualbox network card.

Should it be changed?

PS: sorry, but due to the limitations of the forum (RIDICULOUS) I have to wait 16 hours to continue this thread.

48

Is this something you have set yourself? Like I said I do not use virtualbox, but you could try using an IP in the 192.168.1.0/24 range.

49

it doesn’t matter, you are in bridge mode.
You might even delete the host only network.

Just to explain; you can run a vm in three network modes:

  • VM only, this is an isolated network in which only the vm’s can communicate with each other (not with the host nor any device on your physical network); this network can not even be seen by the host.
  • Host only, a network where VM’s can communicate with each other and with the private network card created on the host. The VM’s can not communicate with any devices on your network.
  • Bridge mode, the physical network card of the host is shared with the VM, allowing it to communicate with all your network devices (including the internet if you have a router in your network).
1 Like
50

You run into forum limitation, because you are posting too many images. Many of those could have been copy and paste of pure texts, using this:
image

Now,

  1. go to your router, disable delete the IP assignment rule to 192.168.1.245 for the time being. Also, while you are here, also check whether you have any firewall rule to regarding port / port range on ip / ip range containing 192.168.1.245
  2. on your VirtualBox setup, remove the setup of 192.168.56.1, and use DHCP instead, ie use this Ottieni automaticamente…
    image
  3. Turn off the VM “domotica-luipez” and double check the network is (still) in bridge mode. Do not boot the VM just yet.
    3.1) Could you show us the drop down list of this Nome?
    image
    3.2) and also show us what’s under the “Avanzate”?
  4. now reboot the host metal box “domotica-lp”
  5. Do not boot any VM just yet. First run ipconfig /all and paste all the output (in text, not in image. the output could be longer than one screen)
  6. Now boot VM “domotica-luipez”, wait a few minutes so it is fully booted
  7. Let’s do a couple of things at this point:
    7.1) check the terminal output from VirtualBox, let us know any IPv4 address in the output.
    7.2) run network info from the same VM terminal window, show the output (in text)
    7.3) run ipconfig /all on your VirtualBox host, ie on domotica-lp, and let us know the full output (in text).
    7.4) from your router, find a list of connected devices in the router webui somewhere, and see whether your DHCP assigns any IPv4 address to “domotica-luipez”, or to whatever the name your VM would be.
51

@k8gg There is something else wrong; as he can open the HA observer page from the host fine:

image
image777×270 21.7 KB

So he can open http://192.168.1.245:4357 but not http://192.168.1.245:8123/
In other words, his vm network is working fine

So don’t post confusing info please

52

Ho RISOLTO impostando i seguenti IP:

PC: 192.168.1.247
VirtualMachine: 192.168.1.245
HomeAssistant: 192.168.1.244

HA si è avviato.

image
image820×713 27.9 KB

2 Likes
53

HA is the virtual machine…
and since the host and vm are bridged:
VirtualMachine: 192.168.1.245 doesn’t make sense…

But glad it works dude

Just out of curiosity, what does

ping homeassistant.local

do?