• Leaflet@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 days ago

    The virt-manager flatpak doesn’t work out of the box, you need to do some setup on the host. At that point you may as well use the deb of virt-manager.

  • user_naa@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 days ago

    If you install virt-manager on Debian via apt it will have full system acres and also automatically install and configure libvirt, so this method is preferred.

  • liliumstar@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 days ago

    I would use the native version. For something like this, it makes sense that it should have less restricted/sandboxed access to the underlying system.

    • hellostick@lemm.eeOP
      link
      fedilink
      arrow-up
      2
      ·
      21 hours ago

      i am not sure which one is the native version… you mean the version packaged by the distro (deb) or the developer (flatpak)?

    • deadcade@lemmy.deadca.de
      link
      fedilink
      arrow-up
      0
      ·
      2 days ago

      virt-manager only requires access to the libvirtd socket, as long as the flatpak.has that as default configuration (which I imagine would be the case), there’s zero difference beteween flatpak and native.

      • deafboy@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        18 hours ago

        In my experience, this is not the case. It just says it can’t connect. Doesn’t specify how or where to.

      • hellostick@lemm.eeOP
        link
        fedilink
        arrow-up
        1
        ·
        21 hours ago

        actually there is difference in version between the two. deb by my distro is in 4.0.0 (mar, 2022) while flatpak is 5.0.0 (nov, 2024)