• TCB13@lemmy.worldEnglish
    19·
    2 months ago

    I’ve questions about this.

    People are talking about it like it is the greatest thing ever, however, isn’t this yet another result of the Broadcom acquisition? After firing a bunch of people , now this. Maybe they just don’t want to maintain the “existing proprietary virtualization code” so they’re moving to KVM. Less costs, less people.

    • moonpiedumplings@programming.dev
      10·
      2 months ago

      I honestly don’t know how this could turn out.

      It could be an amazing change that results in much more progress for hardware acceleration on guests of various types (since that is what vmware is good at) in kvm…

      Or it could mean that they are dropping that feature from vmware altogether.

      Regardless, I like this change because it means I would be able to run vmware machines and libvirt kvm machines at the same time, at least when I am forced to use vmware workstation.

      I also dislike proprietary software in general, so I think less proprietary software and more FOSS is a good thing.

      • TCB13@lemmy.worldEnglish
        7·
        2 months ago

        It could be an amazing change that results in much more progress for hardware acceleration on guests of various types (since that is what vmware is good at) in kvm…

        Yeah but VMware was good. And I’m not seeing Broadcom investing into porting the “proprietary goodness” of VMware into KVM. I just see then looking at KVM and saying “that’s good enough” and seeing it a cost reduction measure.

  • Atemu@lemmy.mlOP
    14·
    2 months ago

    Hell seems to be freezing over at an alarming rate these days; climate change is getting pretty extreme down there too huh?

  • Avid Amoeba
    8·
    2 months ago

    If we get VirtIO 3D acceleration in Windows guests from this, I’d be really happy.

  • wazoox@jlai.lu
    2·
    2 months ago

    That means migrating away from VMWare, which is a must for many nowadays, will be even easier. Good news!