VMware Cloud Community
tupelo_operatio
Contributor
Contributor

Virtual Center strangeness....

My colleague just brought an issue to my attention. When I log into the Virtual Center client and scroll down to the cluster we have designated for VDI, there are a couple of VMs showing up like this:

TC2015 (1)

TC2015 (orphaned)

TC8007 (1) (orphaned)

TC8007 (2)

I checked to see what ESX hosts those VMs are running on and then ssh'd into those hosts and issued an esxtop to verify just what is running on the given host.

Virtual Center says that TC8007 (1) and TC8007 (2) are running on VM8

VM8 reports the following VMs in esxtop:

23 23 TC2011 5 5.18 0.00 0.05 5.19 458.03 13.92 471.95 0.00 0.00 8

220 220 TC2006 5 4.38 0.02 0.04 5.14 457.97 14.47 472.44 0.00 0.00 8

353 353 TC2022 5 5.10 0.01 0.04 5.75 447.70 17.36 465.06 0.00 0.00 8

508 508 TC8007 5 6.44 0.04 0.04 6.85 440.22 17.95 458.16 0.00 0.00 7

594 594 TC2008 5 22.59 0.12 0.10 25.21 419.15 20.02 439.16 0.00 0.00 5

596 596 TC2010 5 17.72 0.02 0.09 20.13 410.16 28.45 438.61 0.01 0.00 5

694 694 TC8005 5 6.55 0.02 0.05 7.51 431.01 23.14 454.15 0.00 0.00 7

698 698 TC2004 5 8.48 0.02 0.03 9.32 443.48 17.34 460.82 0.00 0.00 7

704 704 TC2016 5 6.95 0.00 0.04 7.47 449.49 18.07 467.56 0.00 0.00 8

709 709 TC2021 5 7.42 0.01 0.02 8.00 447.91 17.14 465.05 0.00 0.00 7

712 712 TL7000 5 5.24 0.01 0.04 5.48 459.02 12.39 471.42 0.00 0.00 8

717 717 TC8009 5 5.47 0.00 0.04 6.11 439.68 19.34 459.02 0.00 0.00 7

720 720 TC2009 5 11.46 0.00 0.05 13.59 422.99 24.80 447.79 0.00 0.00 6

Virtual Center reports that TC2015 (1) is running on VM9

esxtop on VM9 reports the following:

365 365 TC2018 5 4.68 0.00 0.02 5.96 449.07 20.43 469.51 0.00 0.00 8

395 395 TC2005 5 7.93 0.03 0.03 8.99 415.60 34.85 450.45 0.00 0.00 6

401 401 TC2007 5 2.93 0.00 0.04 4.25 442.83 28.38 471.21 0.00 0.00 8

414 414 TC2002 5 7.08 0.01 0.03 7.87 438.44 21.90 460.34 0.00 0.00 7

535 535 TC2000 5 4.77 0.02 0.02 5.92 441.37 24.22 465.59 0.00 0.00 8

540 540 TC2015 (1) 5 6.56 0.01 0.02 7.62 432.89 22.87 455.75 0.00 0.00 7

544 544 TC8003 5 4.34 0.02 0.05 5.41 418.53 33.42 451.95 0.00 0.00 7

549 549 TC2017 5 5.65 0.02 0.02 6.97 442.24 20.33 462.57 0.00 0.00 7

559 559 TC2019 5 90.82 0.00 0.12 94.27 367.44 13.50 380.94 0.01 0.00

In the past I had seen orphaned objects but I have never seen it like this before. Anyone seen this before? Any idea how to fix this?

Reply
0 Kudos
5 Replies
kbk00
Hot Shot
Hot Shot

Are you using VMware's broker (VDM)?






If you found this posting to be useful, great. I didn't waste your time.

If you found this posting to be useful, great. I didn't waste your time.
Reply
0 Kudos
tupelo_operatio
Contributor
Contributor

no...we are not using a broker of any kind...

Reply
0 Kudos
aguacero
Hot Shot
Hot Shot

Yeah I've seen that before but didn't know what would cause it. I would assume this is one of the bugs with 2.x but should be resolved with one of the releases. Which version are you running?

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Reply
0 Kudos
tupelo_operatio
Contributor
Contributor

Virtual Center Client and Server - Version 2.0.2 Build 62327

ESX Server 3.0.2 Build 61618

Reply
0 Kudos
kjb007
Immortal
Immortal

I've seen this happen, but it's usually with vm's that had an issue shutting down or vmotion'ng properly. What you can do, when you get time, is remove the vm from inventory, and then add it back in.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos