VMware Workstation Pro 26H1 is now live!

The virtualization program, VMware Workstation Pro, has been updated with a brand new version, 26H1, which was released yesterday. This version of VMware Workstation brings several feature additions, as well as general improvements and bug fixes to improve your virtualization experience and to make this program more secure.

VMware Workstation Pro used to be a 32-bit application that provided compatibility for systems that are still using 32-bit hosts, especially on Windows. Now, with the release of 26H1, it has migrated to a 64-bit only application, which presents you with optimized binaries and components for 64-bit.

VMware Workstation now supports the following systems (guest and host):

Additionally, the following changes have been made:

• You can now easily take a look at both the creation date and the last power on date, which will make it easier for you to identify when the virtual machine was first created and when it was powered on.
• VMware Workstation Pro now supports remote connection to ARM-based ESX hosts, which enables basic virtual machine operations on those hosts.
• On folder tabs, you can now easily take a look at notes for each virtual machine.
• The saved credential format has been updated so that you can easily identify encrypted virtual machines and remote servers in the host’s credentials manager.

You can learn more about the new release of VMware Workstation here.

Hack w/ Me Ep. 3 is LIVE!

Join me as I chat about Linux basics, VMs, and scripting 🤘🏾

https://open.substack.com/pub/digitaldopaminellc/p/hack-w-me-episode-3-linux-basics?r=6fp208&utm_medium=ios

#HackWithMe #Linux #VirtualMachines #DigitalDopamine #Podcast #fyp #discover #cybersecurity

Upgraded to "Not Working".

This laptop is actually a nest of virtual machines. The host does very little beyond running libvirt and its associates.

All user data is on a separate drive that is provided to the VMs via NFS from a server VM. I have multiple users defined that I use for different purposes, testing, development, and general stuff. Each of these users can log into any of the VMs (except for one or two special ones) and see all of their data.

The gotcha with this configuration is the user's directories where programs save configuration data. There is no guarantee that the VMs will have the same version of the programs installed, so data in .local and .config could become confused, or worse.

My solution (from 2020) was to give each user a directory with subdirectories for each VM. A pair of soft-links would then map .local to the VM specific version, via a link in /var/run/$USER/. This link was set up by a script run from /etc/profile when the user logs in.

This worked fine until recently. There is now several things that try to access .local before /etc/profile is called. They tend to not work very well. Some quietly fail with just a bit of inconvenience. Fedora 42 fails completely, as I found out with a recent upgrade.

Each VM is created with a conventional admin user, so I can easily apply a correction. It appears I will need to put the machine soft link in /etc so that it is always there. Some scripting in my future...

#Linux #virtualmachines

Apple Silicon and Virtual Machines: Beating the 2 VM Limit

https://khronokernel.com/macos/2023/08/08/AS-VM.html

#HackerNews #AppleSilicon #VirtualMachines #VMlimit #TechNews #MacOS #Innovation

New post: Installing Mavericks on my Apple Silicon in a UTM VM

https://adam.kostarelas.com/blog/mavericks-in-utm-on-silicon/ #marchintosh #UTM #virtualmachines #macos