<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I've found an open bug tracking this issue:</div><div><br></div><div><a href="https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855">https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855</a></div><div><br></div><div>I'll move this to launchpad but am sharing here to close the loop for anyone else hunting for a solution. </div><div><br></div><div>./JRH </div><div><br>On Nov 7, 2014, at 15:41, Jason Harley <<a href="mailto:jharley@redmind.ca">jharley@redmind.ca</a>> wrote:<br><br></div><blockquote type="cite"><div><span>I’ve been successfully running KVM in an unrestricted container for some months now. Yesterday I tried to attach an iSCSI device to a VM running in a container, and discovered that there’s some trickery here involving NETLINK namespaces.</span><br><span></span><br><span>I’ve found a few old mailing list posts (one with a patch submitted in 2012[1]) of people running into this same issue and am wondering if there is a solution available (confirmed or in testing), or if one is on the horizon? The LXD announcement seems to suggest this is a problem on the project’s radar as well.\</span><br><span></span><br><span>I’m running kernel 3.13.0-39 and LXC 1.0.6-0ubuntu0.1. Does anyone have a method for giving a privileged container access to initiate iSCSI sessions?</span><br><span></span><br><span>./JRH</span><br><span></span><br><span>1: <a href="http://copilotco.com/mail-archives/open-iscsi.2012/msg00020.html">http://copilotco.com/mail-archives/open-iscsi.2012/msg00020.html</a></span><br></div></blockquote></body></html>