VMware Performance Community
niceguy001
Enthusiast
Enthusiast
Jump to solution

Guest Info failures for the following machines: 1 machines : Client1 Error Messages Client1=:

okay, this issues troubled me for a while...(under the same configuration and server infrastructure)

i don't know why the client1 VM suddenly start to hanging and failing (to get gust info) at the "VMmark Setup" stage with the following messages:(as shown in figure below)

Client1 : Get Guest Info did not run correctly

Info: Get Linux guest information completed : Client1

Guest Info failures for the following machines: 1 machines : Client1 Error Messages Client1=:

client1.jpg

i've tried the following troubleshoot steps in the primeclient VM:

1. use staf ping ping to check the client1, it responded with PONG

2. double-check the /etc/hosts file, the client1 IP matched

3. re-provision the client1 VM (from tile0), problem is still the same and no help

4. restart the client1 VM, still can't solve the issue

5. under the /root/weathervane folder, couldn't find useful log to check

6. the VMmark3-STAX_Job_2_User-Parsed.log (and other logs) showed no further details about this issue.(in the results folder)

b.t.w this glitch only occurred on my client1 VM all the time while other client VMs are working just fine.

can anyone help?

0 Kudos
1 Solution

Accepted Solutions
niceguy001
Enthusiast
Enthusiast
Jump to solution

hi fred,

i believe i had solved this guest info failure issue.

i tried migrating other client vm(client2) to the disk where client1 located on and ran vmmark again, and the same error(guest info) occurred.

if i migrate the client1 to other disks/hosts then the client1 became normal to run vmmark.

Also did re-install the ESXi which client1 VM located on but this didn't help.

so my conclusion is, there were some kind of errors on the disk where client 1 is located on.

everything worked just fine after i use another disk datastore to place the client1 vm.

anyway, thanks!

View solution in original post

0 Kudos
6 Replies
fredab2
VMware Employee
VMware Employee
Jump to solution

Can you please pack up (zip or tar) the entire Results directory from the Prime client from a failed client1 guest info issue and upload it?

Fred

0 Kudos
niceguy001
Enthusiast
Enthusiast
Jump to solution

hi fred, thanks for reply!

here's the result of the failed run of client1 VM issue attached.

0 Kudos
fredab2
VMware Employee
VMware Employee
Jump to solution

In var log messages info in guestinfofiles for Client1-GuestInfo.txt I see a lot of Client0 references.  Was Client1 at one time Client0?

1. Can you make sure that on Client1 /etc/hostname = Client1?  Also, type 'hostname' and Linux prompt and Client1 should be returned.

2. Can you make sure that on your PrimeClient in /etc/hosts you have different IP's assigned for Client0 and Client1?

3. On Client1 make sure IP and name for Client1 and Primeclient are correct in /etc/hosts?

4. On Client0 make sure IP and name for Client0 and Primeclient are correct in /etc/hosts?

Fred

0 Kudos
niceguy001
Enthusiast
Enthusiast
Jump to solution

hi fred

the client 1 has never been client 0 in my test infra (client1 was cloned from tile0 through the vmmark3.properties command)

and the answer of the 4 questions are:

1. client1 hostname is correct, i checked it.

2. the IP of client0 and client1 are different all the time

3. the name and IP are all correct in /etc/hosts

4. yes the name & IP of client0 and prime are all correct

0 Kudos
fredab2
VMware Employee
VMware Employee
Jump to solution

Can you provision client1 again from tile0 (client0)?  Then package up and send both up the entire provisioning directory as well as the results directory if you still have this issue.

Fred

0 Kudos
niceguy001
Enthusiast
Enthusiast
Jump to solution

hi fred,

i believe i had solved this guest info failure issue.

i tried migrating other client vm(client2) to the disk where client1 located on and ran vmmark again, and the same error(guest info) occurred.

if i migrate the client1 to other disks/hosts then the client1 became normal to run vmmark.

Also did re-install the ESXi which client1 VM located on but this didn't help.

so my conclusion is, there were some kind of errors on the disk where client 1 is located on.

everything worked just fine after i use another disk datastore to place the client1 vm.

anyway, thanks!

0 Kudos