All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan de Konink <skinkie@xs4all.nl>
To: jpranevich@kniggit.net
Cc: Stephan Seitz <s.seitz@netz-haut.de>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Almost working iSCSI booting, need advice
Date: Sat, 23 Aug 2008 01:05:55 +0200	[thread overview]
Message-ID: <48AF4653.6030401@xs4all.nl> (raw)
In-Reply-To: <24204720.65851219445637794.JavaMail.root@bos-dom-zbox3.bos.lycos.com>

jpranevich@kniggit.net schreef:
> Without these changes, or at least similar changes, I was never
> getting the hotplug scripts called in my config. Maybe it's because
> I'm using pygrub. Maybe it's some other reason. I traced the
> offending code to bootloader:

I guess here is where the problem is... I never used pygrub before it. 
So if you are hacking in PyGrub you might be in the right place ;)

> If you tell me where in the python code the hotplug scripts are
> supposed to get called from, I'll add copious debugging around that
> point in stock Xen to see what it's doing in my configuration and
> report back or provide a fix.

You ask smart questions... but I don't know 'how' PyGrub does this. And 
actually I have no clue were in the actual booting process PyGrub steps in.

> There are no problems with your block-iscsi scripts. Those are
> perfectly fine. They need tweaked a bit because the kernel
> maintainers keep changing the format and layout of /sys between
> versions, but it should be a simple matter to select the right file
> location. (It seems to be one of two.) I was going to send you a
> patch to do this once I got further along.

;) Yes... I Know ;) The Libvirt guys know it too...

What I asked to the open-iscsi.org guys was to copy there utility 
functions to seperate library something like libopen-iscsi.so and create 
a program that does the /sys operations based on their code.

(It could be interesting to make a block script in plain C, I have 
investigated this route for libvirt storage pools as well... but that 
one has an extra 'issue', it should be able to do the 'tap' interface 
too...)


Stefan

  reply	other threads:[~2008-08-22 23:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <28494896.65231219440780834.JavaMail.root@bos-dom-zbox3.bos.lycos.com>
2008-08-22 21:35 ` Almost working iSCSI booting, need advice jpranevich
2008-08-22 21:41   ` Stefan de Konink
2008-08-22 22:01     ` jpranevich
2008-08-22 22:16       ` Stefan de Konink
2008-08-22 22:53         ` jpranevich
2008-08-22 23:05           ` Stefan de Konink [this message]
     [not found] <26406600.65931219456290998.JavaMail.root@bos-dom-zbox3.bos.lycos.com>
2008-08-23  1:54 ` jpranevich
2008-08-23  2:47   ` Stefan de Konink
2008-08-23 15:04     ` jpranevich
2008-08-23 15:24       ` Stefan de Konink
     [not found] <27772392.69541219682667850.JavaMail.root@bos-dom-zbox3.bos.lycos.com>
2008-08-25 16:53 ` jpranevich
2008-08-25 17:06   ` Stefan de Konink

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48AF4653.6030401@xs4all.nl \
    --to=skinkie@xs4all.nl \
    --cc=jpranevich@kniggit.net \
    --cc=s.seitz@netz-haut.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.