AlessandroDN's Posts

Hi dear community I have an Intel MacBook 2019, that I recently updated to macOS Sonoma 14.1 with VMware Fusion 13.5. On this host I run a macOS Sonoma 14.1 VM that used to run flawlessly on macOS Ventura 13.4. Every time I start the VM, the first time I login I found a windows saying that WindowsServer crashed (see attached picture). This seems related to the Apple Paravirtualized graphics; if I switch back to the plain SVGA the crash doesn't occur. I tried uninstalling/reinstalling the VM tools but nothing changes. Is anyone experiencing something like this? I have my other Intel iMac that I'm holding back to Ventura and wonder if this behavior is specific of my config? Thanks for any input on this

Hi all, I hope everyone is OK. I have a weird issue with the VM networking. If I connect to a WiFi without internet access, the VM's network interface goes down (like the cable has been disconnected). I don't remember this was the behavior. The VM has a NAT device, and I was expecting to reach at least the host. I'm on Fusion 13.0.1, on Ventura 13.3, and I tried different VMs and operating systems, and it seems not related to the VM itself but to VMware (or Apple), bringing the virtual network interface down. Does anyone have a clue? Ciao Alessandro

I don't know if someone is using `vctl`, but I found it very useful. It lets you run docker containers out of the box without installing Docker on the Mac. I'm having some issues pulling an image greater than 4GB. It seems that's the maximum allowed size and I didn't find any way to customize it. It seems this is an [old issue](https://github.com/vmware-archive/vctl-docs/issues/48), but nobody addressed it yet. BTW, do you know if `vctl` is still maintained? It seems like a lovely PoC, but I have many issues using it. For reference, I’m using Fusion 13 on macOS Monterey, although I think this is not related to my specific configuration. Thanks for any help here.

Hi all, I'm trying to use `vctl` on Fusion 13 on a Monterey host (Intel) to run a stock Ubuntu 22.04 image. This is what I'm doing: vctl pull ubuntu:22.04 vctl run --interactive --tty ubuntu:22.04 /bin/bash In the container shell I'm trying to update/download packages and I receive a weird error apt update Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB] Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB] Reading package lists... Done E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' provides only weak security information. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' provides only weak security information. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' provides only weak security information. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' provides only weak security information. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. At the beginning I though it was something related to the Ubuntu image and then I try running exactly the same test on Docker running on a Linux VM and everything works fine ‌ ‌ I verified the container can access the network. Do you have any idea what's going on? Thanks

Hi all, great to finally have Fusion 13 with us. I run Fusion 13 on a macOS 13 Intel host. I have a macOS 13 guest that was running fine with Fusion 12: the only issue I had was to set vmxnet3 as network interface to have network running properly. Now, I updated to Fusion 13, updated the VMware tools within the guest, and have the following behavior: - if the network interface is set to vmxnet3 the VM runs fine and stable, even with Paravirt video enabled - if the network interface is set to e1000e (the default when creating a VM for macOS 13) the VM hangs during boot and/or crashes right after boot. I tried also upgrading virtual HW to the latest version 20 with no success. I also created a new macOS 13 VM, and it comes with the e1000e network adapter by default. What's the preferred network interface to use with Mac guests? Any hint is more than welcome.   Please find attached vmx, and both the logs for the e1000e network adapter and the one with vmxnext.

Hi all, I have upgraded to Fusion 12.2, on a Big Sur host (11.6). My Big Sur VM has been upgraded to 11.6.1 and I update the tools to the version coming with Fusion 12.2. After the upgrade of the tools, the VM has a video resolution of 1024x768, as if there is some error with the video driver. I'm using the normal SVGA (not the Apple GPU) and before the VMTools update, the video resolution was fine. Did something change in the VM Tools distributed with 12.2? Thanks for any help!