I am looking into using XEN on for a Java based app. Is it possible to hook a DomU to a TOE? More specifically a quad port with OpenSSL access, one port on the card to each DomU? --Rich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Richard Sperry wrote:> I am looking into using XEN on for a Java based app. Is it possible to hook > a DomU to a TOE? More specifically a quad port with OpenSSL access, one > port on the card to each DomU?Not yet. This would require driver domains working, and of course the requisite support from the guest OS stack, etc. I believe this is a post-3.0 feature.. thanks, Nivedita _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Richard Sperry wrote: > > I am looking into using XEN on for a Java based app. Is it possible to > > hook a DomU to a TOE? More specifically a quad port with OpenSSL access, > > one port on the card to each DomU? > > Not yet. This would require driver domains working, and of > course the requisite support from the guest OS stack, etc. > I believe this is a post-3.0 feature..Also, I suspect you might not be able to "split" the card between domains in this way. We certainly can''t split different functions of a single PCI card between domains, and I''m not sure that it''s really possible to do in general... You''d ideally want an intelligent NIC that could demultiplex to multiple domains - there are some of these coming onto the market now and they''ll probably get more popular over time. Cheers, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nivedita Singhvi schrieb:> Not yet. This would require driver domains working, and of > course the requisite support from the guest OS stack, etc. > I believe this is a post-3.0 feature..Does this mean that direct access to PCI devices from a privileged domU will not be available in 3.0? I think you call that driver domain in 2.0 (I mean that physdev_dom0_hide and pci=bus,dev,func thing). I hope, someone will be able to clarify this. Greetings, Markus _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Does this mean that direct access to PCI devices from a privileged domU > will not be available in 3.0? I think you call that driver domain in 2.0 > (I mean that physdev_dom0_hide and pci=bus,dev,func thing). > I hope, someone will be able to clarify this.It''ll be available in 3.x at some point. Right now it''s not in 3.0 due to a lack of agreement about how to reimplement it, following a fundamental change in the way PCI is handled. It should return; preferably it''d be before the release if somebody is able to come up with a solution that makes everyone happy. Cheers, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson schrieb:>>Does this mean that direct access to PCI devices from a privileged domU >>will not be available in 3.0? > > It should return; preferably it''d be before the release if somebody is able to > come up with a solution that makes everyone happy.I really hope so! I think that''s a crucial feature for standalone XEN machines as it gives you the same flexibility for virtualized as for non-virtualized machines. If that feature doesn''t make it''s way in 3.0, will there be support for newer kernels in 2.x later on (or at least up to the point where 3.x has the same features as 2.x)? Greetings, Markus _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I really hope so! I think that''s a crucial feature for standalone XEN > machines as it gives you the same flexibility for virtualized as for > non-virtualized machines. > > If that feature doesn''t make it''s way in 3.0, will there be support for > newer kernels in 2.x later on (or at least up to the point where 3.x has > the same features as 2.x)?I''m don''t think that support for newer kernels in 2.x is planned - the trouble, as always, is finding a willing and able maintainer. New releases of Xen tend to divert developer time elsewhere... It''s should be possible (although not ideal) to create some sort of working Xen 3.0 setup for whatever you want until it''s ready to do PCI assignment again. It may still get into the 3.0 release... Cheers, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users