Hello,<br><br>Thank you very much for the feedback Nick, I really appreciate it.<br><br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> * To list start a virtual machine:<br> -> remove extra "list"<br> <br> * Similarly, to list start a virtual machine at boot:<br> -> replace extra "list" by "automatically"<br> <br> * The above example assumes that SSH connectivity between the<br> management system and <a href="http://virtnode1.mydomain.com" target="_blank">virtnode1.mydomain.com</a> has already been configured<br> -> add: and uses ssh keys for authentication.<br> <br> * virt-viewer does require a GUI to interaface with the virtual machine.<br> -> replace "interaface" by "interface"<br> <br> * consitency: in virtual machine manager section you use<br> "<a href="http://virtnode1.mydomain.com" target="_blank">virtnode1.mydomain.com</a>" as your example and in Virtual machine viewer<br> section you use "hostname". I believe we should stick to the same example.<br> <br> * Be sure and replace web_devel with the appropriate virtual machine name.<br> -> replace "and" by "to"</blockquote><div><br>These suggestions have been implemented. I need to remember to do some strong proof reading when using cut'n paste... heh. <br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> * If configured to use a bridged network interface you can also setup<br> SSH access to the virtual machine. See the section called "OpenSSH<br> Server" for more details.<br> -> should also point to the section explaining how to setup bridged<br> networking.</blockquote><div><br>Definitely also added a Virtual Network section detailing setting up a bridge using a static IP address. This seems like it would be the most common scenario for a server, but if I'm wrong on that and we should document more configurations please let me know. <br> </div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> * should we add a brief explanation about "virt-clone" ?</blockquote><div><br>Absolutely, section added.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> <br> * should we document how to create a VM using virt-manager GUI?<br> </blockquote><div><br>Good question, I'm pretty conflicted about that one. It feels like it may fit better into a desktop virtualization section, but if the consensus is that it should be there I'm more than willing to write it.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br> * shouldn't we assume, by default, that there is no GUI on the machine<br> (we are in the server guide, right?)<br> </blockquote><div><br>I've drafted a section on virt-install which allows VM installation without a GUI. Though a machine with a GUI and virt-viewer is required to connect to the virtual machine's console and go through the installation process. From my understanding, from talking with Soren and folks in #virt on OFTC, is that at this time some sort of GUI connection or automated method is needed to install the Guest OS. In a future version it may be possible to attach to the Guest's virtual serial console from a TTY or PTY, and proceed through the installation process that way.<br> <br>If however my understanding is wrong please let me know. I would love to be able to install a VM using nothing more than a SSH connection, that would be the cats pajamas :-).<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> * Fists use of the GUI acronym should present the expanded meaning in<br> parenthesis.</blockquote><div><br>In the Installation section: <br><br> "You either need a way to automate the installation, or a keyboard and monitor will need to be attached to the machine. In the case of virtual machines a Graphical User Interface (GUI) is analogous to using a physical keyboard and mouse."<br> <br>Do you think something should be added to the virt-viewer or virt-manager sections as well? <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> == <a href="http://doc.ubuntu.com/ubuntu/serverguide/C/ubuntu-vm-builder.html" target="_blank">http://doc.ubuntu.com/ubuntu/serverguide/C/ubuntu-vm-builder.html</a> ==<br> * The above command will add the vim application to the virtual<br> machine, and create a qemu image.<br> -> change to: The above command will create a qemu image and add the<br> vim package to the virtual machine.<br> <br> * I do not understand why we use qemu in the example where the default<br> and appropriate choice should be kvm</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><font color="#888888"><br> </font></blockquote></div><br>This section was in a very rough draft state, and was written before I had access to hardware with virtualization extensions. I've reworked the section implementing your suggestions.<br> <br>The changes should be available on the website tomorrow. Thanks again for the feedback Nick, I think the Virtualization section is shaping up nicely.<br clear="all"><br>-- <br>Party On,<br>Adam