New answers tagged vmware-vsphere
I fixed it this way: DCUI: Connect to the console of your ESXi host. Press F2 to customize the system. Log in as root. Use the Up/Down arrows to navigate to Restart Management Agents. Note: In ESXi 4.1 and ESXi 5.x, this option is available under Troubleshooting Options. Press Enter. Press F11 to restart the services. When the service has been ...
This seems to be a vsphere artifact of some kind. When I first went to do this, and reported issue above, the VM was running, and this GUI element is locked, by design. Later, after shutting off the VM, the edit was still locked. Today, the VM had been shut down for some time, and I went to edit the VM, and now the setting IS editable.
Check to see if all the snapshots have been removed. I don't think you can resize the disk if there are snapshots.
What you want is not completely possible. Regarding the keyboard and the mouse you have these options: If you have VMware tools installed and an X-session is running the console will grab the mouse and the keyboard as soon as the mouse hovers over the console. If you don't have an X-session running you will have to click into the console, regardless if ...
That's the normal status for open-vm-tools. Only the original VMware tools show the full status. As long as it doesn't say "no VMware tools running" everything is fine. You only need the open-vm-tools-desktop package for systems with a graphical desktop, so you are fine there too. I never installed anything but the basic package on a virtual server.
Snapshots on Netapp take space based on how many blocks have changed since they were created. That can get high with time. You can safely delete any snapshot that's not in a locked state (for things like snapmirror) and that will clear up space for you. You can also configure snap autodelete to prevent the snapshots from exceeding the reserve. Snap show ...
For me, the below command sequence has worked as expected. I have done modifications in /etc/udev/rules.d/70-persistent-net.rules to change the eth number and to reload them without rebooting. /etc/init.d/networking stop /etc/init.d/udev stop udevadm control --reload-rules /etc/init.d/udev start /etc/init.d/networking start Following this, it ...
vSphere snapshots and NetApp snapshots are very different things - as for your answer, you need someone who knows how to manage NetApps to look at your snap schedule, the current snap space being used and configure them more for your needs - it sounds like this person really isn't you.
If you want to use Python maybe pyVmomi can help you. If it's lacking the functionality you need you can always use the SOAP based API directly. And have a look at the VMware Developer Center / VMware Sample Exchange, maybe you can find some interesting things there.
Before you read it, do note that this feature was intended for VMware Support. While it is internally supported, you’d be using it at your own risk, and consider this write-up to be purely for educational purposes. Support for this feature, and exposure through the UI, may or may not change in the future. I have memory pages swapped, can vSphere unswap ...
An old config from a vcenter agent must still be there in the esxi, as please see the fact there : Required ports for VMware vCenter Server 5.5 (2051575) 902 TCP/UDP This is the default port used by the vCenter Server system to send data to managed hosts. Managed hosts also send a regular heartbeat over UDP port 902 to the vCenter Server ...
You are not lackng anything with open-vm-tools and will potentially avoid issues when doing kernel upgrades by upgrading open-vm-tools at the same time. vCenter should see open-vm-tools once they are running. Have you check to make sure the service is running after installation? systemctl status -l open-vm-tools if not running start and enable it `...
Ballooning uses a kernel module (installed as part of VMware Tools) to allocate the memory in the guest. So, it is the Linux kernel that consumes the memory, but not one of the regular processes that top would show.
Use the VMware OSP versions of the tools or open-vm-tools for newer distributions. In both cases, they can be deployed via your yum/apt package manager and could easily integrate into your installation workflow.
Top 50 recent answers are included