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 04:47:36 +0200 [thread overview]
Message-ID: <48AF7A48.7010300@xs4all.nl> (raw)
In-Reply-To: <29618583.65951219456441096.JavaMail.root@bos-dom-zbox3.bos.lycos.com>
jpranevich@kniggit.net schreef:
> ----- "Stefan de Konink" <skinkie@xs4all.nl> wrote:
>
>> 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 ;)
>>
>
> Can you tell me what bootloader you are using and whether you have
> any patches on top of stock Xen, particularly in XendDomainInfo.py or
> XendBootloader.py?
I hope you don't cry now, but I'm not using any bootloader :) I really
can't see the use for it. Actually I have *two* kernels now, but the
only thing my users see is an linux-2.6 as kernel in their config.
> (As an aside, Xen really does seem intent on thinking that you need a
> real block device to boot from in a few other areas. I was playing
> around and was able to get RedHat AS 5.2's newly-added root-on-iSCSI
> support working under Xen without any code modifications using the
> SuSE domUloader and RedHat's initrd and kernel, but I still had to
> specify a block device, even though it's ignored by the initrd which
> has its own mini-open-iscsi built in and mounts root from that. The
> RedHat support has too many limitations to be practical for Xen just
> yet, but it's an interesting different approach. Still, having Xen
> manage the iSCSI connections appears to be the best way.)
Oh they are doing:
kernel initrd-hey-here-are-the-iscsi-tools-lets-switch-rootfs
Instead the nfsway:
kernel-lets-find-a-nice-iscsi-machine
Not only the best way, the only way you can *safely* hide your storage
from the domU's.
Stefan
next prev parent reply other threads:[~2008-08-23 2:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26406600.65931219456290998.JavaMail.root@bos-dom-zbox3.bos.lycos.com>
2008-08-23 1:54 ` Almost working iSCSI booting, need advice jpranevich
2008-08-23 2:47 ` Stefan de Konink [this message]
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
[not found] <28494896.65231219440780834.JavaMail.root@bos-dom-zbox3.bos.lycos.com>
2008-08-22 21:35 ` 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
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=48AF7A48.7010300@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.