kvm autostart doesnt work

    • Neu
    • Offizieller Beitrag

    It is working on my systems. What is the output of:


    sudo ls -al /etc/libvirt/qemu/autostart/

    sudo virsh list --autostart


    And did you look at the logs for the VMs in /var/log/libvirt/qemu/? Are you using usb storage?

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • this is what mine shows


    Code
    sudo ls -al /etc/libvirt/qemu/autostart/
    total 8
    drwxr-xr-x 2 root root 4096 May  9 15:48 .
    drwxr-xr-x 4 root root 4096 May  7 20:21 ..
    lrwxrwxrwx 1 root root   27 May  9 15:48 Win10.xml -> /etc/libvirt/qemu/Win10.xml
    
    sudo virsh list --autostart
     Id   Name    State
    -----------------------
     2    Win10   running
  • sudo ls -al /etc/libvirt/qemu/autostart/

    Code
    total 8
    drwxr-xr-x 2 root root 4096 May  7 14:54 .
    drwxr-xr-x 4 root root 4096 May  9 20:33 ..
    lrwxrwxrwx 1 root root   31 May  7 14:54 1c-server.xml -> /etc/libvirt/qemu/1c-server.xml
    lrwxrwxrwx 1 root root   29 May  7 14:54 mikopbx.xml -> /etc/libvirt/qemu/mikopbx.xml


    sudo virsh list --autostart

    Code
     Id   Name        State
    ---------------------------
     3    1c-server   running
     4    mikopbx     running


    And did you look at the logs for the VMs in /var/log/libvirt/qemu/? Are you using usb storage?

    Code
    2024-05-09T17:31:30.327091Z qemu-system-x86_64: warning: Spice: ../server/reds.cpp:2551:reds_init_socket: getaddrinfo(0.0.0.0,5901): Address family for hostname not supported
    2024-05-09T17:31:30.327109Z qemu-system-x86_64: warning: Spice: ../server/reds.cpp:3442:do_spice_init: Failed to open SPICE sockets
    2024-05-09T17:31:30.327115Z qemu-system-x86_64: failed to initialize spice server
    2024-05-09 17:31:30.401+0000: shutting down, reason=failed

    here's the problem, how can i solve this?

    • Neu
    • Offizieller Beitrag

    here's the problem, how can i solve this?

    The plugin has a menu that lets you remove spice and then you could re-add it.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Find solution by disabling (disgusting) ipv6

    in /etc/sysctl.conf add the following lines at end


    Code
    # Turn off IPv6
    net.ipv6.conf.all.disable_ipv6 = 1

    then

    Code
    sysctl -p

    and reboot for success

  • mcking230

    Hat das Label gelöst hinzugefügt.
  • mcking230

    Hat das Label OMV 7.x hinzugefügt.
    • Neu
    • Offizieller Beitrag

    Find solution by disabling (disgusting) ipv6

    in /etc/sysctl.conf add the following lines at end

    I don't know why that works but I do not have ipv6 disabled on my systems.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!