Reading notes about virtualization chapter

Adam Sommer asommer70 at
Sun Mar 16 02:08:08 UTC 2008


Thank you very much for the feedback Nick, I really appreciate it.

>  * To list start a virtual machine:
>  -> remove extra "list"
>  * Similarly, to list start a virtual machine at boot:
>  -> replace extra "list" by "automatically"
>  * The above example assumes that SSH connectivity between the
> management system and has already been configured
>  -> add: and uses ssh keys for authentication.
>  * virt-viewer  does require a GUI to interaface with the virtual machine.
>  -> replace "interaface" by "interface"
>  * consitency: in virtual machine manager section you use
> "" as your example and in Virtual machine viewer
> section you use "hostname".  I believe we should stick to the same
> example.
>  * Be sure and replace web_devel with the appropriate virtual machine
> name.
>  -> replace "and" by "to"

These suggestions have been implemented.  I need to remember to do some
strong proof reading when using cut'n paste... heh.

>  * If configured to use a bridged network interface you can also setup
> SSH access to the virtual machine. See the section called "OpenSSH
> Server" for more details.
>  -> should also point to the section explaining how to setup bridged
> networking.

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.

>  * should we add a brief explanation about "virt-clone" ?

Absolutely, section added.

>  * should we document how to create a VM using virt-manager GUI?

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.

>  * shouldn't we assume, by default, that there is no GUI on the machine
> (we are in the server guide, right?)

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.

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 :-).

>  * Fists use of the GUI acronym should present the expanded meaning in
> parenthesis.

In the Installation section:

  "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."

Do you think something should be added to the virt-viewer or virt-manager
sections as well?

> == ==
>  * The above command will add the vim application to the virtual
> machine, and create a qemu  image.
>  -> change to: The above command will create a qemu  image and add the
> vim package to the virtual machine.
>  * I do not understand why we use qemu in the example where the default
> and appropriate choice should be kvm

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.

The changes should be available on the website tomorrow.  Thanks again for
the feedback Nick, I think the Virtualization section is shaping up nicely.

Party On,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ubuntu-server mailing list