There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

Need help running homeassistantOS as a VM. VM doesnt receive ipv4 address.

I have a local network where all the devices receive their ip from the router. IP range is 192.168.0.XXX.

On one of those machines i want to run “home assistant operating system” inside a VM using libvirt(using cockpit webgui).

I was able to install the VM, but when I run it, it never receives a IP address. Setting one manual works, but then the VM doesn’t show up in my local network.

On the host machine I created a bridge (virbr0) and I made the nic(enp8s0) from the host member. I also made VM member of virbr0

Any ideas what i’m doing wrong?

Note that the VM also needs to become member of the local network (ip range 192.168.0.XXX) and needs to see all other members of the local network.

jmd_akbar ,

Could it be that you need to run the VM network in NAT mode, instead of a “Bridge” mode?

Please note, I have little experience in troubleshooting these, I’m just spitballing ideas here…

stown ,
@stown@lemmy.world avatar

No, then the VMs would get their own subnet. You want the NIC bridged so that the router actually sees the VMs.

jmd_akbar ,

Gotcha. I learned something new. Thanks :)

toams OP ,

output from “nmcli device status” command:

DEVICE TYPE STATE CONNECTION
virbr0 bridge connected virbr0

so i assume its in bridge mode?

SeeJayEmm ,
@SeeJayEmm@lemmy.procrastinati.org avatar

When I ran all my vms in kvm I used macvtap for the nic type.

stown ,
@stown@lemmy.world avatar

OP, are all of the working-as-expected VMs also members of the virbr0 network?

I’m thinking that this is a firewall issue on your VM host. If you DO NOT have any other working VMs then could you try disabling the firewall on the VM host and see if the VM can receive DHCP traffic.

toams OP ,

I currently have no other VM’s running. I’ll see if disabling the firewall helps.

stown ,
@stown@lemmy.world avatar

Did you ever figure out what was causing your issues?

toams OP ,

No sadly I didn’t. I got it working a few times after reconfiguring everything but it never survived a reboot.

NeoNachtwaechter ,

Forget HA (for a while) and focus on the IP address problem. Start from scratch with a new VM, and/or inspect one of your VM’s where the networking works. Find the difference.

Decronym Bot , (edited )

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
HA Home Assistant automation software
~ High Availability
IP Internet Protocol
NAT Network Address Translation

3 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.

[Thread for this sub, first seen 3rd Nov 2023, 12:30] [FAQ] [Full list] [Contact] [Source code]

OminousOrange ,
@OminousOrange@lemmy.ca avatar

Not an expert, just something I did and learned from; does the hardware you’re running on have more than one ethernet port (enp#…)? Is it possible you’ve selected the wrong one?

Also I notice my VMs in proxmox have the bridge nomenclature of vmbr0 (not virb0). Perhaps something there?

Just throwing ideas out there, I’m pretty new at this.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •