On Fri, Jun 10, 2011 at 10:12:50AM -0500, Michael Cronenworth wrote:
> Richard W.M. Jones wrote:
> > They are available, but I think you have to build them yourself from
> > source.  All the information is here:
> This is not an argument for libvirt/kvm/qemu/spice but against.
> Here's some constructive advice:
> 1. Give the Red Hat virtualization tools one, unique name and package it 
> under that name. Having a new name for every new feature isn't helping 
> your cause. Call it "RHVM" even. Anything is better than the current 
> situation and I'm sure a marketing wizard would love to tackle this.
> 2. Make guest additions dead simple to install. Having to compile them 
> with a Windows DDK is not dead simple.
> 3. Transparent network access. Having to setup bridges or manually edit 
> config files is a big turn off to some folks. I know virt-manager has a 
> GUI for some operations, but I still see editing config files a 
> recommended method in recent mailing list postings.
> 4. Support USB 2.0+ in a easy-to-use way. Under VB, I can just click on 
> a device I want to use, while the VM is running, and use it. When I'm 
> done, I uncheck the device, again, while the VM is running, and it 
> disconnects from the VM and returns for use to my Fedora box.
> 5. Exporting VMs must be a two-click process. Not a 9 command, terminal 
> operation. Importing VMs must be just as easy.

As they say, you get what you pay for.

Customers ask us to make the changes they want -- for server use and
scalability -- and KVM is absolutely the best in that area as a
result.  See many recent benchmarks.

Usability on single desktops is, well ... we do our best.

If you want excellent desktop usability, then organize a group and
make the work and patches happen.


Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
devel mailing list

Reply via email to