Hi,
Can the VMware Tools on Windows Server virtual machine be upgraded without restarting the vm after update?
Hi,
Can the VMware Tools on Windows Server virtual machine be upgraded without restarting the vm after update?
hello all
vCSA 6.5 OVA file deploy in VMware workstation stuck in [Waiting for RPM Installation to finish (64% done.)]
take a long time no change what is the problem
Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details
I tried to turn on all dot net
I have 2 VMs running under VMware cluster of 6 ESXi hosts.
These 2 VMs are oracle RAC nodes.
I want HA/DRS should be disable on these 2 VMs , so that VMware cant move these VMs incase of any failure. Oracle RAC will take care of that.
Pls suggest
Dear all,
one of my VM is unaccessible I want want to reset it somehow.
From command line:
vim-cmd vmsvc/power.off 288
Powering off VM:
Power off failed
or another try to kill
esxcli vm process kill -t force -w 46664
or
esxcli vm process kill -t hard -w 46664
Unable to kill Virtual Machine. Error was : Unable to kill virtual machine. Error returned was No such process
but under:
esxcli vm process list
this ID is still active:
plsw-ts2012-fe1
World ID: 46664
Process ID: 0
VMX Cartel ID: 46640
UUID: 42 24 e8 f3 28 35 e1 77-dd 56 40 46 d2 a4 16 43
Display Name: plsw-ts2012-fe1
Config File: /vmfs/volumes/5156099e-00b6e9ef-83be-e41f131c77b4/plsw-ts2012-fe1/plsw-ts2012-fe1.vmx
Regards
GN
I have two HP DL380G6 servers running ESX4i. These servers are equipped with four 1-gigabit NICs. On Server1 all 4NICs are configured and running at 1000mbps.
However, Server2 indicates that one of the network cards is working at 100mbps instead of 1000mbps. 100mbps is listed for both the configured and actual speed, but I can't seem to change it within vSphere/vCenter. The other 3 NICs in server2 are running at 1000mbps.
Any advice would be greatly appreciated!
This is 5.5.0 build 1331820 hanging on "nfsclient loaded successfully". The host is part of a ESX cluster and was running fine until after we had to rebuild vCenter server. All other hosts and everything else in the cluster is working fine. Has anyone seen this issue? I tried letting it sit for 20 minutes, then cold booted again and still the same.
This is on an HP ProLiant.
Any ideas will be appreciated.
Hello Friends,
I am in need of a little help.
have 2 esxi 5.0 host and a vcenter as VM.
My lab was working good since days, but all of a sudden not sure why I am not able to connect to ESXi Hosts using vSphere Client.
Error:: The request failed because the remote server took too long to respond.
Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "192.168.1.101" failed.
Yes, I am able to connect to vCenter server, when connected to vCenter and opening the VM console, nothing shows up, its a Black screen, as if the VM is off. This is with all VMs on both hosts.
1st I thought it might have to do something with vCenter and I tried connecting to Host individually which I was not able to.
After going through some KBs on vmware and some articles, I checked the firewall state on both hosts.(attached screenshot)
Checked if my workstation can talk to esxi host on port 80, 443, 902. all ports are accessible.
Disabled Symantec endpoint protection and checked. no positive results.
Lastly, I tried browsing the ESXi host via web browser i.e., http://ESXi-IP-Address which redirects me to HTTPS connection with certificate error, when I continue with the cert error, the URL keeps loading and the Host page does not shows up as it should.
This issues are on both hosts. :-(
Can you guys point me to right direction to troubleshoot this issue.
Thanks.
So I got my evaluation license for ESXi 6.0 a while back and tried installing it on the various systems I had available (no real servers, alas.) Despite having some hardware that was top tier at one time, the only thing that ESXi would install cleanly on was an ancient consumer-grade Dell Inspiron 570. No problems with network or SATA drivers or VT-d/IOMMU, just installed - no muss, no fuss. However, this thing is pretty limited. It has a triple core processor, and maxes out at 16GB of RAM. Now I was looking online and saw some old Dell Precision workstations selling for peanuts. The models I was looking at were the T3500 and T5500, but I'm not sure if ESXi would install on either of those boxes. (I almost got one with a Xeon W3520, but researched that Xeon and found that it does not support VT-d.)
So I'm on a shoestring budget and can't afford a real server, but I might be able to swing one of these old workstations. A second option that occurred to me would be to upgrade the triple core processor in the Dell Inspiron 570 to an Athlon/Phenom quad CPU. However, the Xeon would have 4 actual cores plus 4 logical cores thanks to hyperthreading. And if I really wanted to, I could upgrade to a six-core/12 thread Xeon like the L5640.
Comments welcome...
hi there,
I'm trying to get a usb disk connected to a VM on an ESXi 5.0 server in a remote office.
I'm told by staff in the office that the drive is plugged into the ESXi server, yet when I try to add it to a VM it says no devices available.
Is there a way I can check that the ESXi host itself is detecting the drive? A shell command perhaps?
Thanks for any assistance.
-Al
I need to restart the Management agents on an ESXi 5.5 server member of a vSphere 5.5 infrastructure.
The procedure I am considering is described on page Restarting the Management agents on an ESXi or ESX host (1003490) | VMware KB .
Can I safely issue the suggested commands:
/etc/init.d/hostd restart
/etc/init.d/vpxa restart
on a production server without creatibng any problem to running VMs?
Is there anything else I should consider before issuiong the commands?
Regards
Marius
Dear Community,
as per specs, APC PCNS only works up to VS 5.5. Has anyone tried it with VS 6? Or is there any other way to gracefully shutdown an ESXi 6 Host through an UPS?
Thank you an best regards,
Jens Graven
Hello All, Good Day to you!
In my customer environment, we have a 100GB LUN specified solely for swapping. However it is now full, with only 322 MB remaining - and right now it doesn't allow any host vMotion saying that there isn't enough free space. When I browse the relevant data store I can see a lot of .vswp files ans some .swp files ( I am attching the data store ). As far as I know a VM seperates out for itself a capacity equal to it's guest memory size on the swap space. What would be the best way to figure out which .vswp files are not required, and which are ? I can easily expand this LUN on the VNX, but would that be god administering - anyways on the LUN properties, I can see that it is only using 4+% - How does that figure with what is told me in the VMware front ( I would be asking this in an EMC forum seperately ) ?
Basically is there any adminstration guide with regards to virtual memory usage in VMware ? Or should I simply expand the LUN and add the expanded capacity on the VMware side ? What is the difference between vmx-XXXX.vswp, XXXX.vswp and sysswp-xyz.swp , where XXXX presents VMname ?
Regards,
Naleendra
I've upgrade to Esxi 5.5 already and created a vmdk to 4.7 Tb and would like to expand it to 5.6 Tb. I get the following error message when I attempt to expand it and I don't know why or how to bypass it: Hot-extend was invoked with size (12025908428 sectors) >= 2TB. Hot-extend beyond or equal to 2TB is not supported.
I have a cluster of 15 ESXi 5.0 hosts, with a 5.1 vCenter / Enterprise Plus license. This has been running well for quite some time, but two of my hosts were disconnected tonight and I am troubleshooting it now.
When I go to reconnect them, I get an error saying that "A general system error has occured: Timed waiting for vpxa to start". I did some searching and found that this was generally related to snapshots, but none of the VMs on either of my un-connectable hosts have any snapshots at all.
I've tried:
- Restarting vCenter services
- Rebooting vCenter
- Restarting services on the hosts
- Warm reboot of hosts
- Hard/cold reboot of hosts
- Powering off all VMs on hosts and entering maintenance mode
- DNS is working between hosts and vCenter, and vice versa
- Time is correct on vCenter and hosts
- Network connectivity is good between vCenter and hosts (all on the same switch)
However nothing seems to work, and I still can't add these hosts back to my cluster. What's odd is that I can connect to them directly with vSphere, but I just can't get them back into my vCenter. I get through the usual prompts when adding it (where it asks you to assign a license, etc) and it sees the VMs on the host as I'm adding it, but times out with this error after about 5 minutes.
Any insight would be very much appreciated.
Dear All,
I would like to understand about maintenance mode, for example I've two hosts in a cluster and I need to perform firmware upgrade on Host A. Now before I do that I must migrate the virtual machine to Host B, So now Host A is free. Now I can right away turn off the Host A and start firmware upgrade procedure OR first I should say for this host to enter maintenance mode and then turn off ?
Second I want to have clear understanding of standby mode ? Can I also put a host in Standby mode for firmware upgrade or other maintenance activities ?
thanks,
I have a VMware cluster running on a blade server and all but one of the HOSTS report this error Alert Host IPMI System Event Log status. I did a Google search and came up with this fix VMware KB: The Host IPMI System Event Log Status alarm is triggered repeatedly in VMware vCenter Server 4.x and 5.x … In step 4 i get this The system event log is empty. Any help with this would be great.
To resolve this issue, stop the alarm from triggering repeatedly and clear the IPMI System Event log and reset the sensors.
To clear the log and reset the sensors:
I just installed VMware ESXi 5.5 Free Edition on a Dell server, when I open up VMware vSphere Client it says the following:
"In vSphere 5.5, all new vSphere features are available only through the vSphere Web Client. The traditional vSphere Client will continue to operate, supporting the same feature set as vSphere 5.0, but not exposing any of the new features in vSphere 5.5.
The vSphere Client is still used for the vSphere Update Manager (VLM) and Host Client, along with a few solutions (eg. Site Recovery Manager)."
Where do I download vSphere Web Client?
Thanks
I've tried every suggestion out there, and still can't remove one datastore in my vCenter.
(I've not been able to reboot the hosts, or even put them in maintnenace - that's not an option at the moment).
2 -
I've done the following:
- migrated all VM's.
- checked all vmx files for references to the datastore
- found 2 VM's not in inventory or powered on, which referenced the datastore - changed those
- deleted the .dvsData folder from the datastore
- Not used for HA (the 2 hosts are not in a cluster)
- made sure I/O Control is disabled on all hosts
- even followed this: VMware Front Experience: How to disable Storage I/O Control for an unavailable datastore
- no snapshots exist on any of the vm's that *were* on this datastore
- also checked for orphaned *-00000x.vmdk on migrated vm's - none exist
- unmounted the datastore
- this works from one host, but not the other.
- unmounting from host1 gives the red "X" on "no virtual machines exist (all others are green)
- unmounting from host2 unmounts the datastore on host2 but it still shows as mounted on host1
- deleting the datastore (whether mounted or not) fails with the "resource in use" error
Hello all,
I have an issue with 1 FC LUN that can be seen as a device through multiple paths on all 10 hosts in a cluster but it only appear as a VMFS datastore on 6 of the hosts. Other LUNs from the same array appear fine on all hosts. All 10 hosts see the LUN with the same LUN ID and all hosts are identical with respect to ESXi version (5.0 Update 2), HBA models and firmware.
On the 4 hosts that can see the device but not the VMFS datastore it appears that it sees the LUN as a snapshot: "esxcli storage vmfs snapshot list" results in:
4f5e5cbb-a87cd2c6-86e9-d8d385f98034
Volume Name: LUN101_SAS2
VMFS UUID: 4f5e5cbb-a87cd2c6-86e9-d8d385f98034
Can mount: true
Reason for un-mountability:
Can resignature: false
Reason for non-resignaturability: the volume is being actively used
Unresolved Extent Count: 1
The above VMFS UUID matches the VMFS UUID seen on the 6 hosts that can see the VMFS datastore.
When I try to use "Add Storage", the device appears with a VMFS Label of: LUN101_SAS2(head). I'm not sure why (head) has been appended to the VMFS label. On the following screen the "Keep existing signature" and "Assign a new signature" options are greyed out. The only option is "Format the disk". I need to keep the existing signature as there are running VMs that have their .vmx and .vmdk files on this LUN.
Would the fact that I have running VMs on this LUN be preventing me from choosing the "Keep existing signature" option?
Will I need to Storage vMotion these VMs to another LUN before I can add the VMFS datastore to the 4 hosts?
TIA