Hi Vmware Support,
I have installed Windows Server 2012 on Vmware and And also have installed Windows 7 on VMware, after configuring DHCP service on server 2012 i keep my client Ethernet properties on DHCP but it's not getting IP from my DHCP server getting APIPA IP. please help me how can i configure my network connection on VMware so that i can get IP from DHCP server.
Thank you.
Hello,
I'm trying to fix an issue where my root ramdisk / Scatch/logs fills up after a few hows of uptime and esxi can no longer write to its log files.
Unfortunately the only datastore I have is the vsan datastore, and redirecting system logs to that datastore is not supported. I do have vsphere log insight setup but the local path is still {} /scratch/log
I have 3 servers in the vsan, but one of them fills up the root ramdisk much faster than the others. This is an Lenovo server whereas the others are HPE servers.
After spending a fair bit of time looking into this, trying to see if the IBM has a higher logging level than the others etc but I can't see why the Lenovo's logs grow so fast.
Here's what the logs currently look like:
root@MOX-ESXi1:/scratch/log] ls -lah -lS
total 29880
-rw------- 1 root root 10.0M Mar 15 14:54 vsanmgmt.log
-rw------- 1 root root 7.6M Mar 15 18:28 hostd.log
-rw------- 1 root root 3.1M Mar 15 18:29 vsanvpd.log
-rw------- 1 root root 1.9M Mar 15 18:30 vpxa.log
-rw------- 1 root root 1.6M Mar 15 18:34 vsansystem.log
-rw------- 1 root root 943.9K Mar 15 18:29 syslog.log
-rw------- 1 root root 875.4K Mar 15 18:31 osfsd.log
-rw------- 1 root root 744.3K Mar 15 18:28 rhttpproxy.log
-rw------- 1 root root 651.6K Mar 15 17:58 cmmdsTimeMachineDump.log
-rw------- 1 root root 650.4K Mar 15 18:32 vmkernel.log
-rw------- 1 root root 312.0K Mar 15 18:17 fdm.log
-rw------- 1 root root 211.5K Mar 15 18:35 hostd-probe.log
-rw------- 1 root root 172.0K Mar 15 18:40 clomd.log
And here;s the ramdisks:
Ramdisk Size Used Available Use% Mounted on
root 32M 32M 0B 100% --
etc 28M 396K 27M 1% --
opt 32M 0B 32M 0% --
var 48M 816K 47M 1% --
tmp 256M 72K 255M 0% --
iofilters 32M 0B 32M 0% --
hostdstats 803M 4M 798M 0% --
vsantraces 300M 153M 146M 51% --
The largest log file is vsanmgmt.log.
[root@MOX-ESXi1:/scratch/log] tail -f vsanmgmt.log
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] Profiler:
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] VsanHealthHelpers.IsWitnessNode: 0.00s
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] LsomHealth.getHealthStats(): 0.05s
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] plog devices: 0.00s, 0.00s
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] get disks: 0.03s
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] QueryPhysicalHealth.loopfor allVsanDisks: 0.09s
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] impl.QueryDiskRebalanceStatus: 0.00s, 0.00s, 0.00s, 0.00s, 0.00s, 0.00s, 0.00s
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] impl._QueryPhysicalDiskHealthSummary: 0.14s
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] maxComps: 0.00s
2018-03-15T14:53:37Z VSANMGMTSVC: WARNING vsanperfsvc[Thread-2] [VsanHealthUtil::log] QueryPhysicalHealth.GetLocalVsanSystem: 0.01s
If I compare this to one of the HP servers who's logs are tiny in comparison, the output is basically the same:
[root@MOX-ESXi2:/tmp/scratch/log] tail vsanmgmt.log
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] cls.ManipulateControllersWithStressOptions: 0.00s
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] cls._LookupDriverVersion: 0.00s, 0.00s, 0.00s, 0.00s
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] cls._LookupControllerQueueDepth: 0.00s, 0.00s, 0.00s, 0.00s
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] Get storage-core-path, core-adapter, hardware-pci, system-version: 0.03s
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] cls.checkDiskMode: 0.00s, 0.00s, 0.00s, 0.00s
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] Profiler:
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] GetHclInfo.ConnectToLocalHosted: 0.01s
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] impl.GetHclInfo: 1.19s
2018-03-15T18:54:19Z VSANMGMTSVC: WARNING vsanperfsvc[43fc0038-2882-11e8] [VsanHealthUtil::log] invoke-method:ServiceInstance:RetrieveContent: 0.01s
2018-03-15T18:54:19Z VSANMGMTSVC: INFO vsanperfsvc[Thread-12] [PyVmomiServer::log_message] ('127.0.0.1', 45342) - - "POST /vsan HTTP/1.1" 200 -
Any ideas??
Hi there,
I have a newly deployed vCloud Director 9.1. All seems to be fine, but I cannot enter into the console with FQDN (like https://vcloud.mycompany.local) but works ok using the IP (https://10.1.0.100).
Could someone point me in the right direction?
Thanks a lot
Dear all,
I have two HPE ML350 Gen9 Server running with ESXi 6.5U1 Build 7388607 HPE Custom Image.
Latest BIOS-Update P92 2.56_01-22-2018 23.02.2018 is installed.
All running Windows 2012 R2 VMs got the latest Microsoft updates (including KB4056098). Antivirus software is also running and up-to-date.
The registry-keys were set, as mentioned in: https://support.microsoft.com/en-za/help/4072698/windows-server-guidance-to-protect-against-the-speculative-execution
If I run the the Microsoft "SpeculationControl"-Powershell-script, I get as result, that the CPU still have to be updated by microcode (please see attachment).
Does anybody know which additional vmWare-Update I need to install?
Thanks in advance for your assistance!
Regards
Marcus
Any ETA for VMware vRealize Log Insight 4.6 release?
I would like to share my recent experience when troubleshooting a HA issue.Be default when trying adding a new host to the existing cluster or when you reconfigure a HA on one of the existing host in the cluster HA opearing will timeout.To fix the issue eithwe we have to disable and enable the Ha on the cluster level or reconfigure HA on the master node
vpxd logs
vpxd-19.log:2017-09-26T01:17:53.673Z info vpxd[7FA6DC311700] [Originator@6876 sub=vpxLro opID=lro-53-79f246b8-02] [VpxLRO] -- BEGIN task-147951 -- svrau-esx03.jbhi-fi.local -- DasConfig.ConfigureHost --
vpxd-19.log:2017-09-26T01:17:53.673Z info vpxd[7FA6DC311700] [Originator@6876 sub=MoHost opID=lro-53-79f246b8-02] [HostMo::UpdateDasState] VC state for host host-220 (initialized -> uninitialized), FDM state (Live -> Live), src of state (null -> null)
vpxd-19.log:2017-09-26T01:17:53.965Z info vpxd[7FA6DC311700] [Originator@6876 sub=DAS opID=lro-53-79f246b8-02] [VpxdDasConfigLRO::ConfigureResources] Skipping aam RP config for ESX 6+ host
vpxd-19.log:2017-09-26T01:17:54.389Z info vpxd[7FA6DC311700] [Originator@6876 sub=HostUpgrader opID=lro-53-79f246b8-02] [VpxdHostUpgrader] Fdm on host-220 has build 5973321. Expected build is 6671409 - will upgrade
vpxd-19.log:2017-09-26T01:17:54.578Z info vpxd[7FA6DC311700] [Originator@6876 sub=HostAccess opID=lro-53-79f246b8-02] Using vpxapi.version.version11 to communicate with vpxa at host svrau-esx03.jbhi-fi.local
vpxd-19.log:2017-09-26T01:21:41.970Z warning vpxd[7FA6DC698700] [Originator@6876 sub=VpxProfiler opID=lro-53-79f246b8-02-TaskLoop-dc7c952] TaskLoop [TotalTime] took 222225 ms
vpxd-19.log:2017-09-26T01:21:42.104Z info vpxd[7FA6DC311700] [Originator@6876 sub=DAS opID=lro-53-79f246b8-02] [VpxdDasConfig::PushConfigToFDM] pushed config version 127 to host [vim.HostSystem:host-220,svrau-esx03.jbhi-fi.local] (cluster [vim.ClusterComputeResource:domain-c31,AU001_CLUSTER_GENERAL])
vpxd-19.log:2017-09-26T01:23:42.120Z error vpxd[7FA6DC311700] [Originator@6876 sub=DAS opID=lro-53-79f246b8-02] Timed out waiting for election to complete or for host to join existing master
vpxd-19.log:2017-09-26T01:23:42.120Z error vpxd[7FA6DC311700] [Originator@6876 sub=DAS opID=lro-53-79f246b8-02] EnableDAS failed on host [vim.HostSystem:host-220,svrau-esx03.jbhi-fi.local]: N3Vim5Fault8Timedout9ExceptionE(vim.fault.Timedout)
vpxd-19.log:2017-09-26T01:23:42.121Z info vpxd[7FA6DC311700] [Originator@6876 sub=MoHost opID=lro-53-79f246b8-02] [HostMo::UpdateDasState] VC state for host host-220 (initialized -> init error), FDM state (UNKNOWN_FDM_HSTATE -> UNKNOWN_FDM_HSTATE), src of state (null -> null)
vpxd-19.log:2017-09-26T01:23:42.184Z info vpxd[7FA6DC311700] [Originator@6876 sub=DAS opID=lro-53-79f246b8-02] [VpxdDasConfigLRO::Cleanup] Number of unprotected vms: 24
vpxd-19.log:2017-09-26T01:23:42.184Z warning vpxd[7FA6DC311700] [Originator@6876 sub=VpxProfiler opID=lro-53-79f246b8-02] VpxLro::LroMain [TotalTime] took 348510 ms
vpxd-19.log:2017-09-26T01:23:42.184Z info vpxd[7FA6DC311700] [Originator@6876 sub=vpxLro opID=lro-53-79f246b8-02] [VpxLRO] -- FINISH task-147951
vpxd-19.log:2017-09-26T01:23:42.184Z info vpxd[7FA6DC311700] [Originator@6876 sub=Default opID=lro-53-79f246b8-02] [VpxLRO] -- ERROR task-147951 -- svrau-esx03.jbhi-fi.local -- DasConfig.ConfigureHost: vim.fault.Timedout:
vpxd-19.log:2017-09-26T01:24:15.373Z warning vpxd[7FA6DE17B700] [Originator@6876 sub=VpxProfiler opID=lro-53-79f246b8-02-EventManagerProcessJobs-4606457a] EventManagerProcessJobs [TotalTime] took 33248 ms
From the above snippets it is evident that HA configuration is timing because of under lying network latency between the esxi hosts.This issue can be fixed by increasing the default timed out value for FDM in the Vcenter server advanced settings
Applying a VMware HA customization
Using the vSphere Web Client
Log in to VMware vSphere Web Client.
Go to Home > vCenter > Clusters.
Under Object, click on the cluster you want to modify.
Click Manage.
Click vSphere HA.
Click Edit.
Click Advanced Options.
Click Add and enter in Option add config.vpxd.das.fdmWaitForUpdatesTimeoutSec and Value field set it t0 60
Deselect Turn ON vSphere HA.
Click OK.
Wait for HA to unconfigure, click Edit and check Turn ON vSphere HA.
Click OK and wait for the cluster to reconfigure.
Hallo,
Code:
$vm=get-vm -Name 'testmas-v304'
$vm.PowerState
$size=60
Get-HardDisk -VM testmas-v304 -Name "Hard disk 1"
get-vm -Name 'testmas-v304' | Get-HardDisk -Name "Hard disk 1" | Set-HardDisk -CapacityGB 65.2 -Confirm:$false -Verbose
Get-HardDisk -VM testmas-v304 -Name "Hard disk 1"
-->Outputput:
Connected to..
vc-v003
KT\Smarty
PoweredOff
CapacityGB Persistence Filename
---------- ----------- --------
60.100 Persistent ...od_nfs_win2_28d] testmas-v304/testmas-v304.vmdk
AUSFÜHRLICH: 14.03.2018 15:29:39 Set-HardDisk Started execution
AUSFÜHRLICH: Ausführen des Vorgangs "Setting CapacityGB: 65.19999980926513671875." für das Ziel "Hard disk 1".
AUSFÜHRLICH: 14.03.2018 15:29:39 Set-HardDisk Finished execution
Set-HardDisk : 14.03.2018 15:29:40 Set-HardDisk Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
In \\kt.lunet.ch\shares\Powershell-Include\Server\Maintenance\vm-osLWresize.ps1:28 Zeichen:69
+ ... rd disk 1" | Set-HardDisk -CapacityGB 65.2 -Confirm:$false -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-HardDisk], ViError
+ FullyQualifiedErrorId : Client20_ClientSideTaskImpl_ThreadProc_UnhandledException,VMware.VimAutomation.ViCore.Cmdlets.Commands.VirtualDevice.SetHardDisk
60.100 Persistent ...od_nfs_win2_28d] testmas-v304/testmas-v304.vmdk
Kennt jemand diesen Fehler?
When you open WebSphereClient
The following error has occurred.
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE: 0x00007f12dc031ff0] _serverNamespace = / action = Allow _pipeName = / var / run / vmware / vpxd-webserver-pipe)
It will not stop even if you restart vCenter.
vpxd is not running
I can not see vCenter even if I start up manually and log in WevSphereClient.
root @ TM - VC [~] # service - control - status
Running:
applmgmt lwsmd vmafdd vmonapi vmware - cm vmware - content - library vmware - eam vmware - perfcharts vmware - rhttpproxy vmware - sca vmware - sps vmware - statsmonitor vmware - updatemgr vmware - vapi - endpoint vmware - vmon vmware - vpostgres vmware - vpxd - svcs vmware - vsan - health vmware - vsm vsphere - client vsphere - ui
Stopped:
vmcam vmware - imagebuilder vmware - mbcs vmware - netdumper vmware - rbd - watchdog vmware - vcha vmware - vpxd
vCenter Version
If there is any way of carving
please tell me.
Hello everybody,
Unfortunately, I currently have the problem that I can not log in directly to the vCenter Server Appliance (VM) through the vSphere Web Client.
Have already changed the root password in the appliance via the Grub menu, but I can then log in the completely booted system not synonymous.
SSH login is always reported as wrong.
Does anyone have any idea or solution?
I'm looking to automate the process of changing the default snapshot in a floating pool. I've inserted a picture to hopefully better explain the image/snap I'm talking about:
I'm not too familiar with Power Shell or PowerCLI and would like to turn this into a learning experience. If there isn't any specific way you know of I'm also interested in sites that would be useful for someone wanting to start scripting in View.
As per the subject, I am looking for a PowerCLI script that can run through all of the VMs in vSphere and list those that do not have the Sync VM Clock to Host option. I am having issues trying to determine how to target that option.
Do I've been studying for a while now and i'm ready to take this exam so I can finally get my VCIX cert ( I Currently hold the VCAP5-DCD ). Now I find out that this exam is no longer being offered
The frustrating thing is that my VCP will be expiring in a couple months so I don't have time to wait for the newer 6.5 version of this exam to be released!
ESXi is reporting 8GiB used, however top is showing about 3.2ish GiB used.
Hi All,
Has anyone implemented standard vSAN setup with Dell vSAN ready node on 1GB network. If yes, can anyone provide the Dell Part number for storage part i.e RAID controller, Boot device, caching and capacity tier. Sorry, Have not worked on Dell before and getting online BoM is not easy for Dell compare to CISCO.
Regards,
Get-VM doesn't show actual VMs in cluster. Web Client clearly shows 89 VMs powered up and running.
VM count is off. Correct number is 89 VMs in this cluster. Causes issues on performance reports as only subset is used for calculations.
Two resource groups, but subset contains VMs from both (just not all).
Checked PS, .Net, PwrCli versions
Tried this on several servers/workstations.
PS C:\> get-cluster clustername | get-vm | measure
get-vm : 3/15/2018 7:14:39 AM Get-VM Exception has been thrown by the target of an invocation.
At line:1 char:23
+ get-cluster clustername | get-vm | measure
+ ~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-VM], VimException
+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetVM
Count : 47
Average :
Sum :
Maximum :
Minimum :
Property :
PowerCLI Version
----------------
VMware PowerCLI 6.5 Release 1 build 4624819
---------------
Component Versions
---------------
VMware Cis Core PowerCLI Component 6.5 build 4624453
VMware VimAutomation Core PowerCLI Component 6.5 build 4624450
VMWare ImageBuilder PowerCLI Component 6.5 build 4561891
VMWare AutoDeploy PowerCLI Component 6.5 build 4561891
VMware Vds PowerCLI Component 6.5 build 4624695
VMware Cloud PowerCLI Component 6.5 build 4624821
VMware HA PowerCLI Component 6.0 build 4525225
VMware HorizonView PowerCLI Component 7.0.2 build 4596620
VMware Licensing PowerCLI Component 6.5 build 4624822
VMware PCloud PowerCLI Component 6.5 build 4624825
VMware Storage PowerCLI Component 6.5 build 4624820
VMware vROps PowerCLI Component 6.5 build 4624824
VMware vSphere Update Manager PowerCLI 6.5 build 4540462
PS C:\> $psversiontable
Name Value
---- -----
PSVersion 5.1.14409.1012
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14409.1012
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
PS C:\> Get-ChildItem "HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\" | Get-ItemPropertyValue -Name Release
460805
I contacted support and they informed me that I cannot migrate my virtual distributed switches to version 6.5 but that i would have to change them to standard switches, migrate to 6.5 and then change them back to virtual distributed switches. Any one else have to go through that process? I would be curious to know the ups and downs of this process, with my environment it looks pretty ugly.
Any help that gets me logged into a vcenter server with powercli 10 is much appreciated!
I continue to get this error when trying to connect to my vcenter server.
In most cases we deploy a single VM per deployment and in that scenario you can run the destroy action on either the VM or the deployment successfully. But in cases where multiple VMs are part of a single deployment there doesn't appear to be a way to destroy just a single VM in that deployment. In multi-VM deployments it seems like the destroy action is no available for individual items. Am I missing something or is there no way to destroy one VM in a deployment?
Horizon 7.1, App Volumes 2.13.1, RDS Windows Server 2012 R2
I have multiple RDS Farms in View Pod, some of which are showing status of various applications "The application is missing on all RDS hosts". Applications are provisioned using App Volumes, computer-based assignments. Although View Admin shows the applications as missing, I am able to launch them.
Of 7 RDS farms, currently 4 having the issue. When running a Application Pool discovery, only a subset of applications are discovered.
If I manually add the application on a Farm/RDS hosts having the issue, pointing directly to the .exe, it is added successfully to View. So seems View is having problems reading information on the shortcuts/.lnks when searching C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\ and C:\ProgramData\Microsoft\Windows\Start Menu\.
In RDS View Agent log, I see this for example -
2018-03-07T07:19:13.593-07:00 INFO (02D0-1AE0) <MessageFrameWorkDispatch> [ws_applaunchmgr] Scanning "C:\ProgramData\Microsoft\Windows\Start Menu\Programs", depth = 1
2018-03-07T07:19:13.593-07:00 INFO (02D0-1AE0) <MessageFrameWorkDispatch> [ws_applaunchmgr] Creating Shortcut from "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Access 2016.lnk"
2018-03-07T07:19:13.593-07:00 INFO (02D0-1AE0) <MessageFrameWorkDispatch> [ws_applaunchmgr] Resolving shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Access 2016.lnk"
2018-03-07T07:19:13.593-07:00 WARN (02D0-1AE0) <MessageFrameWorkDispatch> [ws_applaunchmgr] "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Access 2016.lnk": target unresolvable
2018-03-07T07:19:13.593-07:00 INFO (02D0-1AE0) <MessageFrameWorkDispatch> [ws_applaunchmgr] "Access 2016.lnk": invalid Application
The shortcut points to "C:\Program Files (x86)\Microsoft Office\root\Office16\MSACCESS.EXE", which is valid. I can run the .exe successfully.
Any ideas?
Thanks,
Lyle
What is the difference between mounting Apple's USB super-drive as a "CD virtual drive" and mounting as as "USB", when they both do the same ?
I'm guessing under "CD" case the Apple driver still needs to be installed in VM, but all i can see is if mounted as a CD ROM, You only get drive "D:" were as if you mounted via "USB" in Fusion u get (D:) and (E:)
Mounting this way can cause issues with certain software, like UltraISO, which the "Make CD/DVD wizard" only recognizes drive D: only even though both appear in the bottom half of the pane..
Probably just a software glitch of the developer, but is there any real differences in Fusion as to the different ways this is mounted?
