4 comments

  • tlamponi6 minutes ago
    FWWI, we did evaluate and benchmark microVMs back in 2020. Back then it was not really seen worth it the maintenance cost compared to what it brought to the table, but it makes sense to re-evaluate that again soonish; with native dynamic load balancing and affinity rules (and further orchestration improvements being lined up) they might be better leveraged today.<p>Oh, and mailing lists are a bliss to use compared to (barely loading) forges, at least to me and especially with public inbox and tools like b4 and lei for patch review, management and applying. For the sending side it&#x27;s basically a git send-email command to pve-devel@list.proxmox.com, see <a href="https:&#x2F;&#x2F;git-send-email.io" rel="nofollow">https:&#x2F;&#x2F;git-send-email.io</a> for a simple tutorial.
  • mkesper17 minutes ago
    Tangentially, in theory, k3s + kubevirt + microvms sounds like the optimal combination for lightweight but isolated deployment. Does anyone have experience with that?
    • alde2 minutes ago
      KubeVirt only supports full QEMU. They have a long open issue about QEMU MicroVM support.
  • cedws7 hours ago
    I see Proxmox blog post I upvote.<p>I’ve also been wanting a setup like this but don’t have to courage to use pve-microvm. First class microVM support would be very nice.
  • impara42 minutes ago
    [flagged]