The following components have been released as OSS:
•Drivers for devices and filesystems access
•Memory ballooning
•Shared folders
•Drag and Drop, Text and File Copy/Paste
•Clipboard sharing
•Disk wiping and shrinking
•Time synchronization
•Automatic guest screen resolution resizing
•GuestInfo (provides statistics about guest environment)
•Guest SDK (provides information about the VM)
•Soft power operations
•Multiple monitor support
•GTK Toolbox UI
Well, Soft Power Operations would be nice to have, e.g. so you can shut down/reset guest OS from vSpere client.
Can we get a response to this? I have a feeling that you don't even know what I'm doing. Right now, I have a small datacenter in a single server running VMware ESXi.
VMware ESXi is a very sofisticated software solution, you can run a complex network inside it with swirches and VLANs. Right now I have several firewalls inside my VMware server with only one physical network interface, and a VLAN aware switch.
By the way, VMware ESXi is free, so download it and see what it's capable of.
If asking about the benefit for virtualizing, the obious answer is cost (not buying hardware) and easy of managment.
If asking about the actual drivers in the Kernel, well if you have a valid reason for virtualizaing then you will want to optimize the guest OS by using the the native drivers provided by the parent OS partition.
I am assuming that dd-wrt svn tree takes a new version of the kernel everyonce in a while.
If thats the casem then, are you saying that even when the Hyper-V drivers source code (which is GPL btw) is in the dd-wrt svn tree, dd-wrt we will NOT be compiled with Hyper-V drivers.
The Hyper-V drivers will be included in the Linux kernel eventually, Are you going to actively prevent this from happening?
I run my home network off x86 DD-WRT on ESXi and I don't really see any benefit to integrating any VMware Tools functionality into the image, certainly not for the amount of work it would take and the bloat to the image.
