VMware Fusion taking too long to expand disk

You need to extend the windows disk size from a running windows.

Here is how you do it: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007266

Now that you have extended the VMware image size, you need to start at #6 in the link.

EDIT:

I don't want to write a new answer, and the comment text-box isn't large enough - so here is a more less re-write of the link:

1) extend the VMware image size.

2) attach the HD image to an existing virtual disk of the same OS as the resized image (Virtual Machine Libary->[select the VM to use]->Settings->Hard Disks->[click +]->[select the new HD in left menu]->File name->Choose existing disk...->[navigate to the resized image, and select the .vmdk]->[choose "Share this virtual disk....."]->Open->Apply) - if you will go the safe way, you'll choose "Make a separate copy af the virtual disk" instead of the "Share this virtual disk...."

3) Start the virtual machine that you just attached the new HD to.

4) Now because you are using Windows 7, you need to go to "Start->Computer Management->Disk Manager" and right-click on the partition you need to extend, and select "Extend Volume".

5) power off (shutdown VM) - and remove the HD attached in #2 - don't delete it...!

6) if you in #2 choose to make a copy of the .vmdk, then you need to replace it manually in the VMware image file (package) - right click on the VMware image (.vmwarevm)->Show Package Contents.

7) Power on the virtual machine from #1, and verify the disk size change.

For what its worth I've seen the same issue with Fusion 6 and nmap. I also saw tcpdump fail as well:

sudo tcpdump -i vmnet8
tcpdump: vmnet8: No such device exists
(BIOCSETIF failed: Device not configured)

After upgrading libpcap to 1.40 and this still not resolving the problem, I found the following outdated post: https://communities.vmware.com/message/693833#693833

Specifically this quote is where the issue lies: "No guarantees, but we can try to take a look at implementing BPF on Fusion's network interfaces in a future release."

This seems to point to the issue being a vmware problem, so I tried VirtualBox 4.3.0 and when using NAT at least, the issues do not occur (nmap also worked for me):

$ ifconfig
…
vboxnet0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:00:00:00:00
inet 192.168.56.1 netmask 0xffffff00 broadcast 192.168.56.255

$ sudo tcpdump -i vboxnet0
tcpdump: WARNING: vboxnet0: That device doesn't support promiscuous mode
(BIOCPROMISC: Operation not supported on socket)
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vboxnet0, link-type EN10MB (Ethernet), capture size 65535 bytes