seniord's Posts

I wouldn't change my mind based on a single post that doesn't even highlight what the 'weird issues' are! The fact that that the author didn't bother to ask the sales guy to explain them raises... See more...
I wouldn't change my mind based on a single post that doesn't even highlight what the 'weird issues' are! The fact that that the author didn't bother to ask the sales guy to explain them raises alarm bells... not really firm basis for a decision. It appears that Marko has implemented a boot from SAN solution which would not have been possible with ESXi anyway. I know many HP customers using ESXi without problems. Their basis of selecting this architecture varies from security (no Service Console), simplicity of deployment (quick), simplicity of management (less patching), cost (SD or USB instead of disks). These are valid reasons for selecting one over the other.
Glad you could access the media. For future reference, the links to the HP ESXi image (which includes the HP CIM providers) and the standalone HP CIM providers is available at the HP VMware web... See more...
Glad you could access the media. For future reference, the links to the HP ESXi image (which includes the HP CIM providers) and the standalone HP CIM providers is available at the HP VMware website: www.hp.com/go/vmware. Integrated HP VMware ESXi 4.0 HP CIM Providers for ESXi 4.0 It is also worth refering to the following HP whitepaper which discusses how to manage and monitor HP Embedded VMware ESXi with HP Systems Insight Manager; HP VMware ESXi Management Environment integration note. Again, this whitepaper is available at the HP VMware website.
The HP ESXi image with the Insight Management agents is available from the following site: HP ESXi 4 CIM and ESXi Hope this helps.
Hi, This issue was identified as a problem with the native Windows NFS Services for Unix. I was using the default Windows NFS Services available with Windows 2003 Server R2 SP2 to setup an... See more...
Hi, This issue was identified as a problem with the native Windows NFS Services for Unix. I was using the default Windows NFS Services available with Windows 2003 Server R2 SP2 to setup and configure my NFS share. After following the VMware KB; , and installing the downloadable Windows Services for Unix, this resolved the issue. A collegue was able to reproduce the same issue using the native services as well. Thanks for any responses.
KjB - How would I check this and what would I be looking for? I was just monitoring the network traffic.
In addition, when cloning a thick vmdk on VMFS to a thin vmdk on NFS, the cloned vmdk file is stored in thick format (see below). DC1:VMTemplates is the Windows NFS volume. # ls -lhs to... See more...
In addition, when cloning a thick vmdk on VMFS to a thin vmdk on NFS, the cloned vmdk file is stored in thick format (see below). DC1:VMTemplates is the Windows NFS volume. # ls -lhs total 25G 25G -rw------- 1 root root 24G Apr 1 08:39 WIN24GB-X32STD-flat.vmdk 64K -rw------- 1 root root 372 May 6 11:55 WIN24GB-X32STD.vmdk # vmkfstools -i WIN24GB-X32STD.vmdk -d thin /vmfs/volumes/DC1\:VMTemplates/WIN24GB-X32STD-THIN.vmdk Destination disk format: VMFS thin-provisioned Cloning disk 'WIN24GB-X32STD.vmdk'... Clone: 100% done. # cd /vmfs/volumes/DC1\:VMTemplates/ # ls -lhs total 26G 25G -rw------- 1 root root 24G May 8 2009 WIN24GB-X32STD-THIN-flat.vmdk 512 -rw------- 1 root root 438 May 8 2009 WIN24GB-X32STD-THIN.vmdk #
When creating a thin vmdk file on the NFS volume, the size on disk is 10G (see below). When creating a thin vmdk on a VMFS volume, the size on disk is 1.0M (see below). DC1:VMTemplates is the W... See more...
When creating a thin vmdk file on the NFS volume, the size on disk is 10G (see below). When creating a thin vmdk on a VMFS volume, the size on disk is 1.0M (see below). DC1:VMTemplates is the Windows NFS volume, VDisk1V1 is the VMFS volume. # vmkfstools -c 10G -d thin /vmfs/volumes/DC1\:VMTemplates/TEST.vmdk # cd DC1\:VMTemplates/ # ls -lhs total 12G 10G -rw------- 1 root root 10G May 7 2009 TEST-flat.vmdk 512 -rw------- 1 root root 397 May 7 2009 TEST.vmdk # vmkfstools -c 10G -d thin /vmfs/volumes/VDisk1V1/TEST.vmdk # cd .. # cd VDisk1V1/ # ls -lhs total 1.7M 1.0M -rw------- 1 root root 10G May 7 15:20 TEST-flat.vmdk 64K -rw------- 1 root root 397 May 7 15:20 TEST.vmdk
I would like to store 'thin' vmdk files on an NFS datastore (not a dedicated NAS device) running Windows or Linux/Unix. When using Windows 2003 Standard Server running Windows Se... See more...
I would like to store 'thin' vmdk files on an NFS datastore (not a dedicated NAS device) running Windows or Linux/Unix. When using Windows 2003 Standard Server running Windows Service for Unix, I cannot create or copy thin disks to the Windows NFS share. Can anyone confirm whether storing thin vmdk files is supported on a Windows NFS share? Are there any versions/flavours of Unix or Linux running NFS services that support storing thin vmdk files? Any guidance would be appreciated.
I have been investigating thin provisioning of VM Templates and found that many people are advising that VMware only supports thin provisioning on NFS if the array supports thin provisioning. If ... See more...
I have been investigating thin provisioning of VM Templates and found that many people are advising that VMware only supports thin provisioning on NFS if the array supports thin provisioning. If a VM template is created as a thin disk and then provisioned (or cloned) using VirtualCenter, the disk is automatically converted to thick... http://communities.vmware.com/message/989524#989524 http://communities.vmware.com/message/842777#842777 http://communities.vmware.com/message/843159#843159
VCB now supports backup of local storage via a VM using SCSI hot-add mode. See more info in the Virtual Machine Backup Guide and the following post; http://communities.vmware.com/thread/162789.... See more...
VCB now supports backup of local storage via a VM using SCSI hot-add mode. See more info in the Virtual Machine Backup Guide and the following post; http://communities.vmware.com/thread/162789. In the SCSI Hot-Add mode, you set up one of your virtual machines as a VCB proxy and use it to back up other virtual machines residing on storage visible to the ESX Server that hosts the VCB proxy virtual machine. This mode eliminates the need of having a dedicated physical machine for your VCB proxy and does not require you to expose SAN LUNs to the Windows VCB proxy. In this mode, you can use Consolidated Backup to protect any virtual disks on any type of storage available to your ESX Server host, including NAS or local storage. The only exceptions are physical compatibility RDMs.
If you want to stay up to date with the latest firmware, select the latest version available under any of the OS versions. Currently this is 8.40 under Windows.
Roysan, The CD will never specify VMware so you should accept the recommendation provided. In offline mode, only firmware is updated and drivers specific to the OS are not installed. Therefore... See more...
Roysan, The CD will never specify VMware so you should accept the recommendation provided. In offline mode, only firmware is updated and drivers specific to the OS are not installed. Therefore there should be no issues using the recommended option regardless of installed OS.
As per my previous post in this thread, HP SIM cannot be used to upgrade firmware as the HP Version Control module it does not support ESX. However, HP SIM can be used to monitor ESX serve... See more...
As per my previous post in this thread, HP SIM cannot be used to upgrade firmware as the HP Version Control module it does not support ESX. However, HP SIM can be used to monitor ESX servers by installing the HP Insight Management Agents for ESX. These agents can also be installed when you don't have HP SIM as you can assess a Systems Management Webpage which provides hardware information on the server. In regards to these agents causing issues with 'hard' reboots, you should disable ASR in the server BIOS to prevent this from happening. Daniel.
Speaking with collegues within HP, it is recommended to use the latest version of the HP Firmware Maintenance CD to ensure that you are up to date with all firmware revisions. Daniel. ... See more...
Speaking with collegues within HP, it is recommended to use the latest version of the HP Firmware Maintenance CD to ensure that you are up to date with all firmware revisions. Daniel.
This is a good question which I am currently investigating with HP. I have previously recommended using the very latest version of the Firmware Maintenance CD. However, I have asked for further c... See more...
This is a good question which I am currently investigating with HP. I have previously recommended using the very latest version of the Firmware Maintenance CD. However, I have asked for further clarification and will post once I get a response.
I should have highlighted that the HP RDP method requires a reboot. Whilst not ideal, at least it is a centralised and automated process. Dan.
JRH, There are 3 options available to automate firmware updates for HP servers as defined in the following article; Unfortunately, HP Version Control does not currently support ... See more...
JRH, There are 3 options available to automate firmware updates for HP servers as defined in the following article; Unfortunately, HP Version Control does not currently support ESX (as you are aware) and neither does HP Smart Update Manager. Therefore, you the only other option is HP Rapid Deployment Pack which is a licensed product. Within HP RDP, the Upgrade ProLiant ML/DL/BL Firmware job uses LinuxPE, not the production operating system. Therefore you can use it on bare-metal servers. The job upgrades the following hardware: System BIOS, Smart Array, iLO, NIC, QLogic HBA, and local hard drives. You can also use this tool to automate your ESX server deployment including the hardware configuration. Hope this helps, Dan.
After a long running VMware support call was finally closed, we were advised that the expected throughput for a VCB server is 40 MB/s from the proxy server to the LUN. Specific details regardin... See more...
After a long running VMware support call was finally closed, we were advised that the expected throughput for a VCB server is 40 MB/s from the proxy server to the LUN. Specific details regarding what limits this speed were not provided.
Is there anyone else who can confirm what Samir explained about how the VMware Tools heartbeat communicates with VirtualCenter? Or is there any different opinions? There are points st... See more...
Is there anyone else who can confirm what Samir explained about how the VMware Tools heartbeat communicates with VirtualCenter? Or is there any different opinions? There are points still to award for further clarification... otherwise they all go to Samir!! Thanks Daniel.
Anil, According to all VMware documentation, you must install VMware Tools for the VM heartbeat to be reported correctly to VirtualCenter (see links in previous post). VMs can reside in an... See more...
Anil, According to all VMware documentation, you must install VMware Tools for the VM heartbeat to be reported correctly to VirtualCenter (see links in previous post). VMs can reside in an ESX HA cluster without the heartbeat activated. What I am trying to understand is exactly how VMware Tools communicates with VirtualCenter. Daniel.