All of lore.kernel.org
 help / color / mirror / Atom feed
From: woody <marvel@us.ibm.com>
To: Daniel Stekloff <dsteklof@us.ibm.com>,
	aquynh@gmail.com, xen-devel@lists.xensource.com
Subject: Re: Updated version of VM-Tools and libxen available
Date: Wed, 06 Apr 2005 10:01:11 -0700	[thread overview]
Message-ID: <425415D7.8080103@us.ibm.com> (raw)
In-Reply-To: <200504060949.06240.dsteklof@us.ibm.com>


[-- Attachment #1.1: Type: text/plain, Size: 2611 bytes --]



Daniel Stekloff wrote:

>On Wednesday 06 April 2005 09:29, aq wrote:
>  
>
>>On Apr 6, 2005 9:06 AM, Anthony Liguori <aliguori@us.ibm.com> wrote:
>>    
>>
>>>Hi,
>>>
>>>A new version of VM-Tools and libxen are available for those
>>>interested.  There's a number of new features that I thought some folks
>>>here would be interested in.
>>>
>>>vm-tools:
>>>o VMX support
>>>o vm-top (with SMP support)
>>>o vm-balloon
>>>o many bugfixes
>>>
>>>libxen:
>>>o Use the positive portion of the return code when possible
>>>o Ensure error code is in errno
>>>o Linux build routine
>>>o memext ops
>>>
>>>VM-Tools:
>>>http://www.cs.utexas.edu/users/aliguori/vm-tools-latest.tar.gz
>>>
>>>libxen:
>>>http://www.cs.utexas.edu/users/aliguori/libxen-3.0.1.tar.gz
>>>      
>>>
>>Anthony, I would like to give those code a try. Could you please give
>>us some brief HOWTO guidance for the first steps? Do I need to stop
>>the xend, and run other alternative daemon to use vm-tools?
>>
>>I looked at the tarball, but found no such documentation.
>>    
>>
>
>Hi, 
>
>vm-tools can co-exist with xend, you don't need to stop xend in order to use 
>vm-tools. To get started with it:
>
>1) vm-tools only works with the xeno-unstable tree.
>
>2) untar the tarball
>
>3) make
>
>4) make install
>  
>
** only required as root

>The "vm" script is intended to work like "xm". For more information on how to 
>use the commands, you can:
>
>1) Use man pages (They need some updating)
>  # man vm
>  
>
* definitely out of sync but the usage should be current. Try --help or -h

>2) Use help options for syntax
> # vm help
>
>3) Read the documenation in the docs directory
>
>Some basic tasks:
>
>1) Creating a domain - vm create CONFIG
> # vm create /etc/xen/vm1
>
>2) Listing domains - vm list
> # vm list
>
>3) Shutting down a domain - vm shutdown DOMID
> # vm shutdown 3
>
>
>The vm-tools are still being developed. There does need to be an installation 
>instruction added - either as a file INSTALL or in the README. A short HOWTO 
>might also help. We'll be sure to add it.
>
>Thanks,
>
>Dan
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

-- 
Sincerely, Woody Marvel   LTC Open Source Projects   Beaverton, OR
tel: 503-578-3833/775-3833	email: marvel@us.ibm.com
=======================================================================
"The branch is not only ever near the stem, but ever receiving life and fruitfulness from it." -- C.H.Spurgeon
=======================================================================


[-- Attachment #1.2: Type: text/html, Size: 3793 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2005-04-06 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06  0:06 Updated version of VM-Tools and libxen available Anthony Liguori
2005-04-06  0:28 ` Michael Hohnbaum
2005-04-06 16:29 ` aq
2005-04-06 16:49   ` Daniel Stekloff
2005-04-06 16:59     ` Daniel Stekloff
2005-04-06 17:01     ` woody [this message]
2005-04-11 14:47       ` aq
2005-04-11 14:34         ` Mark Williamson
2005-04-06 17:41   ` Scott Parish
2005-04-08  3:03 ` Jacob Gorm Hansen

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=425415D7.8080103@us.ibm.com \
    --to=marvel@us.ibm.com \
    --cc=aquynh@gmail.com \
    --cc=dsteklof@us.ibm.com \
    --cc=xen-devel@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.