As in the subject. Guest is openSUSE 15.5.
Snapshots used to work. Maybe this is related to recent Macos upgrades. I am currently on Ventura 13.5.1. Not long after upgrade to 13.5. Can't remember if maybe the snapshots only worked before 13.5.
I have a full generated problem report, but it's way too big to post here (400 MB).
I would like to file a proper bug report, but it doesn't seem to be possible.
Any ideas how I can trouble report this?
What version of Fusion, and what Mac are you running this on?
Are you running VMware Tools in the VM, or are you running open-vm-tools? (You should be running open-vm-tools, provided by openSUSE and not the VMware Tools you install from the Fusion GUI).
As far as the size of the problem report, try a quick report and post it here. Someone here might be able to take a look at it and see if they can see anything that might help. If that's still too big, unzip the product report. Sometimes a smacOS ystem log file might be very large and deleting it and re-zipping the remainder might get enough information for initial triage.
If you have a free personal use license for Fusion, this forum is the only mechanism to get help for Fusion. But there's no guarantee that anyone other than other users will see and act on it. This forum is a user-to-user forum, and VMware Technical Support or developers do not actively monitor this for problems.
If you purchased a license for Fusion, you can open a service request (tech support ticket) with VMware tech support. If your license was purchased within the last 30 days, you can open a service request for free. Otherwise you'll need to purchase a per-incident service request "voucher" through the VMware Online Store, then you can open a service request through the Customer Connect portal.
Sorry about that. I had tagged it as Fusion 13.
It's Fusion 13.0.2. The Mac is Macbook Pro M1 16-inch 2021. I run open-vm-tools in the guest.
You were correct about the system log. It was over 3GB. Also two of the vmware logs were huge, over 500 MB each. So I have drastically cut those to, hopefully, leave the full report almost intact (where it matters).
In the vmware logs there is some indication that something is seriously wrong with the svga driver. 'vmware.log' and 'vmware-0.log' both contained several million lines with the same entry: "svga SVGAMob: Mob mapping succeeded on retry with fallback". 4.661.593 and 6.470.624 respectively. I grepped out those lines from the logs and left everything else. It shrunk the sizes so that I can post it here. Regarding the Macbook system log, I discarded everything except the last 65.000 lines. The reason for this is that 'vmware.log' show:
2023-08-31T15:57:09.678Z In(05) vcpu-0 [msg.panic.haveLog] A log file is available in "/Users/anticn/Virtual Machines.localized/opensuse.vmwarevm/vmware.log". 2023-08-31T15:57:09.678Z In(05) vcpu-0 [msg.panic.requestSupport.withoutLog] You can request support. 2023-08-31T15:57:09.678Z In(05) vcpu-0 [msg.panic.requestSupport.vmSupport.apple.menu] 2023-08-31T15:57:09.678Z In(05)+ vcpu-0 To collect data to submit to VMware support, choose "Collect Support Information" from the "Help" menu.
So I kept everything after a few seconds before this event in the system log.
I do have paid license, but it's older than 30 days. And it doesn't feel right that I should fork out even more just to report a problem with the system. As I see it have actually wasted several hours because of this problem, and to add insult to injury they want me to pay in addition? I also run the same guest on Parallels on a different machine and they provide support for paying customers, which is the decent thing to do. I don't understand how VMWare became like this. A few years back I could talk to them when there were problems.
So I have attached the "full" support information (except what I describe above).