mlevin77's Posts

ok ping works, but even though I set up rules to allow UDP on port 3000 incoming and outgoing, an app (iMonnit) I'm trying to install is telling me it can't connect on that port. Is there anything else I should be checking for why it might be blocked?

so now I have the .vmx file edited as attached, but I'm still getting the same error.  What am I doing wrong?  Also weird, I wanted to post the latest vmware.log to see what the issue is now, and it hasn't created one - the last file is from Jan 26, how come it doesn't make a new one when I run and try to restart the VM?  

> Makes no sense to me as you obviously started the vmx-file one day ago:    well I've never interacted with it directly, I always just start the VM from the VMWare software, but I see it now that I'm looking inside the Package. >checkpoint.vmState = "Cloner - macOS 10.13 VM-49330c93.vmss" >to ># checkpoint.vmState = "Cloner - macOS 10.13 VM-49330c93.vmss"   ok I did that and when trying to boot it, it says File not found: Virtual Disk-cl1.vmdk   > or modify one of this lines: >sata0:0.fileName = "Virtual Disk-cl2-000002.vmdk" >sata0:2.fileName = "Virtual Disk-cl1-000002.vmdk" >sata0:3.fileName = "Virtual Disk-000002.vmdk"      how do I modify it - can I just get rid of the lines referring to sata0:2 ? >Do you need support with a recovery problem ? - call me via skype "sanbarrow" thank you!! I will.

> How about you attach a vmware.log and the .vmx for that problem VM?   Here's the log file; I can't find the .vmx - where should that be?   > There are ways to edit the .vmx so that the VM boots without loading the suspend file and without the disk that doesn't exist anymore. If you're afraid of that rendering the VM corrupt then ... backup before you make any changes.     Great! Let's edit it. How do I backup the VM - can I simply copy it, or I need to use the "duplicate" function?

  I did that once and the VM became completely unbootable. Although I have snapshots of this one, I'm still worried about losing it. Maybe I can back it up somehow... Can I tell it somehow that it doesn't need it?  Or, create a brand new, empty disk and point it to that file (and name it the disk it wants)? It's not the boot disk for that VM, just an accessory disk I mounted once.

Ok I'm further along... I "booted to firmware" in the cloner VM and selected one of the virtual SATAs, and now it booted, and I can see the other VM's disk.  Problem with CCC though: it says ccc has detected that there is another volume with the same unique identifier as the volume you selected I've fired off a request to CCC. I think it's because VMWare is assigning the same UI to each virtual machine's main disk.  I wonder if there's a way to change that? Also, now trying this: https://www.macstrategy.com/article.php?232#fusion seems to make sense.

hmm when do I hold down Option? I can't seem to do it. The machine is showing the circle with the line through it, and my options are only "Resume" - everything else is grayed out. And I can't hold Option and hit Resume, it doesn't restart it.    

I've tried the steps in   https://kb.vmware.com/s/article/2005146       but when I boot the system, which worked fine before I attached this other disk to it, I see:   so now it won't boot. It seems like just attaching the other disk broke the VM??  Also, I can't seem to attach or detach anymore, it says "This device cannot be added until the virtual machine is shut down. To add the device, first resume the virtual machine and then shut it down." but the "Shut down" option is grayed out.