kvm autostart doesnt work

FatherRandom · May 31st 2024

Code

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
    link/ether a8:a1:59:0c:d3:9b brd ff:ff:ff:ff:ff:ff
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 12:e3:60:49:a9:d6 brd ff:ff:ff:ff:ff:ff
    inet 192.168.188.32/24 metric 100 brd 192.168.188.255 scope global dynamic br0
       valid_lft 855497sec preferred_lft 855497sec
4: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:eb:f5:95 brd ff:ff:ff:ff:ff:ff
5: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0
       valid_lft forever preferred_lft forever

Display More

ryecoaaron · May 31st 2024

I can't explain it. It seemed like systems with ipv6 forwarding enabled when the network stack had ipv6 disabled caused the problem but you don't have ipv6 forwarding enabled. Since I can't reproduce this on any of my systems, all I can suggest is to look for some kind of error in the logs - /var/log/libvirt/libvirtd.log is where I would start first. I don't know what kind of errors to look for though.

FatherRandom · May 31st 2024

Thank you very much for your help, ryecoaaron! For now the setups works for me and I have no issue with the missing IPv6. I will look into it later once I've sorted out my backup ideas for my dms inside the VM.

bavism · Jul 8th 2024

I have the same problem as FatherRandom. Not sure if this is relevant or a coincidence, but I also have my ethernet and VMs bridged like the poster here. Checking the entire boot logs, it appears all interfaces on br0 are disabled when libvirtd attempts to startup my VM. Could that be responsible for the failure of getaddrinfo? (I would still expect loopback to have an address there). ryecoaaron

ryecoaaron · Jul 8th 2024

Quote from bavism

Could that be responsible for the failure of getaddrinfo? (I would still expect loopback to have an address there)

I use a bridge on my systems as well and don't have this problem. I haven't been able to reproduce either. So, not sure what failure you are seeing for getaddrinfo. All I can suggest is adding a delay to the libvirtd service by adding a systemd override.

No need to tag me. I get notified of posts I have contributed to and others on the forum can help too.

bavism · Jul 11th 2024

Sorry, I don't have the logs in front of me at the moment, but it was basically getaddrinfo("0.0.0.0") Address family for hostname not supported when trying to connect to spice during the autostart. (same error as 4th post in this thread)

ryecoaaron · Jul 11th 2024

What version of OMV?

bavism · Jul 11th 2024

7.0-32 (Sandworm)

ryecoaaron · Jul 12th 2024

Are you using ipv6?

bavism · Jul 12th 2024

We don't "use" it, but it's not disabled systemwide. Everything has autoconfiged link local ipv6 addresses only.

ryecoaaron · Jul 12th 2024

Have you or can you try disabling ipv6 to see if it fixes the issue?

space_ranger · Oct 22nd 2024

I'm not sure if this is an issue with multiple causes but I have located why my VM seems to fail to start which may be related to the issues others have had.

Spice fails to start and then the VM exits. When i start the VM manually it runs fine but requires me to manually start spice if i want to get to the console which does work.

I think the issue is this one https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1492621

This it the forum post i found about it https://forums.debian.net/viewtopic.php?t=155857

I tried the workaround but it does not work for me. It would be nice to have some way to delay startup until the adapter is up. I have yet to figure out a reliable way to do that, open to suggestions?

That may be why the disabling ipv6 works for some if its making the ip4 come up faster?

space_ranger · Oct 24th 2024

Just an update with a solution I found for anyone suffering with this problem. You can add a delay to the startup by creating a systemd override.

Code

sudo systemctl edit libvirtd

Then add the following lines to delay for 30 seconds. That works for my setup but the time can be altered to whatever works for the sytem.

Code

[Service]
ExecStartPre=/bin/sleep 30

The autostart function is now working fine for me.

kvm autostart doesnt work

Participate now!

Tags