Hello, VMware has posted a "security fixes only" update to the VMware Tools for MacOS - https://customerconnect.vmware.com/en/downloads/details?downloadGroup=VMTOOLS1235&productId=1259&rPId=112353
I use APFS with Apple RAID. I have a pair of Envoy Pro EX drives in an Apple RAID 0 with APFS and it performs around 1800 MB/s in benchmarks. I also did a pair of 8TB WD disks this way and it has w...
See more...
I use APFS with Apple RAID. I have a pair of Envoy Pro EX drives in an Apple RAID 0 with APFS and it performs around 1800 MB/s in benchmarks. I also did a pair of 8TB WD disks this way and it has worked well for me for the last 3 years. I recall looking at SoftRAID. It did not work with whatever MacOS was new at that time, and it looked like it was going to be nothing but trouble over the years.
Maybe...but I am only doing this 2-3 times a year so it is not high on my list for SSD wear. I looked today for the first time and after 3.5 years my VM SSDs are at 99% so I think its OK.
I am still using these instructions I got from an older message in this forum I think: From inside the VM using a terminal session I issue the following command cat /dev/zero > wipefile; rm wipefi...
See more...
I am still using these instructions I got from an older message in this forum I think: From inside the VM using a terminal session I issue the following command cat /dev/zero > wipefile; rm wipefile Shutdown the VM and exit VMware Fusion Execute the following command to defragment the disk (substitute VM name/Disk Name) /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -d macOS\ 10.15\ 64-bit.vmwarevm/Virtual\ Disk.vmdk Execute the following command to shrink the disk (substitute VM name/Disk Name) /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -k macOS\ 10.15\ 64-bit.vmwarevm/Virtual\ Disk.vmdk You would need to substitute your VM folder's names in there. I usually navigate to the VM folder so I do not have to type all that out to run the commands. I have had some problems with Big Sur VMs but everything else shrinks.
I had recently figured out that Fusion was still loading 12.1.0 for Mac after the 12.1.5 update, and the KB confirms the behavior. I think the Fusion team is well aware of what is going on.
This was a detail I missed in 12.0 and 12.1.5 but finally figured it out from the 12.2.0 release notes - https://kb.vmware.com/s/article/88698 12.1.0 was the last VMtools for MacOS. More to be unha...
See more...
This was a detail I missed in 12.0 and 12.1.5 but finally figured it out from the 12.2.0 release notes - https://kb.vmware.com/s/article/88698 12.1.0 was the last VMtools for MacOS. More to be unhappy about.
I will observe on the drive interface that VMware made a big deal about NVMe for performance, and this fellow's tests seem to bear that out - https://www.thomas-krenn.com/en/wiki/VMware_Performance_C...
See more...
I will observe on the drive interface that VMware made a big deal about NVMe for performance, and this fellow's tests seem to bear that out - https://www.thomas-krenn.com/en/wiki/VMware_Performance_Comparison_SCSI_Controller_and_NVMe_Controller In practice I have switched to NVMe for the newer operating systems but I have not been empirical about checking my performance gains. In vSphere ESXi you lose the ability to hot add disk space with NVMe that you have with SCSI, but usually if you can hot add to a VM then you are giving up some amount of performance for the benefit.
I am realizing that this is probably what Parallels was doing last fall too, I was just not digging deep enough to see they were downloading an ESD and not an ISO. As a MPSA holder I have been able ...
See more...
I am realizing that this is probably what Parallels was doing last fall too, I was just not digging deep enough to see they were downloading an ESD and not an ISO. As a MPSA holder I have been able to get the regularly updated (21H2 and 22H2) Windows 10 and 11 ARM ISOs most recently updated last week for Feb 2023. No idea where a consumer user would get something like that though?
OK so Parallels is still building the ISO on your Mac. Wonder what would have changed to make it bootable in Fusion though? I would expect Parallels to insert a boot loader for their virtual hardwa...
See more...
OK so Parallels is still building the ISO on your Mac. Wonder what would have changed to make it bootable in Fusion though? I would expect Parallels to insert a boot loader for their virtual hardware and thus was not surprised when the ISO did not boot elsewhere.
When I tried Parallels last year they downloaded a non-bootable ISO and then inserted a WIM boot loader - that did not work with Fusion. This implies that Microsoft has perhaps made a VM bootable IS...
See more...
When I tried Parallels last year they downloaded a non-bootable ISO and then inserted a WIM boot loader - that did not work with Fusion. This implies that Microsoft has perhaps made a VM bootable ISO now?
Well...this removes my concern around using the Parallels solution. No longer so risky in the long term. Agreed that Fusion 13.5 better show up soon too
10G is not so rare in Macs. The iMac Pro shipped with 10G and it was a build to order option on 2018 MacMinis and 2020 27" iMacs. 2x10G standard on the 2019 Mac Pro. 1x10G standard on the 2022 Mac...
See more...
10G is not so rare in Macs. The iMac Pro shipped with 10G and it was a build to order option on 2018 MacMinis and 2020 27" iMacs. 2x10G standard on the 2019 Mac Pro. 1x10G standard on the 2022 Mac Studio. The iMac 10G is also modern "Multi-Gig" that supports 2.5G and 5G as well as 1G and 10G.
This is fixed in Fusion 13.01 released today. Oddly enough VMware support sent me the usual - A pleasant day to you! Please be informed that the Bootcamp issue is being actively investigated b...
See more...
This is fixed in Fusion 13.01 released today. Oddly enough VMware support sent me the usual - A pleasant day to you! Please be informed that the Bootcamp issue is being actively investigated by our engineering team and we will reach out to you with an update as soon as we have a breakthrough. Thank you for your patience and understanding! So it is clear the support team for Fusion has no connection to the reality on the ground.
The other aspect here is that it's a MBP so the host network is WiFi. WiFi in Fusion and macOS 11 and beyond is generally iffy in my experience. On my M1 MacBook I did an experiment where I hooked ...
See more...
The other aspect here is that it's a MBP so the host network is WiFi. WiFi in Fusion and macOS 11 and beyond is generally iffy in my experience. On my M1 MacBook I did an experiment where I hooked my Thunderbolt 3-2 adapter, then my Thunderbolt to Gigabit Ethernet adapter (both the original Apple adapters to see if they worked with M1) and got better networking results than with the WiFi.
I usually do not bother with Linux guests as they do not get "out of control" disk spacewise like the Mac ones do. The automatic shrinks for Windows works on M1 so that is a good thing. The shrink ...
See more...
I usually do not bother with Linux guests as they do not get "out of control" disk spacewise like the Mac ones do. The automatic shrinks for Windows works on M1 so that is a good thing. The shrink process I am using is a manual one that is documented across a number of old posts here, but I will recap it. In the guest I first run a script to zero the disk space: #!/bin/sh cat /dev/zero > wipefile; rm wipefile sudo halt Then in macOS Terminal I run these commands on the VMDK file: /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -d Virtual\ Disk.vmdk /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -k Virtual\ Disk.vmdk I think on my older Mac guests the VMtool shrinks were done from inside the guest but that no longer works in the "modern era."
I checked things today with the latest round of updates applied, and all my "modern era" macOS disks shrunk as expected this time. This includes the 11.0 disks.
From what I understand Apple did not always use CPUs that supported nested virtualization. If you can post your exact Apple model and CPU we can probably confirm this. My recollection on MacBook Pr...
See more...
From what I understand Apple did not always use CPUs that supported nested virtualization. If you can post your exact Apple model and CPU we can probably confirm this. My recollection on MacBook Pros is that the low end and >high end< CPUs do not support nested virtualization but the mid-range CPU option did.
