joelau007's Posts

Apologies my mistake, mixed up the IPs and logged into the wrong box. The instruction works thanks all. (No thanks to VMware though, high CPU bug, now plug-in bug)
No luck with the instruction. I can't even find lstool.py The whole vmware-lookupsvc directory is missing ??? ls -l /usr/lib total 28 drwxr-xr-x 1 root root 512 Jan 10 04:25 hostprofiles lrwxrwx... See more...
No luck with the instruction. I can't even find lstool.py The whole vmware-lookupsvc directory is missing ??? ls -l /usr/lib total 28 drwxr-xr-x 1 root root 512 Jan 10 04:25 hostprofiles lrwxrwxrwx 1 root root 19 Jun 2 2020 libboost_zlib-gcc48-mt-1_55.so.1.55.0 -> /lib/libz.so.1.2.11 lrwxrwxrwx 1 root root 19 Jun 2 2020 libboost_zlib-gcc48-mt-d-1_55.so.1.55.0 -> /lib/libz.so.1.2.11 drwxr-xr-x 1 root root 512 Jan 10 04:25 locale drwxr-xr-x 1 root root 512 Jan 10 04:25 ssl drwxr-xr-x 1 root root 512 Jan 10 04:25 vmware drwxr-xr-x 1 root root 512 Jan 10 04:25 xorg
A bit of mixed and confusing results. First, on the fresh Windows 2008R2 VM with vmxnet3, re-install Vmware tools indeed increase the copy speed from 30+MB/s to 50+MB/s. Still a bit short of t... See more...
A bit of mixed and confusing results. First, on the fresh Windows 2008R2 VM with vmxnet3, re-install Vmware tools indeed increase the copy speed from 30+MB/s to 50+MB/s. Still a bit short of the 80MB/s+ delivered by the good old e1000. With this result in mind, I went on to re-install Vmware tools on another Windows 2008R2 VM with the same speed issue. However it didn't do the trick this time, still stuck at 30+MB/s.
Well, I did not re-install Vmware tools. However I did check Device Manager to make sure the detected NIC has changed from Pro/1000 MT to a vmxnet3. I'll test re-install Vmware tools later in ... See more...
Well, I did not re-install Vmware tools. However I did check Device Manager to make sure the detected NIC has changed from Pro/1000 MT to a vmxnet3. I'll test re-install Vmware tools later in the evening.
Hi, I have a decent IBM server which is used for testing/development work. I have installed a fresh Windows 2008R2 VM, with e1000. Using a 6GB iso file, file copy speed between physical PC t... See more...
Hi, I have a decent IBM server which is used for testing/development work. I have installed a fresh Windows 2008R2 VM, with e1000. Using a 6GB iso file, file copy speed between physical PC to this VM (with e1000) is around 80+MB/s. Then I powered off this VM, remove e1000, add vmxnet3. Power it on. Using the same 6GB iso file, file copy speed between physical PC to this VM (with vmxnet3) is around 30+MB/s. So between these two tests only the NIC type has been changed. Everything else stays the same, same RAID disk, same vswitch, same physical 1Gbps switch. Host CPU load and physical switch load is negligible, I'm the only person using these resources. Some posts suggest these changes to the Windows 2008R2 VM settings, Netsh int tcp set global RSS=Disable Netsh int tcp set global chimney=Disabled Netsh int tcp set global autotuninglevel=Disabled Netsh int tcp set global congestionprovider=None Netsh int tcp set global ecncapability=Disabled Netsh int ip set global taskoffload=disabled Netsh int tcp set global timestamps=Disabled None of these made any difference, vmxnet3 is still stuck around 30+MB/s. I'm hoping someone has seen this issue because I'm hopelessly stuck. Regards.
5.5 version of the document, http://www.vmware.com/files/pdf/techpaper/hpm-perf-vsphere55.pdf I still want to use P-states so High performance is not what I'm after. I can set it to Custom, ... See more...
5.5 version of the document, http://www.vmware.com/files/pdf/techpaper/hpm-perf-vsphere55.pdf I still want to use P-states so High performance is not what I'm after. I can set it to Custom, and Power.UseCstate to turn off C-states, but this is still not the same as Balanced in 5.1 as I will lose the use of C1,C2.
Hi, I sort of have to find an answer to this question before migrating from 5.1 to 5.5. I have to prevent ESXi from using deep C-state C3. This is due to a design flaw in the IBM server hardw... See more...
Hi, I sort of have to find an answer to this question before migrating from 5.1 to 5.5. I have to prevent ESXi from using deep C-state C3. This is due to a design flaw in the IBM server hardware. Therefore I have a setting in UEFI which limits to C2. Now with ESXi 5.5, balanced power scheme will use deep C-states. How will this react with the UEFI setting ? Which takes priority, ESXi or UEFI setting ? Regards.
Yes I guess there must be a reason for not doing this. I can only see this useful in certain test environment limited to 1 local hard disk. Example create a "employee1-datastore" and "employee2-d... See more...
Yes I guess there must be a reason for not doing this. I can only see this useful in certain test environment limited to 1 local hard disk. Example create a "employee1-datastore" and "employee2-datastore" in the same hard disk.
Try a higher version of FreeNas ? I have a test ESXi 5.1 working with FreeNas 9.1
Hi, I'm doing this as a experiment. I have a 40GB empty harddisk. First, create a datastore, specify 10GB. After that, try to create a new datastore again. The same harddisk won't show up to s... See more...
Hi, I'm doing this as a experiment. I have a 40GB empty harddisk. First, create a datastore, specify 10GB. After that, try to create a new datastore again. The same harddisk won't show up to select. But if I try to increase the datastore, it works. So this means I can't have more than 1 datastore in a harddisk. Any idea why Vmware design it this way ?
Found the solution to this issue burried deep in another forum. Remove all unreachable data stores from Vcenter. In my case I had a iscsi and a nfs store unreachable.
I can confirm this daughter card works properly with ESXI 5.
Hi, I have a test lab ESXI 5 with vcenter 5 running as a VM on the same host. I tend to power off this host at the end of the day and power on the next day. For convenient sake, I have turned o... See more...
Hi, I have a test lab ESXI 5 with vcenter 5 running as a VM on the same host. I tend to power off this host at the end of the day and power on the next day. For convenient sake, I have turned on auto start up vcenter when the host boots up. So I can use vsphere client to connect to the vcenter. In vcenter, if I try to power on another VM, it shows "The operation is not allowed in the current state of the host" This error doesn't happen all the time the host boots up, maybe around 50-50%. One way that I can clear this error condition is in vcenter select the host and select disconnect then connect. Another way is to reboot vcenter VM. I'm puzzled by this funny error condition. Regards.
Hopefully there will be a patch soon for this issue. I use esxi5 in a lab environment and often the iscsi target is powered off.  Now I know why the host seems to have hung at iscsi_vmk
Has anyone else tried this option 46M1076 recently ? I'm going down this path but got worried after reading this post. Essentially this option is just another 2x BCM 5709 ports. Regards.