Hi

I had home assistant running in a Linux VM.

Within this VM I (probably mistakenly) assigned a static IP.

Now the VM does not receive an IP at all.

Unfortunately I cannot access the command line of the VM.

 

My theory is that the VM does not respond to the DHCP server of the Virtualisation Environment.

In my VM I have used the static IP 192.168.10.145.

but in  the network setting I see that   br0 bridge is using 172.18.0.0/16. So probably a fixed IP of 192.168.10.145 is not working anymore.

Is there a chance to change the IP range the br0 bridge is using for the VM ?

 

Quote

2024-05-27 10:24:06.911+0000: 9628: info : libvirt version: 8.7.0
2024-05-27 10:24:06.911+0000: 9628: info : hostname: Tower
2024-05-27 10:24:06.911+0000: 9628: error : qemuDomainAgentAvailable:8411 : Guest agent is not responding: QEMU guest agent is not connected
2024-06-16 07:36:00.263+0000: 9627: error : qemuAgentCheckError:988 : internal error: unable to execute QEMU agent command 'guest-shutdown': child process has terminated abnormally

 

25 minutes ago, Marty56 said:

Hi

I had home assistant running in a Linux VM.

Within this VM I (probably mistakenly) assigned a static IP.

Now the VM does not receive an IP at all.

Unfortunately I cannot access the command line of the VM.

 

My theory is that the VM does not respond to the DHCP server of the Virtualisation Environment.

In my VM I have used the static IP 192.168.10.145.

but in  the network setting I see that   br0 bridge is using 172.18.0.0/16. So probably a fixed IP of 192.168.10.145 is not working anymore.

Is there a chance to change the IP range the br0 bridge is using for the VM ?

 

 

Can you not access via the console? Post diagnostics,

 

 

I resolved the issue via CLI commands on the home assistant command line.

With these commands I could switch to DHCP instead of static IP.