Hey friends this is not my first dance here... I'm not testing the shared folders feature if that was not clear. The macos file sharing uses samba and it pushes a few hundred MB/s between physical h...
See more...
Hey friends this is not my first dance here... I'm not testing the shared folders feature if that was not clear. The macos file sharing uses samba and it pushes a few hundred MB/s between physical hosts with the same hardware. My question is around the TP version of fusion being slow at filesharing traffic with the current version of fusion. It's not an issue with a specific host as the reporting team has the same issue with a bunch of systems in our server room. I know that Fusion has adopted the macOS network stack for recent versions of the product and I'm wondering if it'a know issue with that stack being slow with large transfers?
We have internal reports from a team that has a number of different systems showing the same issue. For my repro test I'm using the following. MacPro 2019 16 Core 256GB RAM macOS 12.6 10Gbit ethern...
See more...
We have internal reports from a team that has a number of different systems showing the same issue. For my repro test I'm using the following. MacPro 2019 16 Core 256GB RAM macOS 12.6 10Gbit ethernet VM is macOS 12.6 8 Core 32GB RAM 100GB NVME disk Setup file sharing on the host system with the internal NVME drive as the target. Mounted the share via the finder and then ran AJA speed test against the share.
We have received some reports of very slow transfer speeds from macOS guests. Host: macOS 12.6 Guest: macOS 12.6 vmxnet3 Tried NAT and Bridged Host is getting 300 MB/s transfers and the guests ...
See more...
We have received some reports of very slow transfer speeds from macOS guests. Host: macOS 12.6 Guest: macOS 12.6 vmxnet3 Tried NAT and Bridged Host is getting 300 MB/s transfers and the guests are seeing 50 MB/s. Is this a known issue?
If you boot from the installer .iso for Monterey that gets you recovery mode. Once you disable SIP you can keep the nvram file around and swap it in anytime you want to boot a VM with SIP disabled. ...
See more...
If you boot from the installer .iso for Monterey that gets you recovery mode. Once you disable SIP you can keep the nvram file around and swap it in anytime you want to boot a VM with SIP disabled. Yes, that took me a while to sort out... Blake
Jinks! Yep with some new hardware showing up this week updating my ubuntu packer template is top of mind. Looked at this doc that potentially you could cram the newer kernel into the live install...
See more...
Jinks! Yep with some new hardware showing up this week updating my ubuntu packer template is top of mind. Looked at this doc that potentially you could cram the newer kernel into the live installer image. https://askubuntu.com/questions/94156/installing-with-a-different-kernel Stares at the pile of projects I have started recently. I'll probably just wait as burning hours hacking up an iso is not the best use of time. Cheers, Blake
Looks like those have not hit the daily ubuntu builds yet. curl -s https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/jammy-live-server-arm64.manifest | grep linux-image linux-image-5.15....
See more...
Looks like those have not hit the daily ubuntu builds yet. curl -s https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/jammy-live-server-arm64.manifest | grep linux-image linux-image-5.15.0-23-generic 5.15.0-23.23 linux-image-generic 5.15.0.23.25
Agreed. Helpful user reports with details assist the team with debugging and priority setting. Wouldn't hurt if Apple would chill out with breaking changes either.
I'm also noticing a reduction in functionality. Previously the About this mac info box would show "Apple paravirtualized Graphics Device" and I'm not seeing that on recent VM builds. Host macOS 12.3...
See more...
I'm also noticing a reduction in functionality. Previously the About this mac info box would show "Apple paravirtualized Graphics Device" and I'm not seeing that on recent VM builds. Host macOS 12.3.0 Fusion 12.2.3 Working graphics accel and shows in about box 11.6.5 12.1 Not working, No transparency under menus and not showing in about box 12.3 12.3.1 12.2.1
it's significantly faster to build an .iso and use that directly than upgrading an existing VM. You can use this script/process to make macOS 12.x iso that works with fusion. https://github.com/tro...
See more...
it's significantly faster to build an .iso and use that directly than upgrading an existing VM. You can use this script/process to make macOS 12.x iso that works with fusion. https://github.com/trodemaster/packer-macOS-11#prerequisite-installer-bits These isos work for manual installs or you can use the packer process if you need to automate the process. Blake
Yep, it's got some issues. If you use SVGA to install the OS and tools then turn on appleGPU it should work. You might give the OS a clean reboot even after enabling any extensions before turning it ...
See more...
Yep, it's got some issues. If you use SVGA to install the OS and tools then turn on appleGPU it should work. You might give the OS a clean reboot even after enabling any extensions before turning it on. https://communities.vmware.com/t5/VMware-Fusion-Discussions/Panic-with-macOS-vms-on-boot-when-appleGPU0-is-enabled/td-p/2883718
I have seen a couple of posts that are likely the same issue but wanted to share what I'm seeing. After building a macOS VM 11.x or 12.x on macOS 12 hosts (possibly 11.x as well) the VM will panic on...
See more...
I have seen a couple of posts that are likely the same issue but wanted to share what I'm seeing. After building a macOS VM 11.x or 12.x on macOS 12 hosts (possibly 11.x as well) the VM will panic on boot sometimes. It appears to be related to having apple GPU enabled and approving kernel extensions using the system preferences panel. macOS seems to be booting up in a different state than normal after you approve a kernel extension or do upgrades. Repro steps.. Install macOS and then enable the appleGPU Install something that requires kernel extension approval. Approve the kext in the system prefs security pannel. Reboot the VM and it will panic on boot Remove the apple GPU vmx settings and restore SVGA ones Boot the VM up shutdown the VM add back appleGPU0 vmx settings VM boots up happily I had missed this issue with my automation for building macOS vms previously as I'm enabling the apple GPU only after tools and upgrades are completed. Hopefully, this issue can be addressed before the apple GPU feature is considered a release quality feature. Sure does work well once the VM is all dialed in tho!! Blake
I have confirmed that fusion 12.2 is working with packer 1.7.2 on macOS 11.6 for me today. The packer code still searches the leases file for IPs they just added the newer source as well.
Hopefully, this issue is just resolved with the next beta. Here is a screenshot from a VM booting in single-user mode. ACPI Error: PSTA namespace lookup failure AE_NOT_FOUND 20160930/psaregs-463
Look into editing the internet sharing settings for macOS. Fusion is using the network services provided by the OS now. This article seems like a good starting point. https://www.amsys.co.uk/change-i...
See more...
Look into editing the internet sharing settings for macOS. Fusion is using the network services provided by the OS now. This article seems like a good starting point. https://www.amsys.co.uk/change-internet-sharing-subnet-on-mac-os-x/
I went to add a second NVME virtual disk to an existing macOS 11 vm to store some data. After booting up the VM it does not show up in system report or disk utility. Shut down the VM and change it to...
See more...
I went to add a second NVME virtual disk to an existing macOS 11 vm to store some data. After booting up the VM it does not show up in system report or disk utility. Shut down the VM and change it to scsi and the disk shows just fine on next boot up. Is there some known issue around multiple NVME disks? host is macOS 10.15.7 Fusion is 12.1 Guest is macOS 11.1 beta Thanks, Blake
Yeah Apple leaving features out when shuffling APIs around is Standard Operating Procedure for them... Here is what I propose doing. BRIDGE_IF=$(pgrep -lf rtadvd | grep -E -o "bridge[0-9]+") ...
See more...
Yeah Apple leaving features out when shuffling APIs around is Standard Operating Procedure for them... Here is what I propose doing. BRIDGE_IF=$(pgrep -lf rtadvd | grep -E -o "bridge[0-9]+") MAC_ADDR=Get the mac addr from fusion gui and collapse any leading zero padding sudo arp -i $BRIDGE_IF -a | grep $MAC_ADDR | grep -E -o "([0-9]+\.){3}[0-9]+" Exposing the resulting IP via one of the vmrun commands like this would be ideal for the long term. vmrun readVariable '/Users/blake/Virtual Machines.localized/macOS 11.0.vmwarevm/macOS 11.0.vmx' runtimeConfig ip You should be able to use the ndp tool to get the IPv6 addresses in a similar manner but didn't have time to sort that part out yet.
Had a quick update from Michael today via email. Sounds like we are still waiting to hear back from Fusion engineering on how this is supposed to work going forward. I have opened a bug to track ...
See more...
Had a quick update from Michael today via email. Sounds like we are still waiting to hear back from Fusion engineering on how this is supposed to work going forward. I have opened a bug to track this behavior on the packer side as well. https://github.com/hashicorp/packer/issues/10177
Is it expected that the /var/db/vmware/vmnet-dhcpd-vmnet8.leases file be populated with guest os dhcp leases when the host is Big Sur macOS 11? The packer tool expects to parse this file to get t...
See more...
Is it expected that the /var/db/vmware/vmnet-dhcpd-vmnet8.leases file be populated with guest os dhcp leases when the host is Big Sur macOS 11? The packer tool expects to parse this file to get the IP of created VMs before the OS responds in any way. What I'm seeing is that file is empty even if the guest VM is reachable with a dhcp provided IP. Depending on how it's supposed to work in the new hypervisor.framework style I'll open a bug with VMware Fusion or packer. Please Advise, Blake
