>>> On 8/6/2009 at 9:44 AM, in message <[email protected]>, Avi >>> Kivity <[email protected]> wrote: > On 08/06/2009 04:03 PM, Gregory Haskins wrote: >>> It's true that vbus is a separate project (in fact even virtio is >>> completely separate from kvm). Still I think it would be of interest to >>> many kvm@ readers. >>> >> >> Well, my goal was to not annoy KVM readers. ;) So if you feel as though > there is benefit to having all of KVM CC'd and I won't be annoying everyone, > I see no problem in cross posting. >> > > I can only speak for myself, I'm interested in this project
In that case, the best solution is probably to have you (and anyone else interested) to sign up, then: https://lists.sourceforge.net/lists/listinfo/alacrityvm-devel https://lists.sourceforge.net/lists/listinfo/alacrityvm-users > (though still rooting for virtio). Heh...not to belabor the point to death, but virtio is orthogonal (you keep forgetting that ;). Its really the vbus device-model vs the qemu device-model (and possibly vs the "in-kernel pci emulation" model that I believe Michael is working on). You can run virtio on any of those three. > >> Would you like to see all conversations, or just ones related to code (and, > of course, KVM relevant items) > > I guess internal vbus changes won't be too interesting for most readers, > but new releases, benchmarks, and kvm-related stuff will be welcome on > the kvm list. Ok, I was planning on that anyway. Regards, -Greg -- 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
