VMware Workstation Shifting From Proprietary Code To Using Upstream KVM

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • slalomsk8er
    replied
    Originally posted by Quackdoc View Post
    also what is VMM in this case?
    https://virt-manager.org/ is my guess

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by JPFSanders View Post

    Exactly. People who are clueless about KVM, libvirt, virsh, VMM don't understand how versatile and powerful the VM infrastructure on Linux are. At a personal level and in non-complex environments (complex = large virtualisation cluster) there is no need whatsoever to use any proprietary tool to set-up and manage virtual machines.

    VMM > Virtualbox, never used vmware workstation, when I need to move a machine from KVM to vmware or vice-versa a couple of commands do the conversion job just fine.
    libvirt is dumb though for instance qemu has a lot of flexibility that libirt strips away, for instance in qemu gl can be on, off, es. libvirt can only handle that as a boolean. also what is VMM in this case? vmm typically means virtual machine monitor or virtual machine manager, it's a generic term. and even for more "enterprise" like stuff, outside of cloud hypervisor, pretty much everyone else major has died off haven't they? Maybe ovirt is still kicking around.

    Leave a comment:


  • JPFSanders
    replied
    Originally posted by slalomsk8er View Post

    Enterprise user here and I did use the CLI for managing my VMs while I was the admin of the KVM hypervisor hosts.
    I vastly prefer to copy and paste the CLI command from the company wiki then to go over screenshots and follow the click trail. CLI also makes automation a lot easier.
    Exactly. People who are clueless about KVM, libvirt, virsh, VMM don't understand how versatile and powerful the VM infrastructure on Linux are. At a personal level and in non-complex environments (complex = large virtualisation cluster) there is no need whatsoever to use any proprietary tool to set-up and manage virtual machines.

    VMM > Virtualbox, never used vmware workstation, when I need to move a machine from KVM to vmware or vice-versa a couple of commands do the conversion job just fine.

    Leave a comment:


  • nanonyme
    replied
    Originally posted by OneTimeShot View Post
    "VMWare backdoor".... I thought the Kernel didn't allow APIs that didn't have an OpenSource implementation.

    Seems like these days the kernel is just a pipe between a closed-source firmware blob and a closed-source userspace blob.
    The very word backdoor should make a maintainer go on defense. Can this be used to create rootkits assuming local access to machine?

    Leave a comment:


  • JPFSanders
    replied
    Originally posted by Sonadow View Post

    More mindless "bloated" garbage.

    Enterprise users have no fucking time to toy with the command line just to spin up, modify or manage a VM. If every damn option and the kitchen sink is not included in the graphical manager interface, it's useless garbage. End of story.
    You haven't worked on an Enterprise environment. When things go south (which they do from time to time) where do you think the troubleshooting/fix is done?

    Leave a comment:


  • richardm317
    replied
    This is kind of a big deal for me. I've been circulating amongst hypervisors and OSs trying to find the best overall combination for my mixed homelab workload for both the backend server and on my desktop. The server is currently ESXi and I've no plans to change that. On my desktop this could be what finally allows me to ditch Windows for good.

    Libvirt, virt-manager, and QEMU are annoying but OK. The jank lies inside the Windows VMs with flaky virtio components and even flakier Spice components. If this new KVM overlord for VMware Workstation permits the use of VMware Tools including vmxnet3, vmmouse, vmmemctl, pvscsi, et al and the host integration features -- drive sharing, clipboard, desktop resolution re-sizing on-the-fly -- are stable and reliable then I, for one, welcome it.

    As it stands today there's just too much screwing around required to obtain a solid desktop virtualization experience on Linux.

    That said, I wasn't aware of the Cyberus vbox fork and I plan to look into this ASAP.

    Leave a comment:


  • slalomsk8er
    replied
    Originally posted by Sonadow View Post

    More mindless "bloated" garbage.

    Enterprise users have no fucking time to toy with the command line just to spin up, modify or manage a VM. If every damn option and the kitchen sink is not included in the graphical manager interface, it's useless garbage. End of story.
    Enterprise user here and I did use the CLI for managing my VMs while I was the admin of the KVM hypervisor hosts.
    I vastly prefer to copy and paste the CLI command from the company wiki then to go over screenshots and follow the click trail. CLI also makes automation a lot easier.

    Leave a comment:


  • NM64
    replied
    Originally posted by ssokolow View Post
    Ever since GNOME-isms started to leak into non-GNOME apps, I've been working to purge all GTK use from my desktop and I've almost succeeded.
    I'm by far no Linux guru, but while I don't tend to mind the aesthetic of GTK3 applications (though GTK4 is a bit much...), I do find it maddening that they don't obey Fitts' Law (and, of course, neither does GTK4 - my personal pet theory is that the GTK devs don't see the problem because GNOME defaults to having the panel at the top).

    I don't know about your distro, but simply installing the gtk3-nocsd package seemed to make all GTK3 apps actually obey Fitts' Law (with the exception that Firefox and LibreWolf are no longer able to have tabs up against the top of their maximized window to take advantage of Fitts' Law for tab-switching, but my primary albeit rather small-time web browser is offered in a GTK2 flavor anyway)

    From the official github page:
    Originally posted by https://github.com/PCMan/gtk3-nocsd
    gtk3-nocsd is a small module used to disable the client side decoration of Gtk+ 3.

    Since Gtk+ 3.10, its developers added a so-called header bar or custom title bar. With this and the client-side decoration, the original title bar and window border provided by the window manager are disabled by Gtk+. This makes all Gtk+ 3 programs look alike. Even worse, this may break some window manager or compositors.

    Unfortunately, the Gtk+ developers decided to be against the existing standards and provide "no option" to turn it off.

    Luckily, with gtk3-nocsd, we still have a way to (partially) turn it off. Window manager (title bar and window border) can be re-enabled.​
    Last edited by NM64; 01 November 2024, 04:01 AM.

    Leave a comment:


  • OneTimeShot
    replied
    "VMWare backdoor".... I thought the Kernel didn't allow APIs that didn't have an OpenSource implementation.

    Seems like these days the kernel is just a pipe between a closed-source firmware blob and a closed-source userspace blob.

    Leave a comment:


  • eszlari
    replied
    Originally posted by ssokolow View Post
    (need to upgrade KDE from 5 to 6 for flatpak-kcm)
    flatpak-kcm is part of Plasma since 5.27.

    At least they properly respect my CSD vs. SSD preferences.
    virt-manager respects SSD.

    Leave a comment:

Working...
X