Re: IO Analyzer Hitting Local Disk
Yes, the second disk(vmdk) is located on the iSCSI LUN. We did find the issue--we didn't set the hostname of the workers. Once that was done, the workers started to run correctly.
View ArticleNFS vs iSCSI IOPS differ - why?
Hello - I recently setup an environment utilizing 8 IO Analyzers each accessing either an iSCSI LUN or NFS Share (but not both at the same time). The secondary virtual disk was set at 30GB.For the...
View ArticleRe: NFS vs iSCSI IOPS differ - why?
Would you be by any chance running a ZFS based storage ? (Illumos, FreeNas, Nexenta ?)
View ArticleRe: NFS vs iSCSI IOPS differ - why?
Thanks for the response. Yes, we are using OS Nexus QuantaStor as our storage server and the underlying disks are formatted with ZFS. The other option would be to utilize XFS. I assume you ask because...
View ArticleRe: IO Analyzer Hitting Local Disk
I have the same problem. How to set the hostname of the workers? I do not find it in the doc
View ArticleSizing the Virtual Hard Disk
For I/O Analyzer worker VMs, it's recommended to create a larger second virtual hard disk which serves as the IOmeter target.Is the size of the virtual Hard Disk exactly the same as the workload's...
View ArticleRe: IO Analyzer Hitting Local Disk
We fixed the issue by setting the hostname in the yast2 menu. Run the command: sudo yast2 network and edit the network adapter assigned to the VM. Our hostnames matched the VM names. Hope this helps.
View ArticleRe: NFS vs iSCSI IOPS differ - why?
For those wondering about ZFS and implications on performance, you may want to visit this thread that helped me understand:...
View ArticleOdd I/O Analyzer Behavior
Hello -I have 10 IO Analyzer VMs setup (1 Master and 9 workers). As of late, we've been experiencing odd behavior with respect to the execution of workloads on the worker VMs. The scenario is as...
View ArticleRe: Odd I/O Analyzer Behavior
It sounds like the backend scripts might have stuck in some weird states or have crashed during execution and left the config file in the /tmp directory. Can you try to clean up all temporary files by...
View Article1.6.2 ova file corrupt?
Hi,When I deploy this ova the vmware client complains, right at the end of the process, that the vmdk file fails the integrity check. Can someone kindly compare the md5sum for a working deployment of...
View ArticleRe: 1.6.2 ova file corrupt?
The MD5 checksum is correct. Which version of vSphere are you running? What is the exact error messages? Thanks,Chien-Chia
View ArticleRe: 1.6.2 ova file corrupt?
Hi, vcenter server 5.5 using the vSphere native client and esxi v5.5U2, build 2456374. The error message is :"Failed to deploy OVF package: file vmware-io-analyzer-1.6.2-disk1.vmdk fails integrity...
View ArticleRe: 1.6.2 ova file corrupt?
I deployed it via the Web Client and was successful. There seems to be an issue specific to the native client... Cheers, Ron
View ArticleRe: Sizing the Virtual Hard Disk
As instructed by the user guide, the size will depend on what you want to test :The default size of the secondary virtual disk is 100MB. This default size typically fits entirely within the cacheon...
View ArticleRe: Sizing the Virtual Hard Disk
Hi RS_1, that's helpful, but I was looking for some additional guidance to the user guide. I got the answers from some of the I/O Analyzer developers, and also ran a few tests of my own. Iometer...
View ArticleNo Operating System - v1.6.2 uses 'Paravirtual' scsi hba
Hi, I finally got the v1.6.2 ova to deploy by using the WebClient instead of the NativeClient, however I went to boot it up and it will not boot. The error message is "No operating system found" and...
View ArticleRe: No Operating System - v1.6.2 uses 'Paravirtual' scsi hba
Hi Ron, I don't think it's paravirtual SCSI problem. More likely the deployment is not successful. Can you try a fresh deployment, have disks think eager zeroed, and do not power on after deployment?...
View ArticleRe: No Operating System - v1.6.2 uses 'Paravirtual' scsi hba
Hi, The file sizes are the same as yours but the checksum's are not. vmkfstools reports that the files are not virtual hard disks, specifically:"DiskLib_Check() failed for source disk...
View ArticleRe: No Operating System - v1.6.2 uses 'Paravirtual' scsi hba
Hmmm... Same issue with v1.6.0 deployed via native client - the disk1.vmdk file fails the integrity check and the vm is not deployed. So something to do with my environment, but what? Ron
View Article