Error: Received Signal 11

[kneemaa]

When trying to use vfuse to create the VMware image, we're getting the error "Error: Received Signal 11" during then immediately having the process fail.

I have replicated this with the following.

System OS: macOS 10.13.6
Original DMG: macOS 10.13.6
vFuse Version: 2.0.6
AutoDMG Version: 1.9

and

Round 1
System OS: macOS 10.14.0
Original DMG: macOS 10.13.6
vFuse Version: 2.0.6 
AutoDMG Version: 1.9

Round 2
System OS: macOS 10.14.0
Original DMG: macOS 10.14.0
vFuse Version: 2.0.6 
AutoDMG Version: 1.9

Output

Password:
Mounting osx-10.13.6-17G65.apfs.dmg
macOS version is 10.13.4
Unmounting /Volumes/Macintosh HD 1
Using VMware Fusion path: /Applications/VMware Fusion.app
Converting DMG to VMDK
/Error: Received signal 11.
Unmounting /dev/disk3```

Unsure why this is failing on High Sierra with another High Sierra installer when this worked previously.

[chilcote]

Fusion 11 introduces this bug. I have a ticket open with VMware. Point vfuse to a copy of Fusion 10 in the meantime. Or use qemu-img.

[kneemaa]

Thank you, I've confirmed this works for now.

[chilcote]

I would encourage everyone who relies on this functionality to open a bug report with VMware. Reference report no. 18931231409 if you want to pile on. More info and a quick example to replicate: https://gist.github.com/chilcote/e044f844dcb28353446dd01f7415914c

[sadcup]

Hi, there

I am not so familiar with the usage of vFuse.
Does the tool run under pure command line environment please?
So is it acceptable that running the command line after VMware Fusion opened manually(or using script)please?

Best Regards

[chilcote]

It's a command line tool only, yes. And you can run it with Fusion open or closed, as it's utilizing binaries from the Fusion library (/Applications/VMware Fusion.app/Content/Library).

[sadcup]

Hi, chicote
I understand now.
Thanks for your reply.

[devlinford]

I would encourage everyone who relies on this functionality to open a bug report with VMware. Reference report no. 18931231409 if you want to pile on. More info and a quick example to replicate: https://gist.github.com/chilcote/e044f844dcb28353446dd01f7415914c

To clarify...we need to downgrade VMware Fusion from 11 to V10 so we can get this to work? Or can we have both installed at the same time and somehow point the command to use V10?

Thanks,

[mistacabbage]

I also get Error: Received Signal 11 with VMware Fusion Professional Version 11.0.1 (10738065). I put the 11.0.1.app in the trash and emptied it then reinstalled 10.1.4 (10700604) and did not get Error: Received Signal 11. Then I put the 10.1.4 app in the trash and emptied it, reinstalled 11.0.1 and the .vmware file booted normally.

[chilcote]

Additional notes on this bug, and how to work around it here: https://github.com/chilcote/vfuse/wiki/Received-signal-11

[erikng]

Would make a great blog post

[chilcote]

If only I knew someone with a blog.

[Honestpuck]

This issue persists with Fusion v11.0.2 dated 21 November 2018

[chilcote]

Yep sure does. VMware says it'll be fixed in the next release, with the caveat that the Fusion app will need to be running.

[motionbug]

New release of Fusion version 11.0.3 Build 12992109 does not fix the Error: Received signal 11

[mikedowler]

Sadly, not fixed in Fusion 11.0.3 as far as I can see. (Sorry - that's what happens when you don't refresh the page before commenting)

[chilcote]

Yeah that's a shame. I've pretty much settled on using qemu-img for now.

[motionbug]

yeah moving to that myself @chilcote

Thanks

[mikeroySoft]

Just FYI, but we are planning to ship a fix for this in the next few weeks. We wanted to get it in 11.0.3 but that release was specifically to address security vulnerabilities disclosed to us. I regret that we weren't able to bundle this fix with the .0.3 release, but please be assured it's coming =)

[mngrant-zz]

Not to be impatient, but a new version of macOS has shipped and this still isn't fixed.

[erikng]

There's no need to wait for VMware to fix it.

[chilcote]

11.1.0 purports to fix this, if someone wants to test.

https://docs.vmware.com/en/VMware-Fusion/11.1.0/rn/VMware-Fusion-1110-Release-Notes.html

[rickheil]

11.1.0 fixed the issue for me, although as noted the app must be launched. This is the traceback I get if the app is not running:

Mounting osx-10.14.2-18C54.apfs-100gb.dmg
macOS version is 10.14.2
Unmounting /Volumes/Macintosh HD 1
Using VMware Fusion path: /Applications/VMware Fusion.app
Converting DMG to VMDK
\Error: AppleXPC: Failed to connect to service com.vmware.MountHelper
AppleXPC: Failed to connect to service com.vmware.MountHelper
HOSTDISK-MACOS: Failed communicating with mount helper.
AppleXPC: Failed to connect to service com.vmware.MountHelper
Failed to convert disk: This function cannot be performed because the handle is executing another function (0x5).
Unmounting /dev/disk7

[chilcote]

Fixed in Fusion 11.1.0. vfuse will alert you if Fusion is not running now.

[motionbug]

FYI
@chilcote fixed in Vmware version 11.1.0