Tag Archives: VMWARE

VMWare Fusion VMon mismatch

27 Feb

Credit for the fix – https://www.tweaking4all.com/forum/applemac-hardware/macos-fix-vmware-fusion-version-mismatch-with-vmmon-module/

1. Close VMware Fusion
2. Open the Terminal and execute:

sudo rm -rf /System/Library/Extensions/vmmon.kext

sudo cp -pR /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext /System/Library/Extensions/

sudo kextutil /System/Library/Extensions/vmmon.kext

3. Exit Terminal and open Fusion again.

Now … you may run into an error message with the last command.
In that case you can try the following command, or like I had to do: reboot your Mac and try that last command again;

sudo kextunload /System/Library/Extensions/vmmon.kextd

VM stuck in a boot loop fix

28 Sep

Recently had a VM Stuck in boot loop due to Windows update not installing correctly, fixed it by mounting the server2012.iso and running the following command.


Server Boot Loop Fix

BSOD after converting from Hyper V to VMWARE

7 Aug

Changing LSI_SAS to 0 worked for me, original guide below;


VMWare P2V tool – Stuck at 1%

31 Jul

When using the standalone convertor make sure you use “run as administrator”.

VPXUSER continually downloading

9 Sep

I had the same problems. vpxuser tries to download a new config for your VM.


To fix this problem:

  1. go to your VM and set the Permission for the user “vpxuser” on no acces.
  2. then go in your VM setting and replace all adapter with a new one
  3. check all VM settings if they are correct
  4. give the vpxuser the permission back
  5. look if the problem is solved

Default VMWare Username and Passwords

17 Dec

Great resource, still scares me how many sysadmins dont change these!



FSCK needs to be run manually on VM start

10 Mar

Linux Volume Cleaning

Sometimes a virtual linux machine will not start up properly due to a file system issue.  If this happens, a manual file system check (fsck) will need to be performed.

To perform a manual file system check you will need to boot into GParted followed various commands in the system.
Below is a step by step guide to fix this problem:

  1. Log into vCenter
  2. Find the machine that is having the issue
  3. Power Off the machine
  4. Click on Edit Settings
  5. Click on Options
  6. Choose to boot into the bios on next boot
    PSPHP - Virtual Machine Properties
  7. Start the machine
  8. When in the bios mount the GParted and change the boot order to have the CDROM first
    • the GParted disc can be found on Nerd>ISO>Linux
    • An alternative option is that when the machine boots up press ESC.  This will allow you the time to add the GParted disc and boot menu will appear
  9. Choose GParted Live (default settings)
  10. Choose Don’t Touch keymap
  11. Press enter to choose the default language which is English
  12. Choose 2
  13. Type fdisk -l
    • This will list all of the disks that will need to fsck
    • Make a note of the this, but it will also be onscreen
  14. Type fsck -y /dev/<device boot from step 13>
    • Example is fsck -y /dev/sda1
    • Errors may appear but can be ignored
    • the -y is to try and automatically fix any errors found
  15. Repeat step 14 for all devices in step 13
  16. Type reboot
  17. Eject/remove the disc when told to

In the case of an LVM that is dirty do these commands.

vgchange –ignorelockingfailure -ay

The LVM should be active now

lvscan –ignorelockingfailure

Now you can run fsck on the LVM

fsck -y /dev/mapper/LVM label

Once all partitions are clean, issue the command shutdown -h now. Remove Live CD and turn back on.

Reference: http://www.turnkeylinux.org/forum/support/20110906/turnkey-lamp-vmware-esx-400-server-now-fails-boot-drops-initramfs-how-i-fix-f