[Lxc-users] single root io virtualization

[atp]

Hi,

 There's no reason why you shouldn't be able to use it
with lxc. Looking at the guide here;
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/sect-Para-virtualized_Windows_Drivers_Guide-How_SR_IOV_Libvirt_Works.html

The virtual devices show as virtual pci cards. If you can 
map that to a device (ethN) on the host then you can assign them
to a network namespace or a container. 

 Let us know if it works. 

 Andy


On Wed, 2011-02-23 at 07:02 -0800, siraj rathore wrote:
> Hi
> 
> Many hypervisor based virtualization technologies can use 
> single root IO virtualization(SR-IOV) to improve isolation and 
> performance of virtual machine. 
> 
> Does Linux container also support this?
> 
> Best Regards
> Siraj
> 
> 
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in 
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business 
> insights. http://p.sf.net/sfu/splunk-dev2dev 
> _______________________________________________ Lxc-users mailing list Lxc-users at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users

-- 
Andrew Phillips
Head of Systems

Direct: +44 (0)203 192 2509
Mobile: +44 (0)7595 242 900

LMAX, Yellow Building, 1A Nicholas Road,  London, W11 4AN



The information in this e-mail and any attachment is confidential and is intended only for the named recipient(s). The e-mail may not be disclosed or used by any person other than the addressee, nor may it be copied in any way. If you are not a named recipient please notify the sender immediately and delete any copies of this message. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any view or opinions presented are solely those of the author and do not necessarily represent those of the company.