<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Libvirt on Michele Bologna</title><link>https://www.michelebologna.net/tags/libvirt/</link><description>Recent content in Libvirt 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/libvirt/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;If you manage virtual machines on a remote host using libvirt and virt-manager, the typical connection flow uses SSH. But virt-manager&amp;rsquo;s graphical connection dialog doesn&amp;rsquo;t expose a port field: it assumes SSH is on the default port 22.&lt;/p&gt;</description></item></channel></rss>