External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-08-26 18:41:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Re-write notes on IPv6

Browse Source
This commit is contained in:
Daniel P. Berrange 2007-07-16 21:37:08 +00:00
parent 67c346b102
commit d9adc2eaf1
3 changed files with 21 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
Mon Jul 16 17:36:24 EST 2007 Daniel P. Berrange <berrange@redhat.com>
* docs/libvir.html, docs/remote.html: Re-write notes on IPV6
support in the remote daemon
Mon Jul 16 16:59:24 EST 2007 Daniel P. Berrange <berrange@redhat.com> Mon Jul 16 16:59:24 EST 2007 Daniel P. Berrange <berrange@redhat.com>
* src/qemu_conf.c, src/qemu_conf.h, src/xend_internal.c, * src/qemu_conf.c, src/qemu_conf.h, src/xend_internal.c,

10
docs/libvir.html
View File

@ -2239,8 +2239,14 @@ Blank lines and comments beginning with <code>#</code> are ignored.
<h3><a name="Remote_IPv6">IPv6 support</a></h3> <h3><a name="Remote_IPv6">IPv6 support</a></h3>
<p> <p>
IPv6 has received some limited testing and should work. Problems with The libvirtd service and libvirt remote client driver both use the
libvirt and IPv6 should be reported as <a href="bugs.html">bugs</a>. <code>getaddrinfo()</code> functions for name resolution and are
thus fully IPv6 enabled. ie, if a server has IPv6 address configured
the daemon will listen for incoming connections on both IPv4 and IPv6
protocols. If a client has an IPv6 address configured and the DNS
address resolved for a service is reachable over IPv6, then an IPv6
connection will be made, otherwise IPv4 will be used. In summary it
should just 'do the right thing(tm)'.
</p> </p>
<h3><a name="Remote_limitations">Limitations</a></h3> <h3><a name="Remote_limitations">Limitations</a></h3>

10
docs/remote.html
View File

@ -548,8 +548,14 @@ Blank lines and comments beginning with <code>#</code> are ignored.
</p> </p>
</td> </td>
</tr></table><h3><a name="Remote_IPv6" id="Remote_IPv6">IPv6 support</a></h3><p> </tr></table><h3><a name="Remote_IPv6" id="Remote_IPv6">IPv6 support</a></h3><p>
IPv6 has received some limited testing and should work. Problems with The libvirtd service and libvirt remote client driver both use the
libvirt and IPv6 should be reported as <a href="bugs.html">bugs</a>. <code>getaddrinfo()</code> functions for name resolution and are
thus fully IPv6 enabled. ie, if a server has IPv6 address configured
the daemon will listen for incoming connections on both IPv4 and IPv6
protocols. If a client has an IPv6 address configured and the DNS
address resolved for a service is reachable over IPv6, then an IPv6
connection will be made, otherwise IPv4 will be used. In summary it
should just 'do the right thing(tm)'.
</p><h3><a name="Remote_limitations" id="Remote_limitations">Limitations</a></h3><ul><li> Remote storage: To be fully useful, particularly for </p><h3><a name="Remote_limitations" id="Remote_limitations">Limitations</a></h3><ul><li> Remote storage: To be fully useful, particularly for
creating new domains, it should be possible to enumerate creating new domains, it should be possible to enumerate
and provision storage on the remote machine. This is currently and provision storage on the remote machine. This is currently