I am reviving this rather old thread (and breaking all manner of etiquette,
I'm sure) to ask if anyone knows the status of getting the iSCSI Netlink
code namespace aware? I'm happy to try "experimental" patches, aelnd help
QA things as having iSCSI support from inside an Linux Container (LXC)
I didn't know that a iscsi sysfs per namespace would be required but it
doesn't
surprise me now that you mention it. Right now, I have access to all iscsi
sysfs data from any lxc container - would this suffice to just get the iscsi
initiator operational in a container?
On Wed, Jan 11, 2012 at 3:58
On 01/11/2012 02:55 PM, Mike Christie wrote:
> On 01/11/2012 01:14 PM, Patrick Mullaney wrote:
>> I tried this patch and iscsid ends up in a tightloop in the kernel. I
>> attempted some
>> basic debugging and it definitely gets beyond my previous issue but then
>> locks.
>>
>> I also attempted to c
On 01/11/2012 01:14 PM, Patrick Mullaney wrote:
> I tried this patch and iscsid ends up in a tightloop in the kernel. I
> attempted some
> basic debugging and it definitely gets beyond my previous issue but then
> locks.
>
> I also attempted to change the patch around such that the netlink socket
I tried this patch and iscsid ends up in a tightloop in the kernel. I
attempted some
basic debugging and it definitely gets beyond my previous issue but then
locks.
I also attempted to change the patch around such that the netlink socket
that
gets create per net namespace is kept with the namespac
On 01/05/2012 08:38 PM, Mike Christie wrote:
> On 12/28/2011 02:36 AM, Mike Christie wrote:
>> On 12/22/2011 04:44 PM, pmullaney wrote:
>>> Hi all,
>>>
>>> Running into problems running under lxc. I am running iscsid in the
>>> container and when it
>>> attempts to connect to the netlink iscsi sock
On 12/28/2011 02:36 AM, Mike Christie wrote:
> On 12/22/2011 04:44 PM, pmullaney wrote:
>> Hi all,
>>
>> Running into problems running under lxc. I am running iscsid in the
>> container and when it
>> attempts to connect to the netlink iscsi socket it is getting a
>> connection refused(111) and
>>
Sure - here is a run with debug level 7 on from within a container:
tenant199-vm3:/open-iscsi-2.0-
872 # /sbin/iscsid -f -d 7 -c /etc/iscsi/iscsid.conf &
[1] 1508
tenant199-vm3:/open-iscsi-2.0-872 # iscsid: sysfs_init: sysfs_path='/sys'
iscsid: sysfs_attr_get_value: open '/module/scsi_transport_i
On 12/29/2011 08:08 AM, Patrick Mullaney wrote:
> I ran the stock sles lxc(0.6.5), tried the latest on sourceforge and the
> most recent stable - all
> had the same result. I was just about to try to put some debug code in the
> netlink
> code. So I'd be interested in any patch you would be nice e
I ran the stock sles lxc(0.6.5), tried the latest on sourceforge and the
most recent stable - all
had the same result. I was just about to try to put some debug code in the
netlink
code. So I'd be interested in any patch you would be nice enough to send -
thanks!
On Wed, Dec 28, 2011 at 5:35 PM, M
On 12/28/2011 04:10 PM, Patrick Mullaney wrote:
> I am using sles11sp1. My kernel is 2.6.32.49-0.3-default.
>
> I tried the packages that came with sles11sp1 as a start and ran into the
> issue. I am currently using
> my own build of open-iscsi-2.0-872 and I have tried building from head of
> the
I am using sles11sp1. My kernel is 2.6.32.49-0.3-default.
I tried the packages that came with sles11sp1 as a start and ran into the
issue. I am currently using
my own build of open-iscsi-2.0-872 and I have tried building from head of
the git repo,
both with the same result.
I have been able to ge
On 12/22/2011 04:44 PM, pmullaney wrote:
> Hi all,
>
> Running into problems running under lxc. I am running iscsid in the
> container and when it
> attempts to connect to the netlink iscsi socket it is getting a
> connection refused(111) and
> the following in the log:
>
> sendmsg: bug? ctrl_fd
Hi all,
Running into problems running under lxc. I am running iscsid in the
container and when it
attempts to connect to the netlink iscsi socket it is getting a
connection refused(111) and
the following in the log:
sendmsg: bug? ctrl_fd 5
which causes iscsid to exit.
Any thoughts on what could
14 matches
Mail list logo
