Cockpit | Access to the VM console created by Virtual Machine Manager

  • Post author:
  • Reading time:3 mins read
  • Post category:KVM / Linux
  • Post comments:2 Comments

Hi there.

A few months ago, I started to mainly use “cockpit” for managing my virtual machines rather than “Virtual Machine Manager”. But after switching, I noticed that the console was not accessible through the WebUI. I only had the option to connect with a remote viewer, which didn’t work too reliably.

This only affected the VMs that were already created.

So, here is how to solve this.

Edit the VM configuration

We need to edit the XML configuration. To do this, use the “virsh edit” command, do not edit it directly.

Just add the following lines to the “graphics” section.

KVM :: ~ » sudo virsh edit virtual-machine
    <graphics type='vnc' port='-1' autoport='yes' listen=''>
      <listen type='address' address=''/>

It should look similar to this. This is just to give an idea of the formatting. Only the marked lines are relevant.

    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' listen=''>
      <listen type='address' address=''/>
    <graphics type='spice' autoport='yes' listen=''>
      <listen type='address' address=''/>
    <sound model='ich9'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>

That’s it. Now you should be able to access the console through the WebUI.

Till next time.

This Post Has 2 Comments

  1. Michele

    Where can I use the “virsh edit” command? Sorry I’m very noob

    1. Gökhan

      Hello Michele,

      You would use the command on the virtualization server (KVM) where the virtual machine is hosted. In my case, I have a KVM server with several virtual machines (VMs) running on it. I installed Cockpit for management on the KVM Server after deploying the VMs, that’s why I don’t have access to the VMs through Cockpit.

      To get access, I execute the commands on the KVM server.

Leave a Reply