virt-manager currently recommends libvirt-bin, which itself recommends qemu-kvm. Thus, when you install virt-manager (even if you just want to manage remote machines), you get the whole hypervisor stack.
I think I agree with you -- that's wrong. I'm going to fix both of these bugs, lowering these to Suggests in Maverick.
There may be some documentation that needs updating, and perhaps a release note.
We have a couple of meta packages, ubuntu-virt-server and ubuntu-virt-mgmt that should be used instead, if someone wants to install the whole stack.
This is related to Bug #589888.
virt-manager currently recommends libvirt-bin, which itself recommends qemu-kvm. Thus, when you install virt-manager (even if you just want to manage remote machines), you get the whole hypervisor stack.
I think I agree with you -- that's wrong. I'm going to fix both of these bugs, lowering these to Suggests in Maverick.
There may be some documentation that needs updating, and perhaps a release note.
We have a couple of meta packages, ubuntu-virt-server and ubuntu-virt-mgmt that should be used instead, if someone wants to install the whole stack.