[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Is: Wrap-up Was: VIRTIO - compatibility with different virtualization solutions
Hi, After some email exchange it looks that there is no consensus how VRITIO should work on Xen. There is some hand waiving and some preliminary tests but it is not sufficient to take final decision and put all needed stuff into upcoming VIRTIO specification release. However, it is certain that any solution which will be chosen in upcoming future MUST not break Xen security model, has a good performance and easily integrate with currently existing solutions. Additionally, it looks that that some terms (e.g. physical address) in VIRTIO specification shall be changed to something which is more platform independent (e.g. handle). Although such changes should not lead to changes in currently existing VIRTIO implementations. Taking into account above mentioned things I state that more research and development work is needed. I volunteer to lead this task. Hence I would like to propose that VIRTIO-46 task (Verify that VIRTIO devices could be implemented in Xen environment) should be opened and work on it should be deferred (from formal POV but that does not mean that work should be on hold in real) until next VIRTIO release. Additionally, I would like to rise VIRTIO on Xen issue during Xen Hackathon 2014 and in other avenues to discuss this with other stake holders of VIRTIO. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |