• AutoTL;DR@lemmings.worldBEnglish
    222·
    11 months ago

    This is the best summary I could come up with:

    • QEMU 8.2 adds a new “virtio-sound” device that implements capture and playback from inside a guest using the configured audio backend of the host machine.

    • A new VirtIO-GPU “Rutabaga” device that allows various abstractions of GPU and display virtualization.

    This VirtIO-GPU Rutabaga comes from the Android/CrosVM graphics stack and is intended for use with the Android Emulator on QEMU.

    QEMU documentation describes this as “virtio-balloon on steroids for Windows guests.”

    • QEMU’s 68k Macintosh Quadra 800 emulation can now boot MacOS 7.1, A/UX 3.0.1, Linux, and NetBSD 9.3.

    Plus support for 4K page sizes and other ongoing LoongArch enablement work.

    The original article contains 305 words, the summary contains 102 words. Saved 67%. I’m a bot and I’m open source!

  • Flaky@iusearchlinux.fyiEnglish
    13·
    11 months ago

    Hopefully some of this comes to Windows guests. One of the major issues right now is that Windows virtualisation isn’t great. VirtualBox has GPU problems, VMware requires a lot of messing about with kernel modules if you don’t use Ubuntu, if KVM/QEMU is able to make a smooth environment for Windows guests that’d help bring people in who still need Windows for the odd bit of software or two.

    I remember there was a GPU driver for Windows but that seems to have stalled?

    Edit: Cleared up why I think VMware is a bit of a mess.

    • drwankingstein@lemmy.dbzer0.comEnglish
      5·
      11 months ago

      virtio-sound likely will eventually and ufs probably will too. the gpu driver is being worked on by a third party, but it’s still using virgl so I doubt it will be very preformant

    • netburnr@lemmy.worldEnglish
      31·
      11 months ago

      Vmware requires a lot of messing around.

      What are you going on about? VMware and Windows work just fine if you install vmware tools.

      • Flaky@iusearchlinux.fyiEnglish
        6·
        11 months ago

        I’m talking about the installation process for VMware itself.

        I had to help someone non-techy install VMware on Pop!_OS (the OS preinstalled by System76 on their hardware), and it required messing with the kernel modules which fails on Pop!_OS. It seems like VMware builds for a very specific version of Ubuntu which of course, means the kernel module building process fails when you use a kernel version that’s different to what Ubuntu has (which Pop!_OS does and maybe some other Ubuntu-based distros). Thankfully someone on GitHub maintains up-to-date patches for the VMware modules so I was able to guide him through there but this isn’t something someone new to Linux would want to do.

        It’s not like simply installing it from a package manager, well unless you use Arch but I’m not putting this person who’s new to Linux on Arch when he just started using CLI.