Selfhosted

40219 readers

1508 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Need help running homeassistantOS as a VM. VM doesnt receive ipv4 address. (discuss.tchncs.de)

submitted 1 year ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago (3 children)

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...

[–] [email protected] 1 points 1 year ago

output from "nmcli device status" command:

DEVICE TYPE STATE CONNECTION
virbr0 bridge connected virbr0

so i assume its in bridge mode?

load more comments (2 replies)