<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><title>Re[2]: [virt-tools-list] virt-manager / QEMU problem connecting to graphical console</title>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
body {
margin: 5px 5px 5px 5px;
background-color: #ffffff;
}
/* ========== Text Styles ========== */
hr { color: #000000}
body, table /* Normal text */
{
font-size: 9pt;
font-family: 'Arial';
font-style: normal;
font-weight: normal;
color: #000000;
text-decoration: none;
}
span.rvts1 /* Heading */
{
font-size: 10pt;
font-weight: bold;
color: #0000ff;
}
span.rvts2 /* Subheading */
{
font-size: 10pt;
font-weight: bold;
color: #000080;
}
span.rvts3 /* Keywords */
{
font-size: 10pt;
font-style: italic;
color: #800000;
}
a.rvts4, span.rvts4 /* Jump 1 */
{
font-size: 10pt;
color: #008000;
text-decoration: underline;
}
a.rvts5, span.rvts5 /* Jump 2 */
{
font-size: 10pt;
color: #008000;
text-decoration: underline;
}
span.rvts6
{
font-size: 8pt;
font-style: italic;
color: #c0c0c0;
}
span.rvts7
{
font-size: 8pt;
font-style: italic;
color: #c0c0c0;
}
/* ========== Para Styles ========== */
p,ul,ol /* Paragraph Style */
{
text-align: left;
text-indent: 0px;
padding: 0px 0px 0px 0px;
margin: 0px 0px 0px 0px;
}
.rvps1 /* Centered */
{
text-align: center;
}
--></style>
</head>
<body>
<p><span class=rvts7>>> >> The remote host OS is Debian Lenny (volatile), kernel 2.6.26-2-amd64)</span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> >> The OSs on which I tried all the virt-manager versions are Ubuntu (latest) and </span></p>
<p><span class=rvts7>>> >> Fedora Core 12.</span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> >> I've used both the packaged versions (.deb & rpm) and I tried with version 0.8.1 </span></p>
<p><span class=rvts7>>> >> from source.</span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> >> Latest one I tried was 0.8.2 under Fedora Core 12 from testing-unstable.</span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> >> All the VMs mentioned are indeed on a remote host, I have no local VMs.</span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> >> Andy</span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> >></span></p>
<p><span class=rvts7>>> </span></p>
<p><span class=rvts7>>> This likely has to do with 'nc' version incompatibilities. virt-manager</span></p>
<p><span class=rvts7>>> and libvirt use the 'nc' utility to stream connection and VNC data over</span></p>
<p><span class=rvts7>>> ssh. Fedora and debian have different default 'nc' utilities with</span></p>
<p><span class=rvts7>>> different options: upstream virt-manager works with red hat based</span></p>
<p><span class=rvts7>>> distros, but debian packages should be appropriately patched to work</span></p>
<p><span class=rvts7>>> with remote debian hosts.</span></p>
<p><br></p>
<p><span class=rvts7>> libvirt in Debian requires the correct 'nc' implementation. So if </span></p>
<p><span class=rvts7>> you're able to connect over SSH with libvirt, then virt-manager should</span></p>
<p><span class=rvts7>> not have any trouble with 'nc' itself. There shouldn't be any need to</span></p>
<p><span class=rvts7>> patch virt-manager - just install the correct 'nc' which is already</span></p>
<p><span class=rvts7>> available in Debian</span></p>
<p><br></p>
<p><span class=rvts7><br></span></p>
<p><span class=rvts7><br></span></p>
<p>Following the NC incompatibility reasoning I installed a fresh Debian OS, with the exact same kernel as my server, on my client machine.</p>
<p>Both machines are now running Debian Lenny with volitale updates and a 2.6.26-2-amd64 kernel.</p>
<p><br></p>
<p>But, I still have the same problem: it won't connect to the virtual machines screen when it's already running.</p>
<p><br></p>
<p>I guess I should've used Fedora as my server OS then... since the machine is already online, that's no more an option though.</p>
<p>I will live with this inconvienience for the time being and just use SSH for my linux clients.</p>
<p><br></p>
<p>Regards,</p>
<p>Andy</p>
<p><br></p>
</body></html>