Running Cockpit inside of RHV-M

Hi Folks, if you’ve been following things for the last few months, you know RHV 4 launched last month and that one of my favorite new features is the Cockpit hypervisor admin tool. I’ve even highlighted it in 2 posts already, and I’m about to go for the “three-peat”. So what’s so cool that I needed to give it a 3rd shout out in such a short amount of time? Easy.

The ability to run it within RHV-M.I can’t even take credit for this. Obviously I didn’t code this. (If you’ve ever seen me code, you’d know this wasn’t even funny. What I mean is that I wasn’t even the one to stumble into this – it was my friend and colleague Tony James. To make a long story short, he pulled me over to what he stumbled into during a workshop I was running and BOOM!, I knew this was going on the blog.


So what is Cockpit, really? It’s not “just” a virtualization tool. It’s a Linux administration tool that is incredibly extensible. We just happen to use it with our hypervisors (RHVH and RHEL), but you could use it for any/all of your Linux hosts, regardless of the distribution. Check out the official project page.

Host Side Configuration

So what does it take to get Cockpit up and running in RHV – in general and inside of RHV-M? It’s very straightforward. If you’re running the thing hypervisor “RHVH”, then it is already installed and configured. If you’re running the RHEL hypervisor then you need to add one more software repo to the default 2 repo’s:

# subscription-manager repos --enable rhel-7-server-extras-rpms

Then install Cockpit:

# yum y install cockpit

Then enable/start it:

# systemctl enable cockpit.socket
# systemctl start cockpit# systemctl status cockpit

To connect directly to that host, point your browser at https://FQDN:9090 or https://IP:9090. That’s it.

RHV Side Configuration

Configuring Cockpit on RHV is no more difficult. Like the hypervisors, there is also an additional repo to add, but not the same one as the hypervisors:

# subscription-manager repos --enable=rhel-7-server-rhv-4.0-rpms

The install the Cockpit UI package:

# yum -y install cockpit-ovirt-uiplugin

And restart RHV-M:

# systemctl restart ovirt-engine

Then reconnect to RHV-M and you should see a shiny new “Cockpit” sub tab under each host tab. Take a look at the video.

Best view in full screen:

To Plugin or Not?

I could see it both ways here, honestly. If you’re a larger organization then you may have more groups that specialize. In that case, you may want to have “operators” with “operator” logins to Cockpit for the hypervisors or a group of hypervisors in order to perform their duties and responsibilities. In that case leave the plugin out, and just use Cockpit as it ships.

On the other hand, if you’re a smaller group where everyone does a little bit of everything, maybe you don’t want to have so many tools and browsers open. You just want stuff to work together. In that case, plug away my friends.

As always, comments and questions are welcome.

Hope this helps,

Captain KVM

4 thoughts on “Running Cockpit inside of RHV-M”

    1. Prakash,

      Go to You’ll see that Cockpit was actually designed as a general purpose web admin tool for Linux. Red Hat simply added in additional pieces for RHV. I’ve not tried the RHV Cockpit packages on non-RHV systems, so I can’t tell you if anything unexpected happens. But, I can tell you that the upstream Cockpit tool is fantastic.

      Captain KVM

  1. Recently upgraded to from 3.6 and installed the cockpitui-plugin. It is a nice feature however we still have to login to the cockpit UI for each host separately from RHV-M. Is this intended behavior? From the video it seems that it should have just logged me in automatically.

    1. Thanks for stopping by. I have seen it work both ways. I would open up a trouble ticket as I’m not sure what the difference is, honestly. I’ve seen where it was in fact logged in automatically, but I’ve also seen exactly what you’re referring to.

      Captain KVM

Agree? Disagree? Something to add to the conversation?