Issue with VM machine on ESXi 4.1

I am unable to remove permission (eg. permission to access console) from a specific virtual machine.
Also, "edit settings", "migrate", and other menu are greyed, so I can't use them.
How can I solve this issue?

Thank you
Armitage318Asked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
My doubt is: is it safe to remove from inventory in this manner (I mean: directly from host, not through vSphere)?

Yes, no problems, and then you will likely see it disappear from the vCenter inventory, or appear as inaccessible, which you can then select remove from inventory.

Would appear there is something not correct with vCenter Database.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is there a current task in progress on that virtual machine ?

1. Restart Network Management Agents on the Host.
2. Restart vCenter Server service if you have vCenter Server.


if the above do not solve the issue, restart the host.

and maybe it's time to upgrade to a supported current version of ESXi e.g. 5.5 or 6.0.
0
 
Armitage318Author Commented:
Hi, is it safe to restart network agent when several VMs are running on the host?
Do you mean this command?

/etc/init.d/hostd restart

/etc/init.d/vpxa restart

service vmware-vpxa restart

?

Thank you
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
it is completely safe, to do the above, it does not affect VMs.

you can do what you have typed or

services.sh restart

or if you feel more comfortable you can do it at the Console from the menu.
0
 
Armitage318Author Commented:
Hi get this messages;

~ # services.sh restart
Running vmware-aam stop
Stopping vmware-aam: success

Running sfcbd-watchdog stop
Running vmware-vpxa stop
Stopping vmware-vpxa:success

Running wsman stop
Stopping openwsmand
Running slpd stop
Stopping slpd
Running vprobed stop
watchdog-vprobed: Terminating watchdog with PID 5752
vprobed stopped.
Running vobd stop
watchdog-vobd: Terminating watchdog with PID 5725
Vobd stopped.
Running storageRM stop
watchdog-storageRM: Terminating watchdog with PID 5703
storageRM module stopped.
Running sensord stop
sensord is not running.
Running lbtd stop
watchdog-net-lbt: Terminating watchdog with PID 5657
net-lbt stopped.
Running hostd stop
watchdog-hostd: Terminating watchdog with PID 5635
Running usbarbitrator stop
watchdog-usbarbitrator: Terminating watchdog with PID 5619
usbarbitrator stopped.
Running TSM-SSH stop
Stopping tech support mode ssh server
Running ntpd stop
Stopping ntpd
Running DCUI stop
Disabling DCUI logins
Running TSM stop
Hiding TSM login
Running TSM restart
Displaying TSM login: runlevel =
su -
Running DCUI restart
Enabling DCUI login: runlevel =
Running ntpd restart
Starting ntpd
Running TSM-SSH restart
Starting tech support mode ssh server
Running usbarbitrator restart
Rescanning all adapters..
usbarbitrator started.
Running hostd restart
Running lbtd restart
[81171904] Begin 'hostd ++min=0,swap,group=hostd /etc/vmware/hostd/config.xml', min-uptime = 60, max-quick-failures = 1, max-total-failures = 1000000
net-lbt started.
Running sensord restart
sensord started.
Running storageRM restart
storageRM module started.
Running vobd restart
Vobd started.
Running vprobed restart
vprobed started.
Running slpd restart
Starting slpd
Running wsman restart
Starting openwsmand
Running vmware-vpxa restart
Starting vmware-vpxa:success

Running sfcbd-watchdog restart
Running vmware-aam restart
Starting vmware-aam:vmware-aam already running - failed

host results "disconnected" in vCenter.
I am connected to this host through SSH, anyway.
What can I do ?
Thank yo
0
 
Armitage318Author Commented:
Sorry, host is UP again.
It seems I still have same issue with this specific VM.
Restarting vCenter Server service is it safe too ?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That looks normal...

yes, restart vCenter Server agents is safe.
0
 
Armitage318Author Commented:
Hi, I rebooted host, but I get same behavior.
It could be and issue with vmx file corrupt, in your opinion?
If so, how can I solve it?
Thank you
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Can you unregister the VM ?

remove from inventory ?

can you browse the datastore the VM is located ?

if you connect direct to the ESXi host, hosting the VM, are the settings still greyed out ?

is the VM powered On ?
0
 
Armitage318Author Commented:
I halted this VM, but I am still unable to unregister it.

If I access through vSphere to specific host, menu "remove from intentory" is clickable.

I am able to browse datastore.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay, so the issue is possible a datastore is unavailable ?

check your datastores?
0
 
Armitage318Author Commented:
Hi, I don't think it's a datastore issue. I have other VMs which are running fine (and they are "editable") on same datastore.
I was referring to an issue to specific VM (in particulary, with it's .vmx file)
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you browse the datastore (which you stated, you cannot), can you look at the VM folders and it's VMs ?
0
 
Armitage318Author Commented:
Hi,
as I said, I have no datastore issue.
I am able to browse datastore, browse VMs folder.
I have other VMs that are running fine on same datastore.
I have issue only with one specific VM, I mean: I am unable to unregistered, edit settings, and so on.
The only things that it seems I am able to do, is "remove from inventory" from specific HOST on which this specific VM is running (not through vCenter).
I don't know if, remove VM in this manner, could cause problem, anyway.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you access the host directly, not via vCenter Server, do you have the same issue.
0
 
Armitage318Author Commented:
Hi, when accessing to host directly, I can use "edit settings" menu.
If the machine is powered off, I can use "remove from inventory" menu too.
My doubt is: is it safe to remove from inventory in this manner (I mean: directly from host, not through vSphere)?
Thank you very much
0
 
Armitage318Author Commented:
Hi,
I succesfully removed affected VM from host, but now on vCenter I get "orphaned" status.
It is not a major issue, anyway, if you know how can I solve this cosmetic issue, it would be appreciated !
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Right Click and select DELETE
0
 
Armitage318Author Commented:
Hi,
I have no such option in vSphere, and I don't want to delete this virtual machine from datastore.
My goal was to options (like edit settings, user permission, and so on) available again.
Anyway, probably, as you said, there is something wrong in that vCenter database.
Thank you
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.