From: <xen@wood.id.au>
To: "'Alan C. Oehler'" <alan@xensource.com>,
xen-users@lists.xensource.com, xen-devel@lists.xensource.com
Subject: RE: [Xen-users] Xen 3.0 User Manual revision
Date: Thu, 11 May 2006 14:51:57 +1000 [thread overview]
Message-ID: <00ba01c674b6$a2fe6a10$fe02420a@BDR529> (raw)
In-Reply-To: <002b01c673a9$3fac46c0$03c8a8c0@PAPA>
[-- Attachment #1.1: Type: text/plain, Size: 2701 bytes --]
Hi Alan,
I support the HVM requests others have made. Particularly confusing for me
was that I started with Xen 3.0.2 which seemed to have changed all
references to vmx to hvm including files, this meant I rebuilt xen numerous
times trying to get vmx files (e.g. vmx-builder) when I already had hvm
files (e.g. hvm-builder) and didn't need anything else.
Some ways of telling whether your computer supports hvm, e.g. a simple test
program.
How to move real partitions to file backed partitions.
Using VNC/RDP/SDL.
I think heaps of examples in both networking and HVM would be excellent.
Also some notes about various operating system restrictions about changing
the hardware between reboots and how to avoid those problems.
Links to the Wiki for each section of the manual would be excellent, meaning
you would:
a) hopefully have a more up to date manual just a click away
b) have a handy reference for when you are actually updating the manual
c) harness the community to collect bits for the manual in a place handy for
you
cheers,
Woody
(sorry about top-posting - just going with the flow)
_____
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mito
Sent: Wednesday, 10 May 2006 06:44
To: 'Alan C. Oehler'; xen-users@lists.xensource.com;
xen-devel@lists.xensource.com
Subject: RE: [Xen-users] Xen 3.0 User Manual revision
I would like to see the addition of how to use customized networking. I
finally got NAT networking working, but all documentation that I ran across
was from other sources, the Xen manual doesn't even mention NAT other than
in the sentence that says "other options are available".
Thanks for all your work!
Mito
_____
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Alan C. Oehler
Sent: Tuesday, May 09, 2006 12:46 PM
To: xen-users@lists.xensource.com; xen-devel@lists.xensource.com
Subject: [Xen-users] Xen 3.0 User Manual revision
I'm the tech writer at XenSource and I'm planning to devote some energies to
improving the Xen User Manual. To that end, I'm eliciting feedback from the
community.
Please respond here on the list if you have any notions about how the manual
might be improved, and I'll collect and review the feedback, prioritize it,
and do all I can to move it forward.
* Is anything glaringly omitted from the manual that should be there?
* Are there any sections that are notably incomplete or lacking in clarity?
* Is the current organization of the material reasonable? If not, how would
you like to see it changed?
Thanks very much!
Regards,
Alan C. Oehler
Sr. Technical Writer
XenSource, Inc.
[-- Attachment #1.2: Type: text/html, Size: 11649 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2006-05-11 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 16:46 Xen 3.0 User Manual revision Alan C. Oehler
2006-05-09 17:09 ` Matt Ayres
2006-05-09 19:37 ` Christian Horn
2006-05-09 20:43 ` Mito
2006-05-11 4:43 ` [Xen-users] " Anthony Wood
2006-05-11 4:51 ` xen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00ba01c674b6$a2fe6a10$fe02420a@BDR529' \
--to=xen@wood.id.au \
--cc=alan@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.