mailmichael's Posts

I figured this out on my own. The reason the screen is blank could be due to Display settings unsupported by the BIOS or grub.  I dumb downed my display settings, and now I can see the bios and grub... See more...
I figured this out on my own. The reason the screen is blank could be due to Display settings unsupported by the BIOS or grub.  I dumb downed my display settings, and now I can see the bios and grub boot.  Grub is failing to read the (hd0) partition table.  I'll be digging into this next, though not a vmware issue at this point.  At least I can now boot off a CDROM and use gparted to see the partition table is recoverable.   I just need to figure out how to get grub to see it.
I just resized my disk using the expand and then use gpartd to repair the gpt in the Linux guest.  Upon existing gpartd, it recommended rebooting so the kernel would reload the partition.  Now when I... See more...
I just resized my disk using the expand and then use gpartd to repair the gpt in the Linux guest.  Upon existing gpartd, it recommended rebooting so the kernel would reload the partition.  Now when I restart the guest, the screen spins for a while with "Waiting for connection." and then the screen goes blank.  Near the end of vmware.log is the host error "host: can't find smbios entry point". From the behavior of the system, this error must mean it is unable to load the bios.  Attempting to force bios setup upon restart results in the same failure, thus it doesn't appear to be related to the expanding of the disk. The disk went from 300GB to 400GB in size. With respect to the vmware.log file, the only issue possibly related is "AHCI: Tried to enable/disable IO space." shows up a couple times. Any ideas on how to resolve this issue?   Edit:  I did find this to be interesting.  In an older log (likely post disk expansion but pre-gdisk fix of gpt), I got the following differences in a couple places:  newest vmware.log: <, older vmware.log > < In(05) vmx DISK: Opening disks took 37 ms. --- > In(05) vmx DISK: Opening disks took 43 ms. < In(05) vmx DISKUTIL: (null) : max toolsVersion = 0, type = 0 < In(05) vmx DISKUTIL: Offline toolsVersion = 0, type = 0 ... --- > In(05) vmx DISKUTIL: scsi0:0 : max toolsVersion = 11269, type = 4 > In(05) vmx TOOLS setting legacy tools version to '11269' type 4, manifest status is 9 Both logs have the "vcpu-0 Host: can't find host SMBIOS entry point" entry, so this error could be a red herring.
Signum 11 is a segmentation fault, which is definitely a bug in Fusion.  It could be bad handling of a configuration error you have in your setup or a problem you can do nothing about until they fix ... See more...
Signum 11 is a segmentation fault, which is definitely a bug in Fusion.  It could be bad handling of a configuration error you have in your setup or a problem you can do nothing about until they fix it. If you haven't already, look at the fs type and mount options for the external disk and make sure it isn't setup as a removable device.  Here are the mount type and options for my home directory on my older, macbook pro 2014 vs macbook air 2000-m1:  2014 macbook pro: apfs, local, journaled, nobrowse  2020 macbook air m1: apfs, local, journaled, nobrowse, protect  To make sure you are looking at the correct disk partition:  cd ~  df .  # look for the disk at the start and grep for it in mount replacing my entry:  mount | grep /dev/disk3a5  The VMWare Fusion v12 is installed on my Macbook Pro.  A couple years ago, I moved nearly everything off but left VMWare Fusion and my Linux VM.  I updated fusion too.  It was a hack job, where I may have removed contents under Library/Preferences.  My Linux VM runs and mounts hgfs, but clipboard doesn't work.  It gets a lot of the same issues of not finding files as in your log, but neither of the warnings -- even without having an /etc/vmware/hostd file. The only file it does appear to read is ~HOME/Library/Preferences/VMware\ Fusion/preferences, where your log doesn't list this file.  The differences are likely in the version of Fusion.  I have a Mac-mini with Fusion at home, so can check out the logs when I'm back there later. Hope this helps.  I'm just a user of VMWare, but had a recent issue so thought I'd pitch in to help. 
I appreciate your attempt to help, but I'm confused as to why a problem with synchronization between the store-us and customerconnect accounts is related to VMWare Workstation.  Can you elaborate?  T... See more...
I appreciate your attempt to help, but I'm confused as to why a problem with synchronization between the store-us and customerconnect accounts is related to VMWare Workstation.  Can you elaborate?  Thanks. 
I just purchased Workstation Pro and got an email with my license key.  On another machine without access to email, I went to my VMware store account and only found an invoice without a key.  Went to... See more...
I just purchased Workstation Pro and got an email with my license key.  On another machine without access to email, I went to my VMware store account and only found an invoice without a key.  Went to VMware connect and found two old licenses under "Manage licenses" but can't find my most recent.  Went to register the key and it says the key is invalid.  There is no one to assist.  No number.  No email.  No form.  No chat.  Just some stupid auto assistant that is worthless and too time consuming. 
I realize a lot of time has gone by on this issue, but I had something similar and resolved it.  My issue was due to not responding to a prompt in a timely manner after resume completed. It was a... See more...
I realize a lot of time has gone by on this issue, but I had something similar and resolved it.  My issue was due to not responding to a prompt in a timely manner after resume completed. It was asking me if I wanted to replace or append a file for serial port output.  This error appears in the log on failure but not on success: 2013-03-01T06:53:47.093-08:00| vmx| I120: GuestRpcSendTimedOut: message to toolbox timed out. 2013-03-01T06:53:47.093-08:00| vmx| I120: Vix: [6088 guestCommands.c:1926]: Error VIX_E_TOOLS_NOT_RUNNING in VMAutomationTranslateGuestRpcError(): VMware Tools are not running in the guest I notice you had the same error appear in your log: Apr 02 11:00:33.154: vmx| GuestRpcSendTimedOut: message to toolbox timed out. Apr 02 11:00:33.209: vmx| Vix: [12616 guestCommands.c:2392]: Error VIX_E_TOOLS_NOT_RUNNING in VMAutomationTranslateGuestRpcError(): VMware Tools are not running in the guest Is there a chance your not responding to a prompt in time?