Vmware Build Version
Socorro Henson
I just downloaded the iso for the 64bit version of Mint Linux. I want to run it from Windows and to do this I installed the free version of VMware player. It said it couldn't auto detect the type of operating system and is asking me to specify. I choose Linux and it gave me the sub category to choose from a whole bunch of versions such as Debian, Ubuntu, "other" and the 64 bit versions of them. Which one should I select (Mint isn't on the list)?
Speaking of requirements and compatibility, Mint should work fine with Ubuntu presets. I'm not sure about setup automation, but you can give it a try. In case of setup failing take notes on what hardware Player had assigned for the Ubuntu preset, then create new VM but this time choosing Other Linux 3.x kernel and configure identical hardware. Installation automation will be skipped for Other.
Mint is a spin-off of Ubuntu which is a spin-off of Debian.
So first preference is Ubuntu 64bit, then Debian 64bit.
As a last resort try "Other Linux" with the highest 64bit kernel available and then work you way downwards to earlier kernel presets if needed.
It depends on which Mint version you downloaded. There is an Ubuntu-based Mint, and a Debian-based Mint edition called LMDE, based on Debian-testing. So I suggest you act on the basis of this knowledge. The fact that a Mint option does not exist is indicative of the fact that the choice is not truly critical, given its popularity. I have run in the past an Arch Linux VM off the generic choice Linux Kernel 3.x 64 bits without any problem.
There certainly is a paucity of information with instructions for installing on VMware. I downloaded the XG ISO and tried to install it in VMware Player where I've played with UTM. I tried with several different choices for the underlying OS and was unsuccessful with each.
BAlfson said:There certainly is a paucity of information with instructions for installing on VMware. I downloaded the XG ISO and tried to install it in VMware Player where I've played with UTM. I tried with several different choices for the underlying OS and was unsuccessful with each.
VMWare Player runs a virtual machine. It can't create one from an ISO. You need to install the Sophos XG ISO into a full version of VMWare. Then, you can take that virtual machine and run it in VMWare Player.
I was just making sure you understood that there is also a free Home version which is a business/enterprise class version locked in a perpetual trial mode. This versions does not come in a virtual machine, but you could put it in one.
In this article, we will take a closer look at the newest release of the Software-Defined Data Center (SDDC) version 1.24 for VMware Cloud on AWS which has quite a few security and performance improvements under the hood and introduces new capabilities for the customers.
The SDDC version 1.24, released on the 14th of November 2023, comes with an updated bill of materials and features the most recent versions of vSphere including vCenter and ESXi with vSAN 8 Update 2 and NSX 4.1.2.
SDDC version 1.24 is an essential release meaning that every new SDDC deployed after general availability (GA) will use it. However, existing SDDCs must be upgraded to 1.24 to cater to all features available in the release. This happens according to VMware Cloud on AWS lifecycle management. You can explore details of the lifecycle process in this article Infrastructure Lifecycle Management Done for You with VMware Cloud on AWS.
The VMware Aria Suite is now part of VMware Cloud on AWS new subscriptions, providing even better cloud management for our customers. The following key VMware Aria enterprise products and capabilities are included:
This benefits customers who have created separate SDDC Groups per AWS region and need to connect them without disrupting existing network traffic. SDDC Group to Group connectivity is established using the existing Transit Connect per region. Interconnected SDDC Groups can leverage their existing external connections to Direct Connect Gateway and/or AWS VPC and Transit Gateways.
This feature is available for all customers on supported AWS versions (starting from 1.18) for both new and existing Transit Connect deployments. Customers can configure the feature from VMware Cloud Console in SDDC Group UI by selecting desired SDDC Groups to connect.
IPv6 protocol support has been introduced in VMware Cloud on AWS v1.22 and has been extended in the new 1.24 release. Previously VMware Cloud on AWS announced support for IPv6 communication over Direct Connect and VMware Transit Connect which allows to use of IPv6 workloads inside SDDC and workloads communication with on-premises datacenters. Customers have to enable IPv6 individually on each SDDC from the Actions menu at the SDDC Summary tab.
With the 1.24 release IPv6 enabled VMs can now communicate with SDDC Management components such as vCenter (which is using IPv4) using NAT64 rules. If you require IPv6 workloads to communicate with SDDC Management components, work with your VMware representatives. You can learn more about IPv6 support on VMware Cloud on AWS by reading the following blog Introducing IPv6 Networking in VMware Cloud on AWS.
The most recent blog post vSAN ESA now available in VMware Cloud on AWS announces a new chapter in the evolution of VMware Cloud on AWS storage foundation and we will reveal some exciting details about it below.
VMware Cloud on AWS release 1.24 introduces vSAN Express Storage Architecture (ESA) which is supported on i4i.metal host type for new SDDCs. To enable vSAN ESA feature customers currently require assistance from the VMware team. To learn more about vSAN ESA architecture, please refer to vSAN ESA Frequently Asked Questions.
vSAN ESA is available for greenfield SDDC as primary and secondary clusters. Enabling vSAN ESA is a one-click selection during a new SDCC or cluster deployment. You can read more in the following article: vSAN ESA with VMware Cloud on AWS: Technical Deep Dive
This feature enables customers to establish a direct network link between their VMware Cloud on AWS SDDC and an Amazon VPC hosting Amazon FSx for NetApp ONTAP. This presents customers with a compelling network architecture, offering both simplicity and cost savings for external NFS storage. With the introduction of VPC Peering, customers can fully leverage the capabilities of Amazon FSx for NetApp ONTAP without incurring additional expenses associated with AWS Transit Gateway data processing fees.
Using external NFS Datastores (VMware Cloud Flex Storage or Amazon FSx for NetApp ONTAP) introduces additional traffic flowing through the host network adapter. Using jumbo frames NFS storage traffic throughput can be significantly increased by reducing the overhead associated with transmitting NFS requests and responses. This can improve NFS performance, but all network devices in the path must support jumbo frames for it to be effective. SDDC version 1.24 for VMware Cloud on AWS supports increased MTU and would provide better performance for customers with External Storage.
Together with simplified profile settings, UI enhancements and Quick Sizer which now also supports external storage VMware Cloud Sizer becomes an even more handy tool making it essential for capacity planning.
Adding NSX Security Admin role to NSX adds granularity and enables separation of Security Admin and Network Admin roles for different teams of users. Granular role-based access control (RBAC) allows customers to assign limited access to Network-only or Security-only configuration on VMware Cloud on AWS, instead of providing full administration controls to the users.
Lifecycle management in the new version of VMware Cloud SDDC got several enhancements such as non-disruptive vCenter certificate replacement and upgrade improvements making day 2 operations faster, more reliable and even less intrusive for the end users.
VMware by Broadcom is excited to present the Beta release of the new edition of the VMware Host Client. All customers registered with the vSphere Beta program can access and download the new GUI for ESXi management. You can register to the vSphere Beta program from the dedicated form.
As we have previously announced to the customer community, the legacy VMware Host Client is facing issues from technological and usability perspective and has been put in maintenance mode. For the legacy Client, we are only addressing critical issues related to the security or availability of the GUI. We are fulfilling our promise to deliver a new edition of the Host Client and we are inviting you to download and test the new bits and share your feedback with us.
As this is the first version of the new UI for ESXi mgmt., it is covering the basic flows for host and VM management and operations. We will gradually enhance the functionality with the most important workflows to provide vSphere users with a compelling tool for host mgmt. covering the critical provisioning and troubleshooting use-cases at the ESXi level.
The new Host Client Beta is a web desktop application which can be installed on Mac OS, Windows or Linux. It is not associated to a specific ESXi version and thus can connect to the most recent versions of the hypervisor as well as older ones. While connecting to an ESXi, connection details can be saved to allow seamless switching between the servers.
For the Beta we also provide the capability for the user to enlist in the Customer Experience Improvement Program allowing the team to collect telemetry from the usage of the interface. You can also share feedback using a dedicated form available from the graphical interface.
Please be aware that the legacy Host Client is entering deprecation state. It will still be available and supported in the generally available version of the next major release of vSphere and will coexist with the new ESXi UI. However, over the course of the updates of the said major release, the support for the legacy Host Client will be terminated and it will not be available for the subsequent major release. We will provide regular updates on this topic.
c80f0f1006