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.

  • NeoNachtwaechter@lemmy.worldEnglish
    3·
    1 year ago

    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.

  • jmd_akbar@aussie.zoneEnglish
    52·
    1 year ago

    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@lemmy.worldEnglish
      5·
      1 year ago

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

    • toams@discuss.tchncs.deOPEnglish
      1·
      1 year ago

      output from “nmcli device status” command:

      DEVICE TYPE STATE CONNECTION
      virbr0 bridge connected virbr0

      so i assume its in bridge mode?

  • Decronym@lemmy.decronym.xyzBEnglish
    2·
    1 year ago

    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 #261 for this sub, first seen 3rd Nov 2023, 12:30] [FAQ] [Full list] [Contact] [Source code]

  • stown@lemmy.worldEnglish
    1·
    1 year ago

    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.