Greg KH wrote:
It's that "second" part that I'm worried about. How is that going to
happen? Do you have any patches that show this kind of "assignment"?
For kvm, this is in 2.6.28-rc.
Note there are two ways to assign a device to a guest:
- run the VF driver in the guest: this has the advantage of best
performance, but requires pinning all guest memory, makes live migration
a tricky proposition, and ties the guest to the underlying hardware.
- run the VF driver in the host, and use virtio to connect the guest to
the host: allows paging the guest and allows straightforward live
migration, but reduces performance, and hides any features not exposed
by virtio from the guest.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
