<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Virt-Manager on Michele Bologna</title>
    <link>https://www.michelebologna.net/tags/virt-manager/</link>
    <description>Recent content in Virt-Manager on Michele Bologna</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 15 May 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.michelebologna.net/tags/virt-manager/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Accessing remote libvirt on a non-standard SSH port via virt-manager</title>
      <link>https://www.michelebologna.net/2018/accessing-virt-manager-on-a-non-standard-ssh-port/</link>
      <pubDate>Tue, 15 May 2018 00:00:00 +0000</pubDate>
      <guid>https://www.michelebologna.net/2018/accessing-virt-manager-on-a-non-standard-ssh-port/</guid>
      <description>&lt;p&gt;Scenario: you are using a remote host as a virtualization host with libvirt and you want to manage it via ”Virtual machine manager” (&lt;code&gt;virt-manager&lt;/code&gt;) over SSH.&lt;/p&gt;&#xA;&lt;p&gt;But SSH is listening on a non-standard port, and &lt;code&gt;virt-manager&lt;/code&gt; does not offer you to connect to a remote libvirt instance on a non-standard port.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
