vmjoe's Posts

LWCSteve‌ Thanks for the solution! Works for me on 2012 R2 server with vCenter 6.5 (build 4602587). I didn't use group policy - we have a group on the server where I had to add all the local ... See more...
LWCSteve‌ Thanks for the solution! Works for me on 2012 R2 server with vCenter 6.5 (build 4602587). I didn't use group policy - we have a group on the server where I had to add all the local users created by vCenter installation. It's a shame that VMware is creating such rubbish... and from the error message in the browser it's impossible to even get a clue what's the problem.
I can confirm, a second network card causes this error. (vCenter is on W2K8 as domain member) Disabling the second network card (in Windows) and re-run the installer worked.
I experienced the same phenomenon (without the VM being migrated before) on ESXi 5.1/vCenter 5.1 enivronment. The VM seems to be suddenly powered on, and the only thing the task and event logs re... See more...
I experienced the same phenomenon (without the VM being migrated before) on ESXi 5.1/vCenter 5.1 enivronment. The VM seems to be suddenly powered on, and the only thing the task and event logs reveal is, that "DRS powered On" the VM. The task itself is "Initiated by System", the "related events" do NOT show a task by a user (could be considered a bug). On datacenter level, select "Show datacenter entries" instead of "Show all entries" and search for the same date and time. There should be a task "Initialize powering On" initiated by the actual user. There's no reference to the VM, the target is the datacenter. So the only correlation is the time stamp! Make sure the list size in vSphere client is set to the maximum: Edit -> Client Settings -> Lists -> Page size: 1000 (the maximum).
The VM is configured as "Microsoft Windows Server 2003 (32-bit)". There's no "Enterprise Edition" explicitly listed anymore in ESXi 5.1 as in previous versions. In the vmx file this leads to the... See more...
The VM is configured as "Microsoft Windows Server 2003 (32-bit)". There's no "Enterprise Edition" explicitly listed anymore in ESXi 5.1 as in previous versions. In the vmx file this leads to the entry guestOS = "winnetenterprise" however. We found that if we disable "Memory Hot Add" for this VM, then a startup with 8 GB RAM is possible. All other VMs (including a very similar P2Ved VM) do not have a problem with "Memory Hot Add" enabled - strange. Also, as described before, if "Memory Hot Add" is enabled but the initial amount of RAM is not higher than 4032 MB, hot adding also works for this VM! :smileyshocked:
Hello I encountered a very strange problem with a Windows 2003 VM and have no idea how to solve it. The problem started when the VM was cold migrated from an old host to a new one, got a VM... See more...
Hello I encountered a very strange problem with a Windows 2003 VM and have no idea how to solve it. The problem started when the VM was cold migrated from an old host to a new one, got a VMware Tools update and the requested reboot. Then the VM did not start anymore, resetting after less than a second (even before showing any Windows splash screen). Even Safe Boot, Last Known Good etc. didn't really help; it would maybe start till the logon screen in safe mode but resetted (without blue-screen) a few seconds later. I tried a lot of things: attaching to 2nd VM for chkdsk, disabling VMware Tools service by editing the registry hive, recovery console, new vm with just disk attached, etc. pp. No joy. Then I configured the VM with just 1 CPU and 1 GB RAM, and it started! Tried 2nd CPU, 4 CPUs, more RAM - bang, problem back. I iteratively narrowed it down to this, 100% reproducible: 4032 MB RAM works 4036 MB RAM doesn't work To make it even sweeter, if I hot-add RAM (beyond 4032 MB) after the VM started, it works! To make it even more interesting, I can reboot the VM then and it still works! But if I shutdown the VM and restart the VM container with more than the magic 4032 MB, it resets immediately! I have another "identical" VM on that cluster, and there's no problem at all. Any hints where to look? More information: - vHW9 - 4 vCPU, 8 GB vRAM (initially) - The VM was originally (long time ago) created by P2V I guess (it has a virtual USB controller device) - W2K3 Enterprise 32 bit SP2 - Memory Hot Add enabled - ESXi 5.1.0 build 1483097 - Critial system files are identical to a working system (hal.dll, ntdetect.com, ntldr, ntoskrnl.exe, boot.ini) - chkdsk, fixmbr, fixboot done - VMware Tools reinstalled - Booted on different hosts (even on the "old" cluster)
All these tips didn't work for me - the default gateway (route) was always gone after a reboot (or service network restart). The solution for me was: sudo vi /etc/sysconfig/network/routes ... See more...
All these tips didn't work for me - the default gateway (route) was always gone after a reboot (or service network restart). The solution for me was: sudo vi /etc/sysconfig/network/routes and add a line "default your_gateway_ip dev eth0". Then sudo service network restart
The "sdelete -c" trick worked for me on all VMs so far! In one instance, I had sdelete run and then increased the vmdk by some GB, and before the storage migration to convert it to thin - the ... See more...
The "sdelete -c" trick worked for me on all VMs so far! In one instance, I had sdelete run and then increased the vmdk by some GB, and before the storage migration to convert it to thin - the disk showed up as thin already! So it's a bug in VMware I guess. All my VMs were converted from SAN storage to NAS storage with the thin option, yet a certain amount of machines has "thick eager zeroed" disks (often the secondary disk).
I have this problem too. The second disk of some VMs will stay on "Thick Provision Eager Zeroed" no matter what I do. The VM might be an older one though, created as vHW 4 and then upgraded to v... See more...
I have this problem too. The second disk of some VMs will stay on "Thick Provision Eager Zeroed" no matter what I do. The VM might be an older one though, created as vHW 4 and then upgraded to vHW 7 and now 8. Running on Esxi 5.0.0 build 821926. In the .vmdk file the parameter ddb.adapterType is set to "legacyESX". Does this maybe prevent it from being converted to thin?
It really puzzles me that this old question is unanswered, and that this topic/problem seems rarely discussed. :smileyshocked: On standard switches you can define a port group either as Virtua... See more...
It really puzzles me that this old question is unanswered, and that this topic/problem seems rarely discussed. :smileyshocked: On standard switches you can define a port group either as Virtual Machine or VMkernel port group. VMkernel port groups will not show up in the hosts network list, and you can't assign a VM network card to this port group. This is how it should be in my opinion. But with virtual distributed switches (vDS) there is no option to define the connection type?! Therefore VLANs that are used for the ESX host only (like FT, VMotion, Management Traffic and NFS storage) can accidentally assigned to a VM network card. :smileyshocked: Especially in case of VMotion or NFS this can expose a security threat, since these VLANs usually are not routed and not accessible from the normal network. This type of traffic is also not encrypted as far as I know... I don't think the "permissions approach" is feasible here. Either I'm missing something here completely, or VMware hasn't well-conceived this feature.
But SERIOUSLY, it's been out a WHOLE day you are ALREADY complaining it needs to be supported???!!  It takes time to make APPs compatible.. did you lose your common sense or are you high? Ne... See more...
But SERIOUSLY, it's been out a WHOLE day you are ALREADY complaining it needs to be supported???!!  It takes time to make APPs compatible.. did you lose your common sense or are you high? Neither. But why is VMware "claiming" to support Windows 8 (it is inthe OS dropdown list) if they do not even implement the required 11 year old ACPI standard... :smileyconfused: The competition does... (and other VMware products like Workstation... but not their "flagship"...)
@Dave.Mishchen… This doesn't work... How's that... Windows 8 and Windows 8 Server (both in 32 and 64 bit) are implemented in the ESXi 5.0 OS drop down list (but oddly NOT when creating the VM... See more...
@Dave.Mishchen… This doesn't work... How's that... Windows 8 and Windows 8 Server (both in 32 and 64 bit) are implemented in the ESXi 5.0 OS drop down list (but oddly NOT when creating the VM in the first place... but later when editing it?!), but Windows 8 crashes because ACPI 2.0 is not supported. It's embarassing for VMware that they do not support an ACPI 2.0 standard from year 2000! ACPI 3.0 was already defined 2003... :smileyshocked: Btw, Windows 8 installed without ANY issues on an old Sony Vaio laptop (2-3 years old)... but not on a three weeks old VMware ESXi release... :smileyangry:
Hi Is there a way to downgrade the vNetwork Distributed Switch version from 4.1.0 to 4.0? Background: We got new hosts and installed them with ESXi 4.1 in a new cluster, and created vDS ... See more...
Hi Is there a way to downgrade the vNetwork Distributed Switch version from 4.1.0 to 4.0? Background: We got new hosts and installed them with ESXi 4.1 in a new cluster, and created vDS with version 4.1.0 The previous hosts are running ESX 4.0 and do not have vDS configured, just standard virtual switches. For the migration of the VMs I wanted to add the old hosts to the vDS... but I can't since the vDS version is too new.
I tried the installation again with install cdrom instead of install url and it worked now... :smileyconfused: So it seems specifying another vmnic than vmnic0 is not compatible with the network... See more...
I tried the installation again with install cdrom instead of install url and it worked now... :smileyconfused: So it seems specifying another vmnic than vmnic0 is not compatible with the network installation option (at least if there's no connectivity on vmnic0)...
Hi We've tried to install ESXi 4.1 on a HP BL460c G7 blade with scripted installation. Our Service Console network is connected to a port of the quad-port nic, which is vmnic4. In the ks.cfg f... See more...
Hi We've tried to install ESXi 4.1 on a HP BL460c G7 blade with scripted installation. Our Service Console network is connected to a port of the quad-port nic, which is vmnic4. In the ks.cfg file, we specified network --addvmportgroup=true --device=vmnic4 --bootproto=static --ip=1.2.3.4 --netmask=255.255.255.0 --gateway=1.2.3.5 --nameserver=1.2.3.6 --hostname=esxhost Nevertheless, the installer chooses vmnic0 (and DHCP)... vmnic0 is one of the trunks, no DHCP available... and we end up with the error: Error (see log for more info): Error connection to the network Did not get an IP Address from DHCP server In the esxi_install.log I can see it parses the ks.cfg... so the file is read. But then it gets odd... DEBUG Progress happened on a task that has not started INFO Network choices not specified.  Using DHCP. WARNING Still waiting for an IP address from DHCP DEBUG Progress happened on a task that has not started It tries to fetch the install sources from a webserver via vmnic0 and fails. If we install ESXi 4.1 manually and switch from vmnic0 to vmnic4 everything is fine. But we need it working with scripted installation...
No, no backups that could generate additional snapshots... and all VMs are constantly powered on. But good point, DRS is enabled and is moving some VMs around... I just checked all 12 VMs in t... See more...
No, no backups that could generate additional snapshots... and all VMs are constantly powered on. But good point, DRS is enabled and is moving some VMs around... I just checked all 12 VMs in the LUN, and indeed the two VMs already having an open snapshot got vmotioned a lot... that means every couple days (8 hosts in the cluster). But VMotion of a snapshotted VM will not generate an additional snapshot? What about the swapfile? But VMotion didn't happen every day anyway, but we get the alarm at least once a day. I also checked all vmdks - all are "thick". Today I was able to see the Datastore summary page while the LUN reported the alarm, and saw this: Capacity 351 GB Provisioned Space: 371 GB Free Space: 19 GB <-- triggers alarm After I refreshed it, the alarm went away: Capacity 351 GB Provisioned Space: 311 GB Free Space: 39 GB (values slightly rounded) I did a du -h . on the LUN and will try to repeat it while the alarm is set again, hopefully narrowing it down to the VM causing it...
Your tip didn't help, unfortunately. The same alarm still triggers once or twice a day... all I can see is, that there are constantly 39 GB of free space.. Any other ideas?
Ok, I just disabled and re-enabled it... will have to wait 1-2 days to see its effect. Awkward: the alaram definition is set on a folder which contains seven identical LUNS; problem occurs onl... See more...
Ok, I just disabled and re-enabled it... will have to wait 1-2 days to see its effect. Awkward: the alaram definition is set on a folder which contains seven identical LUNS; problem occurs only with one specific LUN I never have to acknowledge or reset to green... it happens automatically.
Hi We have a problem with a Datastore Disk Usage alarm that triggers without obvious reason... We have several SAN LUNs with 351 GB capacity and a Datastore Disk Usage alarm set to 93% (w... See more...
Hi We have a problem with a Datastore Disk Usage alarm that triggers without obvious reason... We have several SAN LUNs with 351 GB capacity and a Datastore Disk Usage alarm set to 93% (warning) and 97% (alert). So the alarms should trigger around 24.5 and 10.5 GB free space left. While this works as expected for the majority of LUNs, we have one where the yellow alarm is set off about once a day... and goes back from yellow to green after one hour or so (but sometimes it takes several hours overnight), according to the Events list. This LUN has 39.7 GB of free space currently... so fairly above the 24.5 GB threshold. Two of the twelve Windows Server VMs residing on this LUN have a snapshot, which are growing slowly, of course. What could cause the trigger to think that suddenly there is less than 24.5 GB of free space, but if I check or refresh the datastore, everything is ok again...? ESX 4.0.0 Hosts and vCenter 4.0.0
I'd like to know in which location vCenter Server 4.0 license keys are saved? Somewhere in the database? Or a file? Registry? ...?
Thanks man! I almost went crazy with this issue... My PATH variable contained quotes around the PKzip path; I removed them and now Update Manager works like a charm! But I rate this as a V... See more...
Thanks man! I almost went crazy with this issue... My PATH variable contained quotes around the PKzip path; I removed them and now Update Manager works like a charm! But I rate this as a VMware bug - since the PATH is perfectly working in Windows...