•  

  • Archives

  • Follow me on Twitter

    • « | Home | »

    How to use Virtual IQ to manage Hyper-V environments?


     

    virtualiq It was few months ago when I wrote one post about Virtual IQ, program that helps you monitor virtual machines (Hyper-V, VMWare, Citrix, Oracle). I decided to test it. I have only one laptop, I have Windows Server 2008 R2 installed on it, and I wanted to install Virtual IQ on it to monitor my virtual machines. But, Windows Server 2008 R2 (and Windows Server 2008) are still not supported platform for Virtual IQ, and it didn’t work, I would always get the same error message when trying to add new host:

    Could not connect to agent running on given host name.

    virtual-iq-problem

    With the assistance of Virtual IQ support, I realized that there are two possible ways to solve this problem:

    1. You can install VirtualIQ on separate management machine, which runs Windows Server 2003, or Windows XP, and than you can monitor your Hyper-V machine. I think this is the most common situation in all data centers, management is separated from virtualization environment. Of course, for me this doesn’t work as I don’t have another machine.
    2. If you want to have everything on one machine, solution for this is to install Windows Server 2003 in virtual machine using built-in Hyper-V manager, to install Virtual IQ on it, and then you can add Windows Server 2008 as a virtualization host. So, you would manage virtual environments from virtual machine and for this you need one more license for management operating system (I think most of the companies already have it).

    What’s your opinion about this? Is it wise to monitor Hyper-V from virtual machine which is installed on top of it? Or you prefer to have everything separated? How do you monitor your virtual machines?

     


     

    By Ilija Brajkovic | September 3, 2009
    Tags: , , , , , , ,
    Category: hyper-v | Comments
     Subscribe to RSS feed

    • Simon
      I tried this...still same error even when server hosted on guest vm and agent on virtualisation host.

      Probably something I'm not quite getting. Doesn't seem to be network...but...could be...
    • Hi Marin,

      thank you for your opinion. I also agree that installing monitoring application on separate computer is better option.
    • Monitoring Hyper-V from itself will result in adding overhead to the server and it will distort the results. So the better way to go is to install monitoring application on separate computer.
    blog comments powered by Disqus