VMware Communities
PrinceAlbert
Contributor
Contributor

Fusion 12 Hanging on startup

 

Today for no apparent reason, when I started VM Fusion 12, it just hangs.

What should I do first to resolve this problem.

I've been running Big Sur since it's release.

I have removed it and re-installed, same thing happens

0 Kudos
44 Replies
blahblahyooho
Contributor
Contributor

Hi

You can obvs hear the frustration. I posted what others had been asked for in their messages which was just the log. 

Mac Model: MacBook Pro (15-inch, 2016)

2.7 GHz Quad-Core Intel Core i7

16 GB 2133 MHz LPDDR3

Radeon Pro 455 2 GB

Fusion Pro 12

Ordered and downloaded: 2022-04-29

I have reinstalled Fusion Pro twice since my order date above. 

The issue resolved itself the first time as others have said. I did have to wait all day (about 6 hours) though. This happened again on Monday this week (the third time) during my exam unfortunately but it again resolved itself after an hour this time and VMWare started working again after it gave me the message that "Application Not Responding".

Please find the logs you requested attached too. I couldn't locate the "vmware.log" file in the VM's directory unfortunately so I attached the logs I could find in /Library/Logs/VMware Fusion.

I followed this advice: https://kb.vmware.com/s/article/1017838

Appreciate your time and expertise because I'm stumped.

 

 

0 Kudos
larrycable
Contributor
Contributor

@Mikero 

same problem Fusion 12.1.2 on iMac running Catalina 10.15.7 fusion hangs.

"top" reports that the process is consuming 99-100% cpu - busy waiting on something?

 

I am attaching an 'lldb bt all' below ...

I also dtruss'ed the process and got this:

madvise(0x7F89B0D20000, 0x2A8000, 0x7) = 0 0

madvise(0x7F89B08B8000, 0x468000, 0x7) = 0 0

madvise(0x7F89B0D20000, 0x2A8000, 0x7) = 0 0

madvise(0x7F89B0FC8000, 0x2A8000, 0x7) = 0 0

madvise(0x7F89B08B8000, 0x710000, 0x7) = 0 0

madvise(0x7F8920B80000, 0x2A8000, 0x7) = 0 0

madvise(0x7F89B08B8000, 0x468000, 0x7) = 0 0

madvise(0x7F89B0D20000, 0xD18000, 0x7) = 0 0

madvise(0x7F89208D8000, 0x2A8000, 0x7) = 0 0

madvise(0x7F8920B80000, 0xA80000, 0x7) = 0 0

madvise(0x7F8970470000, 0x2A8000, 0x7) = 0 0

madvise(0x7F8970008000, 0x468000, 0x7) = 0 0

madvise(0x7F8970470000, 0x2A8000, 0x7) = 0 0

madvise(0x7F8970718000, 0x2A8000, 0x7) = 0 0

madvise(0x7F8970008000, 0x710000, 0x7) = 0 0

this pattern of madvise calls is repeated, which I think is the "busy wait" I am seeing consuming 99% cpu

 

I also have a full lldb process save-core file but it is large (approx 5Gb) you can find it here:

https://drive.google.com/file/d/1zxdOuG1WiY1idsAJnFo6XI2-Oxq6Qd6T/view?usp=sharing

MacOs "compressed" lldb core.

hope this helps!

 

 

PPisKing
Contributor
Contributor

Same issue, on Fusion 13. now

0 Kudos
PPisKing
Contributor
Contributor

Are you still following the issue? They provided things you asked then you disappear? 

0 Kudos
Croxton23
Contributor
Contributor

Thanks for sharing this.

0 Kudos