Hello i installed Home Assistant docker image on a nas, then discovered there is no community store and now i try HA OS Hyper-V install.
Followed the guide, started the VM and i have no IP adress !
How do i debug this ?
On the same Hyper-V i have linux and windows VM’s, on the same Default Network,
and they both have IP adress.
I took the hyperv image from the official download link.
Best regards 
In the HA console type the fo;;owing commands:
net info (provides the interface names and you choose the one you want to assign a static IP)
in your case I noticed the interface you require is called eth0
to assign a static IP address type the following I provide example assuming 192.168.0 net:
net update --ipv4-address 192.168.0.123 --ipv4-gateway 192.168.0.1 --ipv4-nameserver 8.8.8.8
type the following to verify your settings
net info
reboot HA to make certain everything works
reboot
good luck
sorry I missed one value:
net update --ipv4-method static --ipv4-address 192.168.0.123 --ipv4-gateway 192.168.0.1 --ipv4-nameserver 8.8.8.8
apologies again the interface name was missing from my last correction; finally the correct syntax follows; please let me know if you still have problems.
net update eth0 --ipv4-method static --ipv4-address 192.168.0.123 --ipv4-gateway 192.168.0.1 --ipv4-nameserver 8.8.8.8
thank you,
no error now when i type :
net update eth0 --ipv4-method static --ipv4-address 192.168.1.90 --ipv4-gateway 192.168.1.1 --ipv4-nameserver 8.8.8.8
but after restart :
we have IP for eth0 in HA OS prompt :OK
but no IP in Hyper-V manager : NOK
no response from :
http://homeassistant.local:8123
http://localhost:8123
This is a Hyper-V issue which can be rectified, however I need a bit of time to dig this info. Generally speaking Hyper-V is the worst hypervisor when it comes to networking (nothing beats Linux or OVS bridges).
If you want search for Hypervisor bridge issues with Linux VMs.
If you want search for Hyper-V bridge issues with Linux VMs.
Thank you very much,
I will look into this, if i resolve this i will update the post.
(unfortunatly i have minimal experience with linux)
Please look into it if you have time.
I choos Hyper-V because i don’t have second PC, and the main PC is for work and gaming.
And i already use some Hyper-V vm’s so i would like not to install second hypervisor in windows.
Also backup hyperv vm is very simple.
Once i have money to buy second PC, i will try proxmox as hypervisor for homelab.
I tryed once on the main PC, achieved gpu and usb passthrugh but had blue screens in windows when installed corsair icue and logitech ghub, and had poor performance in Flight Simulator (20 fps in proxmox windows vm / 40 fps with no hyperviser).
My hardware seems not be very compatible with proxmox.
Best regards
OK one more thing messing from the command earlier is the netmask (must specify 192.168.1.90/24 to see the entire network with netmask 255.255.255.0 which is the meaning of /24):
net update eth0 --ipv4-method static --ipv4-address 192.168.1.90/24 --ipv4-gateway 192.168.1.1 --ipv4-nameserver 192.168.1.100 --ipv4-nameserver 8.8.8.8
Please let me know once you tried my last correction to the command line
For whatever is worth consider Minisforum and Beelink AMD options for mini PCs. NUCs are also stellar but cost more. For homelab go the 16 core 32G RAM and 2T SSD or better 4T, configure with ZFS and u will never look back.
Hyper-V is very good but the networking side sucks IMHO.
Unfortunatly no IP with this command in Hyper-V Manager.
Looks like there is something wrong with the official hyper-v HA OS image
Thank you for hardware advice.
Check this article to understand Hyper-V switching.
Most likely there is misconfiguration in your Hyper-V networking this is why HAOS was not able to pickup and IP address in the first place.
If you cannot get it up and running I will spend a bit of time over the weekend to assist you by installing HAOS under Hyper-V. Then I can possibly guide you with your network config if you cannot sort it by then.
I assume you are running Hyper-V in Windows 10.
I am on windows 11 pro insider beta channel, up to date.
I tryed internal / external / private / default switch, with restart HA OS : same result.
Perhaps i should exit winbdows insider program and back into normal windows to test ?
You can try normal channel Windows or you can try dual boot normal & insider.
The issue is with how Hyper-V does networking. I had this issue in the past with several Linux servers running in Hyper-V VMs. Microsoft in attempting to make things easier for people to grasp, they can actually make things worse; I am an ex-MS engineer so I know how sometimes better we stick with standards rather than try to change them in an attempt to make them easier.
ok i exit insider channel and retry
an other option i saw is linux + VFIO for windows and gaming :
Are Gaming VMs Fast? KVM/VFIO Benchmarks vs Native Install - YouTube
but i need 2 graphic cards to do it
If you are into performance computing Linux VMs can be almost as fast as bare metal. You just need good hardware to build your hypervisor on top. KVMs even system containers are super fast today assuming you have the right hardware platform.
