Re: [libvirt] about libvirt-qpid on libvirt.org
On Tue, Jan 27, 2009 at 12:51:57PM +0900, Atsushi SAKAI wrote: Hi, I have a question about libvirt-qpid. The libvirt-qpid is working for QPID broker? If so, it should be added in livirt is section of following pages. http://libvirt.org/ How do you think? Yes, it should be listed - here is an updated front page, also added the User Mode Linux driver, and mentioning the Windows client support. I also added details of URI format to all the per-driver pages, since people often seem to ask about this Daniel diff -r f787e41fb699 docs/drvopenvz.html --- a/docs/drvopenvz.html Tue Jan 27 11:15:48 2009 + +++ b/docs/drvopenvz.html Tue Jan 27 11:39:31 2009 + @@ -142,6 +142,7 @@ /p pre openvz:///system (local access) +openvz+unix:///system(local access) openvz://example.com/system (remote access, TLS/x509) openvz+tcp://example.com/system (remote access, SASl/Kerberos) openvz+ssh://r...@example.com/system (remote access, SSH tunnelled) diff -r f787e41fb699 docs/drvopenvz.html.in --- a/docs/drvopenvz.html.inTue Jan 27 11:15:48 2009 + +++ b/docs/drvopenvz.html.inTue Jan 27 11:39:31 2009 + @@ -21,6 +21,7 @@ pre openvz:///system (local access) +openvz+unix:///system(local access) openvz://example.com/system (remote access, TLS/x509) openvz+tcp://example.com/system (remote access, SASl/Kerberos) openvz+ssh://r...@example.com/system (remote access, SSH tunnelled) diff -r f787e41fb699 docs/drvqemu.html --- a/docs/drvqemu.html Tue Jan 27 11:15:48 2009 + +++ b/docs/drvqemu.html Tue Jan 27 11:39:31 2009 + @@ -149,6 +149,23 @@ node. If both are found, then Xen paravirtualized guests can be run using the KVM hardware acceleration. /li/ul +h2Connections to QEMU driver/h2 +p +The libvirt QEMU driver is a multi-instance driver, providing a single +system wide privileged driver (the system instance), and per-user +unprivileged drivers (the session instance). The of the driver protocol +is qemu. Some example conection URIs for the libvirt driver are: +/p +pre +qemu:///session (local access to per-user instance) +qemu+unix:///session (local access to per-user instance) + +qemu:///system (local access to system instance) +qemu+unix:///system (local access to system instance) +qemu://example.com/system(remote access, TLS/x509) +qemu+tcp://example.com/system(remote access, SASl/Kerberos) +qemu+ssh://r...@example.com/system (remote access, SSH tunnelled) +/pre h2 a name=xmlconfig id=xmlconfigExample domain XML config/a /h2 diff -r f787e41fb699 docs/drvqemu.html.in --- a/docs/drvqemu.html.in Tue Jan 27 11:15:48 2009 + +++ b/docs/drvqemu.html.in Tue Jan 27 11:39:31 2009 + @@ -32,6 +32,26 @@ /li /ul +h2Connections to QEMU driver/h2 + +p +The libvirt QEMU driver is a multi-instance driver, providing a single +system wide privileged driver (the system instance), and per-user +unprivileged drivers (the session instance). The of the driver protocol +is qemu. Some example conection URIs for the libvirt driver are: +/p + +pre +qemu:///session (local access to per-user instance) +qemu+unix:///session (local access to per-user instance) + +qemu:///system (local access to system instance) +qemu+unix:///system (local access to system instance) +qemu://example.com/system(remote access, TLS/x509) +qemu+tcp://example.com/system(remote access, SASl/Kerberos) +qemu+ssh://r...@example.com/system (remote access, SSH tunnelled) +/pre + h2a name=xmlconfigExample domain XML config/a/h2 h3QEMU emulated guest on x86_64/h3 diff -r f787e41fb699 docs/drvtest.html --- a/docs/drvtest.html Tue Jan 27 11:15:48 2009 + +++ b/docs/drvtest.html Tue Jan 27 11:39:31 2009 + @@ -126,6 +126,22 @@ /div div id=content h1Test mock driver/h1 +h2Connections to Test driver/h2 +p +The libvirt Test driver is a per-process fake hypervisor driver, +with a driver name of 'test'. The driver maintains all its state +in memory. It can start with a pre-configured default config, or +be given a path to a alternate config. Some example conection URIs +for the libvirt driver are: +/p +pre +test:///default (local access, default config) +test:///path/to/driver/config.xml (local access, custom config) +test+unix:///default(local access, default config, via daemon) +test://example.com/default (remote access,
Re: [libvirt] about libvirt-qpid on libvirt.org
Hi, Daniel It looks good for me. Thanks Atsushi SAKAI Daniel P. Berrange berra...@redhat.com wrote: On Tue, Jan 27, 2009 at 12:51:57PM +0900, Atsushi SAKAI wrote: Hi, I have a question about libvirt-qpid. The libvirt-qpid is working for QPID broker? If so, it should be added in livirt is section of following pages. http://libvirt.org/ How do you think? Yes, it should be listed - here is an updated front page, also added the User Mode Linux driver, and mentioning the Windows client support. I also added details of URI format to all the per-driver pages, since people often seem to ask about this Daniel diff -r f787e41fb699 docs/drvopenvz.html --- a/docs/drvopenvz.html Tue Jan 27 11:15:48 2009 + +++ b/docs/drvopenvz.html Tue Jan 27 11:39:31 2009 + @@ -142,6 +142,7 @@ /p pre openvz:///system (local access) +openvz+unix:///system(local access) openvz://example.com/system (remote access, TLS/x509) openvz+tcp://example.com/system (remote access, SASl/Kerberos) openvz+ssh://r...@example.com/system (remote access, SSH tunnelled) diff -r f787e41fb699 docs/drvopenvz.html.in --- a/docs/drvopenvz.html.in Tue Jan 27 11:15:48 2009 + +++ b/docs/drvopenvz.html.in Tue Jan 27 11:39:31 2009 + @@ -21,6 +21,7 @@ pre openvz:///system (local access) +openvz+unix:///system(local access) openvz://example.com/system (remote access, TLS/x509) openvz+tcp://example.com/system (remote access, SASl/Kerberos) openvz+ssh://r...@example.com/system (remote access, SSH tunnelled) diff -r f787e41fb699 docs/drvqemu.html --- a/docs/drvqemu.html Tue Jan 27 11:15:48 2009 + +++ b/docs/drvqemu.html Tue Jan 27 11:39:31 2009 + @@ -149,6 +149,23 @@ node. If both are found, then Xen paravirtualized guests can be run using the KVM hardware acceleration. /li/ul +h2Connections to QEMU driver/h2 +p +The libvirt QEMU driver is a multi-instance driver, providing a single +system wide privileged driver (the system instance), and per-user +unprivileged drivers (the session instance). The of the driver protocol +is qemu. Some example conection URIs for the libvirt driver are: +/p +pre +qemu:///session (local access to per-user instance) +qemu+unix:///session (local access to per-user instance) + +qemu:///system (local access to system instance) +qemu+unix:///system (local access to system instance) +qemu://example.com/system(remote access, TLS/x509) +qemu+tcp://example.com/system(remote access, SASl/Kerberos) +qemu+ssh://r...@example.com/system (remote access, SSH tunnelled) +/pre h2 a name=xmlconfig id=xmlconfigExample domain XML config/a /h2 diff -r f787e41fb699 docs/drvqemu.html.in --- a/docs/drvqemu.html.inTue Jan 27 11:15:48 2009 + +++ b/docs/drvqemu.html.inTue Jan 27 11:39:31 2009 + @@ -32,6 +32,26 @@ /li /ul +h2Connections to QEMU driver/h2 + +p +The libvirt QEMU driver is a multi-instance driver, providing a single +system wide privileged driver (the system instance), and per-user +unprivileged drivers (the session instance). The of the driver protocol +is qemu. Some example conection URIs for the libvirt driver are: +/p + +pre +qemu:///session (local access to per-user instance) +qemu+unix:///session (local access to per-user instance) + +qemu:///system (local access to system instance) +qemu+unix:///system (local access to system instance) +qemu://example.com/system(remote access, TLS/x509) +qemu+tcp://example.com/system(remote access, SASl/Kerberos) +qemu+ssh://r...@example.com/system (remote access, SSH tunnelled) +/pre + h2a name=xmlconfigExample domain XML config/a/h2 h3QEMU emulated guest on x86_64/h3 diff -r f787e41fb699 docs/drvtest.html --- a/docs/drvtest.html Tue Jan 27 11:15:48 2009 + +++ b/docs/drvtest.html Tue Jan 27 11:39:31 2009 + @@ -126,6 +126,22 @@ /div div id=content h1Test mock driver/h1 +h2Connections to Test driver/h2 +p +The libvirt Test driver is a per-process fake hypervisor driver, +with a driver name of 'test'. The driver maintains all its state +in memory. It can start with a pre-configured default config, or +be given a path to a alternate config. Some example conection URIs +for the libvirt driver are: +/p +pre +test:///default (local access,
Re: [libvirt] about libvirt-qpid on libvirt.org
On Tue, Jan 27, 2009 at 09:04:22PM +0900, Atsushi SAKAI wrote: Hi, Daniel It looks good for me. Ok, i committed that Daniel P. Berrange berra...@redhat.com wrote: On Tue, Jan 27, 2009 at 12:51:57PM +0900, Atsushi SAKAI wrote: Hi, I have a question about libvirt-qpid. The libvirt-qpid is working for QPID broker? If so, it should be added in livirt is section of following pages. http://libvirt.org/ How do you think? Yes, it should be listed - here is an updated front page, also added the User Mode Linux driver, and mentioning the Windows client support. I also added details of URI format to all the per-driver pages, since people often seem to ask about this Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
