• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

VM Orphaned

J

jenuster

Limp Gawd
Joined
Mar 8, 2011
Messages
154
Had a particular VM complaining that the datastore was full. I turned it off and tried to remove the snapshot in which I got an error saying that there was another operation going on. Now the particular VM is listed as orphaned.

I also noticed a HA event related to this VM, so I think it has something to do with this. Should I remove the vm from inventory and create a new vm and point back the vmdks?
 
Yes. Remove from inventory and then add it back in. Don't create a new VM. Remove it from inventory, browse the datastore, right-click on the .vmx file and then re-add to inventory.
 
Cool I didn't know that was an option! vm is not linked after host sync is the message I received when VCenter tries to register the VM.
 
Try restarting the management services on the vSphere host:

service mgmt-vmware restart
 
I think the reason I was getting that message (the second one) was HA was doing something after I re-added it to the inventory (most likely trying to start that machine). So I waited a few minutes, and all of a sudden the VM started. And then I was able to delete the snapshot which was causing the datastore to fill up.
 
Last edited:
Thanks. By the way iopetve, Vmware acknowledged the iscsi boot hang as an issue on their end due to the new iSCSI target login code.
 
jenuster said:
Thanks. By the way iopetve, Vmware acknowledged the iscsi boot hang as an issue on their end due to the new iSCSI target login code.
Click to expand...

That one is news to me. At least on the MD series, it's due to the firmware problem that is being fixed shortly (if not already - check the release notes on the latest release for the 3200 at least). I haven't heard anything from our end on a problem yet, but I'm also out of the office and only checking occasionally on email :)
 
You must log in or register to reply here.
Back
Top