(→Enterprise Management Tools List: Connecting to VNC Console on Remote System Installs) |
|||
| Line 43: | Line 43: | ||
=== Enterprise Management Tools List === | === Enterprise Management Tools List === | ||
This section contains the discussion happening on the [https://www.redhat.com/ mailman/listinfo/et-mgmt-tools et-mgmt-tools list] | This section contains the discussion happening on the [https://www.redhat.com/ mailman/listinfo/et-mgmt-tools et-mgmt-tools list] | ||
==== Connecting to VNC Console on Remote System Installs ==== | |||
While executing <code>virt-install</code> on a remote system, Stephan found[1] | |||
that the installer created a VNC service listening on 127.0.0.1, and wanted to | |||
know how to connect to this service or move it to a public interface on the | |||
remote system. | |||
[[DanielBerrange|Daniel P. Berrange]] answered[2] that | |||
modifying the <code>vnc_listen</code> parameter in <code>/etc/libvirt/qemu.conf</code> | |||
will affect the IP used, but this isn't necessary. The <code>virt-viewer</code> application will automatically tunnel[3] VNC connection over SSH. | |||
<pre>virt-viewer --connect qemu+ssh://root@remotehost/system centos1</pre> | |||
[1] http://www.redhat.com/archives/et-mgmt-tools/2008-November/msg00041.html | |||
[2] http://www.redhat.com/archives/et-mgmt-tools/2008-November/msg00042.html | |||
[3] http://virt-manager.org/page/RemoteSSH | |||
=== Fedora Xen List === | === Fedora Xen List === | ||
Revision as of 17:19, 22 November 2008
Virtualization
In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen- list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies.
Contributing Writer: Dale Bewley
Fedora 10 Virtualization Features
The Fedora 10 release includes a number of virtualization enhancements[1] over previous releases.
Below is listing of virtualization softwares comparing the versions at Fedora 9 and Fedora 10 release times.
| Software | F9 Release | F10 Release | Release Notes or Changes |
|---|---|---|---|
| kvm | 65-1 | 74-5 | http://kvm.qumranet.com/kvmwiki/ChangeLog |
| libvirt | 0.4.2-1 | 0.4.6-3 | http://www.libvirt.org/news.html |
| python-virtinst | 0.300.3-5 | 0.400.0-4 | http://virt-manager.et.redhat.com/download.html |
| virt-df | n/a | 2.1.4-2 | http://et.redhat.com/~rjones/virt-df/ |
| virt-manager | 0.5.4-3 | 0.6.0-3 | http://virt-manager.et.redhat.com/download.html |
| virt-mem | n/a | 0.2.9-6 | http://et.redhat.com/~rjones/virt-mem/faq.html |
| virt-top | 0.4.1.1-1 | 1.0.3-2 | http://et.redhat.com/~rjones/virt-top/ChangeLog.txt |
| virt-viewer | 0.0.3-1 | 0.0.3-3 | http://virt-manager.et.redhat.com/download.html |
| xen | 3.2.0-10 | 3.3.0-1 | http://www.xen.org/download/ |
| xenner | 0.29-2 | 0.46-3 | http://cvs.bytesex.org/xenner.html |
| xenwatch | n/a | 0.5.3-1 | http://cvs.bytesex.org/xenwatch.html |
[1] http://fedoraproject.org/wiki/Docs/Beats/Virtualization
Enterprise Management Tools List
This section contains the discussion happening on the mailman/listinfo/et-mgmt-tools et-mgmt-tools list
Connecting to VNC Console on Remote System Installs
While executing virt-install on a remote system, Stephan found[1]
that the installer created a VNC service listening on 127.0.0.1, and wanted to
know how to connect to this service or move it to a public interface on the
remote system.
Daniel P. Berrange answered[2] that
modifying the vnc_listen parameter in /etc/libvirt/qemu.conf
will affect the IP used, but this isn't necessary. The virt-viewer application will automatically tunnel[3] VNC connection over SSH.
virt-viewer --connect qemu+ssh://root@remotehost/system centos1
[1] http://www.redhat.com/archives/et-mgmt-tools/2008-November/msg00041.html
[2] http://www.redhat.com/archives/et-mgmt-tools/2008-November/msg00042.html
[3] http://virt-manager.org/page/RemoteSSH
Fedora Xen List
This section contains the discussion happening on the mailman/listinfo/fedora-xen fedora-xen list.
Libvirt List
This section contains the discussion happening on the mailman/listinfo/libvir-list libvir-list.
oVirt Devel List
This section contains the discussion happening on the mailman/listinfo/ovirt-devel ovirt-devel list.