HELP MEì
I have a Bmax B3Pro minipc with Win11.
I installed Vmware 17 and installed a VM of Homeassistant following this guide:
Install Home Assistant On Windows Using VMware | Simply Smart House.
When starting the VM I get the error:
Failed to start Wait Until Kernel Time Synchronized.
How can I solve this?
I also enclose photos of the VM settings
The error indicates an issue with the internet access.
Either there is no access at all or the DNS service is failing.
Not having a promiscous driver installed in Windows can cause this among other things.
Hi, I’ve only just got into using HA and I’m not familiar with it, could you be more precise in this info of yours?
What should/can I do to solve it?
Its not a HA thing. Its a VMware/Windows thing related to the network card.
Sometimes it can be a setting on the network card other times it can be a different driver.
There might be other ways too and there might be settings in VMware too, but I have not worked much with VMware and never on Windows.
My first approach to HA was with another minipc with win10, on which I was advised to try HA in VM with Virtualbox.
I did so and everything went smoothly, in fact it is still running.
Then I bought the Bmax minipc with Win11, I did the same procedure as the first one and with Virtualbox I have error on the QEMU Agent, with Vmware I have the problem in question.
If the minipc is just used for HA and other servers, then most go with Proxmox as a hypervisor.
Because Proxmox is the OS on the bare metal, then it will have the right drivers included.
Proxmox is a new thing to learn and you might fiddle with it in the beginning, but it has a graphical user interface where most things can be done.
Yes, it had already been recommended to me, but I should also use the minipc for something else.
Like what?
I use office, web browsing, etc.
For example, I am now answering you from the minipc, without having to use another device to do it.
Well, I can’t help much with the Windows side then.
Generally I avoid the Windows Os as a platform for servers, because it is hard to manage restarts.
Windows is generally set to restart when updates have been installed and that might not always be a good time to coincide with what HA is doing.
I understand, but I only know Windows.
I was led to understand that HA was the top for home automation and above all easy for everyone, but I see that this is not really the case.
I hope there is someone else in the community who can help me.
Thanks anyway.
HA is top of the pop in home automation, but it is still not straight forward.
Your problem is most likely with the VMWare setup on Windows, which is not HA.
It might benefit you if you make a new question with the headline “Help with cobfiguring VMware Network for HA”.
This will catch the VMware peoples eye more than the current headline.
I have updated the title of this thread with your indication, so as not to duplicate it.
I hope it works.
Thanks
I succeeded.
It was all an IP problem.
After creating the VM and before starting it, on the router I set the IPs, via MAC Addresses, of both the physical networks (lan and wifi) of the minipc and the virtual one of Virtualbox.
When the VM started up, the error did not occur and HA started.
Good to hear and thanks for posting the solution.
It will help the next one stumbling over the thread. 
