Someone mentioned to me that they interpreted this section of the KVM
driver page as suggesting that new guests should be created by
creating a qemu commandline and converting it to XML with
domxml-from-native. I don't think that's the intent of
domxml-from-native, so I added that clarification.
v2
Suggstion from eblake: Add link to the applications page
---
docs/drvqemu.html.in | 13 ++++++++++---
1 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in
index fa5496c..fc76829 100644
--- a/docs/drvqemu.html.in
+++ b/docs/drvqemu.html.in
@@ -432,9 +432,16 @@ mount -t cgroup none /dev/cgroup -o devices
<h3><a name="xmlimport">Converting from QEMU args to domain
XML</a></h3>
<p>
- The <code>virsh domxml-from-native</code> provides a way to convert an
- existing set of QEMU args into a guest description using libvirt Domain XML
- that can then be used by libvirt.
+ The <code>virsh domxml-from-native</code> provides a way to
+ convert an existing set of QEMU args into a guest description
+ using libvirt Domain XML that can then be used by libvirt.
+ Please note that this command is intended to be used to convert
+ existing qemu guests previously started from the command line to
+ be managed through libvirt. It should not be used a method of
+ creating new guests from scratch. New guests should be created
+ using an application calling the libvirt APIs (see
+ the <a href="apps.html">libvirt applications page</a> for
some
+ examples) or by manually crafting XML to pass to virsh.
</p>
<pre>$ cat > demo.args <<EOF
--
1.7.7.6