The KB is wrong!
This is not a cosmetic issue! We are not able to set the preferred patch from the client, webclient or even PowerCLI!
We've created an SR (17504104407) but get no response from vmware other than it will be patched in the future.
We need this fixed ASAP!
hello,
I have around 2-4TB drives available with each of mine 4 nodes. We bought it for vsan but that project never finish because of vsan price and some other problems.
is there any free software available in the market with the similar capabilities as vsan or any other idea i can build that local storage as a shared storage.
Regards
Hello, see if any details on the link ghettoVCB.sh - Free alternative for backing up VM's for ESX(i) 3.5, 4.x & 5.x helps
Hello,
My problem goes like this, i've installed ESXi 6.0.0 to a server, created my virtual servers and everything is working fine.
I wanted to login to esxi today via vsphere client but gotten an error stating invalid username / password.
I went and logged to the server via ipmi / ilo and was able to login just fine, when i restart management agents for a short period of time, i can login with vsphere client again.
But after a while, vsphere cliend, vcenter or ssh starts to reject my password again. And the only way to fix the issue (temporarily) seems to be restarting the management agents.
Has anyone experienced this?
I cannot reinstall the server because my customers are already using their virtual servers so i must come up with a solution, loggin' to ipmi and restarting management agents every single time i need to check or do something is wasting a lot of time.
Thanks in advance
Here is the output :
~ # partedUtil getptbl /vmfs/devices/disks/naa.6000eb32f4b70e830000000000000862
gpt
2272469 255 63 36507222016
1 2048 36507221982 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
Check if its due to a firewall
Try FreeNAS, a Opensource Stroage OS with lots of features and plugins. Well supported by ESXi and can be usable for shared block storage. Supports both NFS and iSCSI protocol.
Hello,
My backup script was created based on the link you indicated. Even following the references of Cron Job, I am still in difficulties.
Anyone have any tips?
Save, edit and run the below PS script to rename Windows VM without restart:
$ComputerName = "New Name"
Remove-ItemProperty -path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -name "Hostname"
Remove-ItemProperty -path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -name "NV Hostname"
New-PSDrive -name HKU -PSProvider "Registry" -Root "HKEY_USERS"
Set-ItemProperty -path "HKLM:\SYSTEM\CurrentControlSet\Control\Computername\Computername" -name "Computername" -value $ComputerName
Set-ItemProperty -path "HKLM:\SYSTEM\CurrentControlSet\Control\Computername\ActiveComputername" -name "Computername" -value $ComputerName
Set-ItemProperty -path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -name "Hostname" -value $ComputerName
Set-ItemProperty -path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -name "NV Hostname" -value $ComputerName
Set-ItemProperty -path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" -name "AltDefaultDomainName" -value $ComputerName
Set-ItemProperty -path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" -name "DefaultDomainName" -value $ComputerName
You can edit and use the below bash script for a Linux VM (Ubuntu in this example):
#!/usr/bin/env bash
NEW_HOSTNAME=$1
echo $NEW_HOSTNAME >/proc/sys/kernel/hostname
sed -i 's/127.0.1.1.*/127.0.1.1\t'"$NEW_HOSTNAME"'/g'/etc/hosts
echo $NEW_HOSTNAME >/etc/hostname
service hostname start
su $SUDO_USER -c "xauth add $(xauth list | sed 's/^.*\//'"$NEW_HOSTNAME"'\//g' | awk 'NR==1 {sub($1,"\"&\""); print}')"
Hi
In production datastore running out of space. I found folder as patch (Name:update-from-esxi6.0-6.0_update01.zip size:688,024,90kb path:[Datastore]patch Modified:9/28/2015. Would be safe to delete that to gain some space without any issue.
Thank you
This is a different LUN and not what you reported previously. Can you share the vmkernel.log snippet for this LUN one which is similar to this.
2017-08-02T13:31:42.103Z cpu4:34284)LVM: 2908: [naa.6000eb32f4b70e830000000000000849:1] Device expanded (actual size 42949670879 blocks, stored size 34360260575 blocks)
Best Regards,
Deepak Koshal
Yes, this is an offline bundle which can be used to update/patch an ESXi host. It's only required at the time wen you run the update/patches.
André
so its safe to delete? if yes what's the best way to delete it?
Thank you
Hey!
i have the same issue and tested all the suggestions...
Any update?
UPDATE:
I've solution!
1) Install the locker vib manually:
cd /tmp
esxcli software vib install -f -v /tmp/VMware_locker_tools-light_6.5.0-0.23.5969300.vib
2)
Update:
esxcli software profile update -f -p ESXi-6.5.0-20170702001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-
depot-index.xml
Reboot and youre done :-)
Hello,
Just browse the datastore and right click on file and "Delete from datastore". if you are not sure about importance of file then you can also move it to another datastore.
Regards,
Rahul
The anser is.... you have to contact customer services who in my case were happy to provide free licence within 10 minutes. They said you can't get it in any other way nowadays.
Thank you for your reply.
Rolled this out to 6 more host and it fixed every one of them.
I've been tasked with getting official recommendations for how to handle our specific circumstances, and I have not been able to find anything. VMWare tech support has been near silent in the ticket I submitted, instead choosing to forward responsibility on to licensing support. Our reseller hasn't given me any decent response, or even a price quote relating to what we need. Google searches have brought up best practices guides, but they just seem to be more marketing materials than anything useful.
So, here's the situation:
We have a 2 machine cluster with vSphere Essentials Plus 5.5. Currently each host only has local storage, and yet my predecessor set them up in a cluster. Since it couldn't do any failover in case one host failed, we are (finally) getting some centralized storage soon. Even with this, we don't have enough memory on one host to keep all the VMs at maximum, and we have some VMs that are absolutely necessary to keep at 100%. Some will have memory swapped out. There is no way around that. So, my boss had me give some recommendations and asked for the official best practices for such things.
Here is what I have:
Option 1 (my main recommendation): Get more memory so we can get all the VMs up on one host. We would need 256GB of memory on each host.
Option 2 (my backup position): Set memory reservations on the most important VMs to make sure they get what they need. Also, set CPU shares to high on those same VMs.
Option 3 (my boss's suggestion): Use DRS and resource pools to automate the resource reservations for the high priority VMs. Of course, this requires upgrading to vCenter Standard and vSphere Enterprise Plus, and that is expensive. I asked CDW for a quote, only to have the sales guy hook me up with their VMWare specialist to tell me it will be a big cost, and then not send me a quote. So, I can't give my boss any feedback on this one. (Really annoying in that it would cost us $3000 to get the memory, and about $17,000 for the E+ licenses, but he wouldn't listen to me.)
I can find no documentation to back up any of these positions, and my boss wants it. Advice?