Re: [open-vm-tools-devel] Getting involved

[Elliot L. <el...@vm...>]

On Mon, 2007-10-01 at 18:42 -0500, Justin M. Forbes wrote: 
> > . Implementing a CLI for the tools. Some of this type of work has
> > already been done (see
> > http://chitchat.at.infoseek.co.jp/vmware/ ).
> > 
> This is indeed interesting and a CLI would be most useful from a
> software appliance standpoint.
> 
> > . Making the tools work with qemu, KVM, etc. Anthony Liguori
> > 
> Also interesting work, particularly with KVM.
> 
> > . Packaging on OS's where the code should already work
> >    . Debian
> >    . Fedora
> 
> Add rPath to this list.  I am working on this packaging righ tnow.
> 
> 
> One thing I am curious on.  The kernel modules... Are there any
> intentions to upstream them? I know the virt I/O bits could probably
> eventually replace some of these (vmblock/vmnet).  I am guessing if
> there was a desire to get the vm* drivers upstream, earlier rather than
> later would be best...

Hey Justin, 

Sorry for the lag... I don't have a good official answer off the top of
my head, but those of us inside of VMware have definitely done some
thinking about upstreaming, and I'll do what I can to keep the issue on
the agenda. Hopefully we'll have something more definitive to share with
the rest of the group at some point.

Any particular reason you think earlier is better than later? (Other
than the benefits that come from having the modules upstream in
general... :)

Best,
-- Elliot