Hey, Just committed this simple patch. Cheers, Mark. Subject: [PATCH] Fix typo in manpage It's "service libvirtd start", not "service start libvirtd". Reported-by: Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> Signed-off-by: Mark McLoughlin <markmc@xxxxxxxxxx> --- docs/virsh.pod | 2 +- virsh.1 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/virsh.pod b/docs/virsh.pod index 2438984..6434d78 100644 --- a/docs/virsh.pod +++ b/docs/virsh.pod @@ -34,7 +34,7 @@ the program. All B<virsh> operations rely upon the libvirt library. For any virsh commands to run xend/qemu, or what ever virtual library that libvirt supports. For this reason you should start xend/qemu as a service when your system first boots using xen/qemu. This can usually be done using the command -B<service start libvirtd> . +B<service libvirtd start> . Most B<virsh> commands require root privileges to run due to the communications channels used to talk to the hypervisor. Running as diff --git a/virsh.1 b/virsh.1 index 2197c20..45ea614 100644 --- a/virsh.1 +++ b/virsh.1 @@ -171,7 +171,7 @@ the program. .IX Header "NOTES" All \fBvirsh\fR operations rely upon the libvirt library. For any virsh commands to run xend/qemu, or what ever virtual library that libvirt supports. For this reason you should start xend/qemu as a service when your system first boots using xen/qemu. This can usually be done using the command -\&\fBservice start libvirtd\fR . +\&\fBservice libvirtd start\fR . .PP Most \fBvirsh\fR commands require root privileges to run due to the communications channels used to talk to the hypervisor. Running as -- 1.6.0.6 -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list