Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Deprecation of SPICE was news to me. Issue thread on the removal:

    https://bugzilla.redhat.com/show_bug.cgi?id=2030592

  • Why the pony with the hat if they do not sponsor it.
  • The major challenge is not keep it building and compatible. The major challenge is to keep up with security issues.

    I wish op all the best, it's a tough journey

  • I guess I hadn't been paying attention. Is this just the Windows SPICE client that Red Hat has abandoned, or are they moving toward dropping SPICE altogether? Does Red Hat no longer have a VDI product? (I'm sure they did at one point.)

    Regardless, thanks for picking this up, OP.

  • I used to use x2goserver which was and still is awesome.

    These days I prefer docker-based KASM Workspaces, or if you just want a nice GUI over your "bare-metal" VM or server then KasmVNC is great and easy to setup (not that KASM Workspaces is hard to setup)

    https://hub.docker.com/r/linuxserver/kasm https://github.com/kasmtech/KasmVNC

  • I really don't get why redhat decided to kill SPICE. It was the only thing that got using a VM on open source virtualization (e.g. proxmox) close to the experience of using one on vmware.

    VNC is truly the worst remote desktop protocol you can have. Bad latency, bad quality, bad integration.

  • As an irregular user of spice (via Proxmox PVE), I wish the stars would align for QEMU to gain support for sunlight/moonlight streaming directly in the hypervisor. That'd be a killer app for VDI-style infrastructure, now that accelerated guest graphics via Venus, VirtIO GPU, and Intel's support for SR-IOV is finally coming together.
    by c0l0
  • Major confusion for me, as SPICE is well known circuit simulator: https://en.wikipedia.org/wiki/SPICE

    Using it often. Mostly via ngspice nowadays: https://en.wikipedia.org/wiki/Ngspice

Explore Birbla archives