etherboot-discuss — General Etherboot Discussion

[Etherboot-discuss] SRP timeout

[Matthew L. <ml...@sh...>]

I'm receiving a connection timed out error while trying to boot from a SRP target. The same SRP target works perfectly under a locally running OS (tested in Linux and Windows).

My setup includes one Linux box connected in a back-to-back configuration to a desktop. My goal is to boot the desktop from the Linux server's fast raid array. Each computer has a Mellanox MHES18-XTC (MT25204) card in it, which is running the latest firmware. I've followed the instructions for SRP booting in the Wiki. I think my problem is related to the arbel driver. 

On boot gPXE loads fine, it loads the arbel driver, it detects the card, it obtains an IP address from the DHCP server, gets the root-path string and then attempts a sanboot. This is where it times out.

To troubleshoot I compiled gPXE with DEBUG=srp:3 and only got more frequent reporting of the timeout error. The following set of messages repeat several times:

SRP 0x1d9d4 TX request tag 00000000000000000000001b SRP 0x1d9d4 socket closed: Connection timed out (0x4c206035)

The Linux box is a little more helpful. As we can see below, the connection is established just fine, but eventually times out on this end too. 

Any help would be greatly appreciated.

- Matt

[24923.754700] [19451]: scst: scst_register_target:469:Target ib_srpt_target_4 (rel ID 5) for template ib_srpt registered successfully
[24955.191467] ib_srpt: Received SRP_LOGIN_REQ with i_port_id 0x0:0x2c9020021b829, t_port_id 0x2c9020021b8d0:0x2c9020021b8d0 and it_iu_len 80 on port 1 (guid=0xfe80000000000000:0x2c9020021b8d1)
[24955.192272] [1207]: scst: scst_init_session:6166:Using security group "Default" for initiator "0x00000000000000000002c9020021b829"
[24955.192282] [1207]: scst_alloc_add_tgt_dev:2976:Device vdisk0 on SCST lun=0
[24955.192290] [1207]: scst_alloc_set_UA:6004:Adding new UA to tgt_dev ffff8800d77928a0
[24955.192537] [19457]: scst: scst_cmd_thread:4171:Processing thread vdisk00_0 (PID 19457) started
[24955.192546] [19457]: scst_cmd_thread:4192:Alloced new IO context ffff88004b1bfbd0 (p_cmd_threads ffff8800d7792990)
[24955.192573] [19458]: scst: scst_cmd_thread:4171:Processing thread vdisk00_1 (PID 19458) started
[24955.192576] [19458]: scst_cmd_thread:4211:Linked IO context ffff88004b1bfbd0 (p_cmd_threads ffff8800d7792990)
[24955.192588] [19459]: scst: scst_cmd_thread:4171:Processing thread vdisk00_2 (PID 19459) started
[24955.192591] [19459]: scst_cmd_thread:4211:Linked IO context ffff88004b1bfbd0 (p_cmd_threads ffff8800d7792990)
[24955.192599] [19460]: scst: scst_cmd_thread:4171:Processing thread vdisk00_3 (PID 19460) started
[24955.192601] [19460]: scst_cmd_thread:4211:Linked IO context ffff88004b1bfbd0 (p_cmd_threads ffff8800d7792990)
[24955.192612] [19461]: scst: scst_cmd_thread:4171:Processing thread vdisk00_4 (PID 19461) started
[24955.192615] [19461]: scst_cmd_thread:4211:Linked IO context ffff88004b1bfbd0 (p_cmd_threads ffff8800d7792990)
[24955.192622] [19462]: scst: scst_cmd_thread:4171:Processing thread vdisk00_5 (PID 19462) started
[24955.192625] [19462]: scst_cmd_thread:4211:Linked IO context ffff88004b1bfbd0 (p_cmd_threads ffff8800d7792990)
[24955.192637] [19463]: scst: scst_cmd_thread:4171:Processing thread vdisk00_6 (PID 19463) started
[24955.192641] [19463]: scst_cmd_thread:4211:Linked IO context ffff88004b1bfbd0 (p_cmd_threads ffff8800d7792990)
[24955.192659] [19464]: scst: scst_cmd_thread:4171:Processing thread vdisk00_7 (PID 19464) started
[24955.192663] [19464]: scst_cmd_thread:4211:Linked IO context ffff88004b1bfbd0 (p_cmd_threads ffff8800d7792990)
[24967.090591] ib_srpt: Received SRP_LOGIN_REQ with i_port_id 0x0:0x2c9020021b829, t_port_id 0x2c9020021b8d0:0x2c9020021b8d0 and it_iu_len 80 on port 1 (guid=0xfe80000000000000:0x2c9020021b8d1)
[24967.090601] [1207]: scst_unregister_session:6380:Unregistering session ffff880015b0c9c0 (wait 0)
[24967.090610] [1207]: scst_rx_mgmt_fn:5907:TM fn 10
[24967.090614] [1207]: scst_rx_mgmt_fn:5917:sess=ffff880015b0c9c0, tag_set 0, tag 0, lun_set 1, lun=0, cmd_sn_set 0, cmd_sn 0, priv (null)
[24967.090622] [1207]: scst_post_rx_mgmt_cmd:5836:Adding mgmt cmd ffff8801154a8958 to active mgmt cmd list
[24967.090630] ib_srpt: ***ERROR***: rejected SRP_LOGIN_REQ because another login request is being processed.
[24967.090734] [4319]: scst_tm_thread:5722:Deleting mgmt cmd ffff8801154a8958 from active cmd list
[24967.090738] [4319]: scst_abort_all_nexus_loss_sess:5280:Nexus loss for sess ffff880015b0c9c0 (mcmd ffff8801154a8958)
[24967.090742] [4319]: scst_call_dev_task_mgmt_fn:4540:Calling dev handler vdisk_fileio task_mgmt_fn(fn=10)
[24967.090745] [4319]: scst_call_dev_task_mgmt_fn:4544:Dev handler vdisk_fileio task_mgmt_fn() returned 1

[Etherboot-discuss] VMWare ESXi 4 NVRAM Settings e1000

[Bob Q. <bqp...@gm...>]

I've managed to get the BIOS loaded and to get a VM to boot from my SAN, but
I'd really love if the NVRAM settings would work.

Do these not work with vmware e1000 adapters?

I try to set using config net0.nvo and sometimes it will give me an error,
sometimes it will let me change settings.

Either way nothing saves on reboot.

The iscsi is on a network with another DHCP server that I don't want to have
to alter (and I would like static ips and initiator iqns)

Re: [Etherboot-discuss] cannot boot from usb

[Marty C. <md...@et...>]

Hi Chantal,

You should join the gp...@et... mailing list:

    http://etherboot.org/mailman/listinfo/gpxe

where there are more people who are actively using gPXE and will be 
happy to hear from you.

I thought we had an appnote on our wiki that talked about how to create 
a USB stick that is bootable with either a DOS or Linux (ext2/ext3) file 
system on it.

gPXE's .usb format is sometimes confusing to systems, and I sometimes 
use a FreeDOS formatted memory stick to put a copy of syslinux.

There are lots of tutorials on the web about making USB drives DOS 
bootable.  Things like:

    http://wiki.fdos.org/Installation/BootDiskCreateUSB

Once you have a DOS bootable USB drive you can put Syslinux on it, and 
updating the drive becomes as easy as copying a new .lkr[n] file to the 
USB drive.

Who else uses a DOS formatted USB driver for USB booting gPXE?

/ Marty /

P.S.  For fun, build a gPXE  .iso formatted image and look at the files 
on it. :)  Something very similar could be used with a USB stick and DOS.

ch...@an... wrote on 6/3/10 9:14 AM:
> Thanks Andrew,
>
> The machines are pretty old so it is possible that usb boot is not
> supported (although I can choose USB in the boot order), I "fixed" it
> by using a floppy disk image instead.
>
>
> Quoting ru...@gm...:
>
>> Hello Chantal,
>>
>> If you're getting a black screen now and the BIOS boot order doesn't
>> continue on to the hard disk, it appears as though your USB stick is
>> indeed  being booted by the BIOS insofar as [attempted] execution of
>> the MBR code,  but curiously you're not getting any farther than that.
>>
>> Of course, the newer a motherboard is, the more likely you'll be able
>> to  successfully boot via USB, but ensuring a USB boot is not always
>> the  easiest thing to do. That said, could you verify that the stick
>> works by  booting it directly in a virtual machine or from another
>> computer which  you've known to successfully boot USB sticks? Apologies
>> if you're already  certain that the machine you're attempting to boot
>> currently should work :-P
>>
>> Otherwise speaking, I'd suggest erasing and attempting to rewrite the
>> .usb  image to the stick or some such. I'm not too knowledgeable on
>> troubleshooting this particular issue, but just wanted to offer you
>> some  steps you might like to take.
>>
>> Regards,
>> Andrew Bobulsky
>>
>>
>>
>> On Jun 3, 2010 8:19am, ch...@an... wrote:
>>> Ofcourse you are right, i feel a bit stupid now! But still no
>>
>>> luck........ it doesn't boot from the harddisk anymore but I get a
>>
>>> black screen and nothing happens.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>> Quoting Thomas Miletich tho...@gm...>:
>>
>>
>>
>>>> Hi
>>
>>>> As far as I remember, the .usb image is supposed to be written to the
>>
>>>> entire usb drive, instead of a partition on the usb drive. You can
>>
>>>> either use the .hd image type and write it to sdb1, or use the usb
>>
>>>> image and write it to sdb, instead of sdb1:
>>
>>>>
>>
>>>> sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb
>>
>>>>
>>
>>>> Please keep in mind that this will destroy the current partition table
>>
>>>> and any filesystem that may be on the usb drive. If you want to keep
>>
>>>> the filesystem, you may be interested in instaling syslinux or grub on
>>
>>>> the drive and use the .lkrn image type.
>>
>>>>
>>
>>>> Thomas
>>
>>>>
>>
>>>> On Thu, Jun 3, 2010 at 12:33 PM, ch...@an...>  wrote:
>>
>>>>> Hi list,
>>
>>>>>
>>
>>>>> I use Ubuntu 10.04
>>
>>>>>
>>
>>>>>
>>
>>>>> I downloaded an usb image from http://rom-o-matic.net/ and wrote it
>>> to  usb:
>>
>>>>>
>>
>>>>> sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb1

Re: [Etherboot-discuss] cannot boot from usb

[<ch...@an...>]

Thanks Andrew,

The machines are pretty old so it is possible that usb boot is not  
supported (although I can choose USB in the boot order), I "fixed" it  
by using a floppy disk image instead.


Quoting ru...@gm...:

> Hello Chantal,
>
> If you're getting a black screen now and the BIOS boot order doesn't
> continue on to the hard disk, it appears as though your USB stick is
> indeed  being booted by the BIOS insofar as [attempted] execution of
> the MBR code,  but curiously you're not getting any farther than that.
>
> Of course, the newer a motherboard is, the more likely you'll be able
> to  successfully boot via USB, but ensuring a USB boot is not always
> the  easiest thing to do. That said, could you verify that the stick
> works by  booting it directly in a virtual machine or from another
> computer which  you've known to successfully boot USB sticks? Apologies
> if you're already  certain that the machine you're attempting to boot
> currently should work :-P
>
> Otherwise speaking, I'd suggest erasing and attempting to rewrite the
> .usb  image to the stick or some such. I'm not too knowledgeable on
> troubleshooting this particular issue, but just wanted to offer you
> some  steps you might like to take.
>
> Regards,
> Andrew Bobulsky
>
>
>
> On Jun 3, 2010 8:19am, ch...@an... wrote:
>> Ofcourse you are right, i feel a bit stupid now! But still no
>
>> luck........ it doesn't boot from the harddisk anymore but I get a
>
>> black screen and nothing happens.
>
>
>
>
>
>
>
>
>
>> Quoting Thomas Miletich tho...@gm...>:
>
>
>
>>> Hi
>
>>> As far as I remember, the .usb image is supposed to be written to the
>
>>> entire usb drive, instead of a partition on the usb drive. You can
>
>>> either use the .hd image type and write it to sdb1, or use the usb
>
>>> image and write it to sdb, instead of sdb1:
>
>>>
>
>>> sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb
>
>>>
>
>>> Please keep in mind that this will destroy the current partition table
>
>>> and any filesystem that may be on the usb drive. If you want to keep
>
>>> the filesystem, you may be interested in instaling syslinux or grub on
>
>>> the drive and use the .lkrn image type.
>
>>>
>
>>> Thomas
>
>>>
>
>>> On Thu, Jun 3, 2010 at 12:33 PM, ch...@an...> wrote:
>
>>>> Hi list,
>
>>>>
>
>>>> I use Ubuntu 10.04
>
>>>>
>
>>>>
>
>>>> I downloaded an usb image from http://rom-o-matic.net/ and wrote it
>> to  usb:
>
>>>>
>
>>>> sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb1
>
>>>>
>
>>>> I changed the bios to boot from the usb but it doesn't work. It goes
>
>>>> to the next boot device (harddisk). I'm sure I changed the boot order
>
>>>> in the bios correctly.
>
>>>>
>
>>>> Thanks
>
>>>>
>
>>>>
>
>>>>
>
>>>>
>
>>>>
>
>>>>
>
>>>>
>
>>>>
>> ------------------------------------------------------------------------------
>
>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>
>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>
>>>> lucky parental unit. See the prize list and enter to win:
>
>>>> http://p.sf.net/sfu/thinkgeek-promo
>
>>>> _______________________________________________
>
>>>> Etherboot-discuss mailing list
>
>>>> Eth...@li...
>
>>>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>
>>>>
>
>>>
>
>>>
>> ------------------------------------------------------------------------------
>
>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>
>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>
>>> lucky parental unit. See the prize list and enter to win:
>
>>> http://p.sf.net/sfu/thinkgeek-promo
>
>>> _______________________________________________
>
>>> Etherboot-discuss mailing list
>
>>> Eth...@li...
>
>>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>
>>>
>
>
>
>
>
>
>
>> ------------------------------------------------------------------------------
>
>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>
>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>
>> lucky parental unit. See the prize list and enter to win:
>
>> http://p.sf.net/sfu/thinkgeek-promo
>
>> _______________________________________________
>
>> Etherboot-discuss mailing list
>
>> Eth...@li...
>
>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss

Re: [Etherboot-discuss] cannot boot from usb

[<ru...@gm...>]

Hello Chantal,

If you're getting a black screen now and the BIOS boot order doesn't  
continue on to the hard disk, it appears as though your USB stick is indeed  
being booted by the BIOS insofar as [attempted] execution of the MBR code,  
but curiously you're not getting any farther than that.

Of course, the newer a motherboard is, the more likely you'll be able to  
successfully boot via USB, but ensuring a USB boot is not always the  
easiest thing to do. That said, could you verify that the stick works by  
booting it directly in a virtual machine or from another computer which  
you've known to successfully boot USB sticks? Apologies if you're already  
certain that the machine you're attempting to boot currently should work :-P

Otherwise speaking, I'd suggest erasing and attempting to rewrite the .usb  
image to the stick or some such. I'm not too knowledgeable on  
troubleshooting this particular issue, but just wanted to offer you some  
steps you might like to take.

Regards,
Andrew Bobulsky



On Jun 3, 2010 8:19am, ch...@an... wrote:
> Ofcourse you are right, i feel a bit stupid now! But still no

> luck........ it doesn't boot from the harddisk anymore but I get a

> black screen and nothing happens.









> Quoting Thomas Miletich tho...@gm...>:



> > Hi

> > As far as I remember, the .usb image is supposed to be written to the

> > entire usb drive, instead of a partition on the usb drive. You can

> > either use the .hd image type and write it to sdb1, or use the usb

> > image and write it to sdb, instead of sdb1:

> >

> > sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb

> >

> > Please keep in mind that this will destroy the current partition table

> > and any filesystem that may be on the usb drive. If you want to keep

> > the filesystem, you may be interested in instaling syslinux or grub on

> > the drive and use the .lkrn image type.

> >

> > Thomas

> >

> > On Thu, Jun 3, 2010 at 12:33 PM, ch...@an...> wrote:

> >> Hi list,

> >>

> >> I use Ubuntu 10.04

> >>

> >>

> >> I downloaded an usb image from http://rom-o-matic.net/ and wrote it to  
> usb:

> >>

> >> sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb1

> >>

> >> I changed the bios to boot from the usb but it doesn't work. It goes

> >> to the next boot device (harddisk). I'm sure I changed the boot order

> >> in the bios correctly.

> >>

> >> Thanks

> >>

> >>

> >>

> >>

> >>

> >>

> >>

> >>  
> ------------------------------------------------------------------------------

> >> ThinkGeek and WIRED's GeekDad team up for the Ultimate

> >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the

> >> lucky parental unit. See the prize list and enter to win:

> >> http://p.sf.net/sfu/thinkgeek-promo

> >> _______________________________________________

> >> Etherboot-discuss mailing list

> >> Eth...@li...

> >> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss

> >>

> >

> >  
> ------------------------------------------------------------------------------

> > ThinkGeek and WIRED's GeekDad team up for the Ultimate

> > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the

> > lucky parental unit. See the prize list and enter to win:

> > http://p.sf.net/sfu/thinkgeek-promo

> > _______________________________________________

> > Etherboot-discuss mailing list

> > Eth...@li...

> > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss

> >







> ------------------------------------------------------------------------------

> ThinkGeek and WIRED's GeekDad team up for the Ultimate

> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the

> lucky parental unit. See the prize list and enter to win:

> http://p.sf.net/sfu/thinkgeek-promo

> _______________________________________________

> Etherboot-discuss mailing list

> Eth...@li...

> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss

Re: [Etherboot-discuss] cannot boot from usb

[<ch...@an...>]

Ofcourse you are right, i feel a bit stupid now! But still no  
luck........ it doesn't boot from the harddisk anymore but I get a  
black screen and nothing happens.




Quoting Thomas Miletich <tho...@gm...>:

> Hi
> As far as I remember, the .usb image is supposed to be written to the
> entire usb drive, instead of a partition on the usb drive. You can
> either use the .hd image type and write it to sdb1, or use the usb
> image and write it to sdb, instead of sdb1:
>
> sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb
>
> Please keep in mind that this will destroy the current partition table
> and any filesystem that may be on the usb drive. If you want to keep
> the filesystem, you may be interested in instaling syslinux or grub on
> the drive and use the .lkrn image type.
>
> Thomas
>
> On Thu, Jun 3, 2010 at 12:33 PM,  <ch...@an...> wrote:
>> Hi list,
>>
>> I use Ubuntu 10.04
>>
>>
>> I downloaded an usb image from http://rom-o-matic.net/ and wrote it to usb:
>>
>> sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb1
>>
>> I changed the bios to boot from the usb but it doesn't work. It goes
>> to the next boot device (harddisk). I'm sure I changed the boot order
>> in the bios correctly.
>>
>> Thanks
>>
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>> lucky parental unit.  See the prize list and enter to win:
>> http://p.sf.net/sfu/thinkgeek-promo
>> _______________________________________________
>> Etherboot-discuss mailing list
>> Eth...@li...
>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Etherboot-discuss mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>

Re: [Etherboot-discuss] cannot boot from usb

[Thomas M. <tho...@gm...>]

Hi
As far as I remember, the .usb image is supposed to be written to the
entire usb drive, instead of a partition on the usb drive. You can
either use the .hd image type and write it to sdb1, or use the usb
image and write it to sdb, instead of sdb1:

sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb

Please keep in mind that this will destroy the current partition table
and any filesystem that may be on the usb drive. If you want to keep
the filesystem, you may be interested in instaling syslinux or grub on
the drive and use the .lkrn image type.

Thomas

On Thu, Jun 3, 2010 at 12:33 PM,  <ch...@an...> wrote:
> Hi list,
>
> I use Ubuntu 10.04
>
>
> I downloaded an usb image from http://rom-o-matic.net/ and wrote it to usb:
>
> sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb1
>
> I changed the bios to boot from the usb but it doesn't work. It goes
> to the next boot device (harddisk). I'm sure I changed the boot order
> in the bios correctly.
>
> Thanks
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Etherboot-discuss mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>

[Etherboot-discuss] cannot boot from usb

[<ch...@an...>]

Hi list,

I use Ubuntu 10.04


I downloaded an usb image from http://rom-o-matic.net/ and wrote it to usb:

sudo dd if=gpxe-1.0.0-sis900.usb of=/dev/sdb1

I changed the bios to boot from the usb but it doesn't work. It goes  
to the next boot device (harddisk). I'm sure I changed the boot order  
in the bios correctly.

Thanks

Re: [Etherboot-discuss] Network-Install Windows 7 to iSCSI target

[Marty C. <md...@et...>]

Hi Bernhard,

Thanks for your question.  I suggest you join the gp...@et... 
list and ask there.  There are quite a few people on that list who can help.

Here is the mailing list subscription link:

   http://etherboot.org/mailman/listinfo/gpxe

Regards,

/ Marty /

Bernhard Steiner wrote on 5/19/10 7:53 AM:
> Hi gPXE fellas;
> I hope its okay writing to you gPXE guys, knowing that I use gPXE out of the SYSLINUX package.
>
> I'm successfully using the SYSLINUX version of gPXE, called 'gpxelinux.0', to boot Windows from iSCSI.  Right now, I install Windows to a hard drive first, and then I use 'dd' to move the image of the HD to my iSCSI target.  But I like to go a step further…
>
> I'd like to boot from network, connect to a iSCSI target, and then start the installation of the OS from network, too.
>
> What I'm doing at the moment…
>
> 1) Boot server hands 'gpxelinux.0' (chain-loading pxelinux after gpxe) to my PXE clients
> 2) In my PXELINUX (using sanboot.c32 module of SYSLINUX) menu I select an empty iSCSI target
> 3) I get a "SAN boot failed" message, because the iSCSI target I'm trying to boot is empty.
> 4) Then I fall back to my PXELINUX menu, and now I select the entry to start WDS (Windows Deployment Services)
> 5) But when Windows 7 Setup asks for an installation destination, there are no hard drives…
>
> I already tried to set the "KEEP-SAN" option (175 gPXE_options: 08 01 01 FF) in my MS-DHCP server, but without any positive change.
>
> My question to you guys is:
> Is it possible to use gPXE to mount an empty iSCSI disk and then proceed with installing an OS (e.g. Linux, Windows, …) from network?
>
> Thanks,
> Bernhard

[Etherboot-discuss] Fwd: Network-Install Windows 7 to iSCSI target

[Andrew B. <ru...@gm...>]

Forgot to CC the mailing list :)

Also, the Etherboot-discuss list has been deprecated (?), you'll want to continue this on gp...@et...

-Andrew Bobulsky

Begin forwarded message:

> From: Andrew Bobulsky <Ru...@gm...>
> Date: May 19, 2010 10:25:34 AM EDT
> To: "Bernhard Steiner" <ber...@ee...>
> Subject: Re: [Etherboot-discuss] Network-Install Windows 7 to iSCSI target
> 
> Bernhard,
> 
> I've actually done this before, but the process was more than cumbersome... it was a bit of a nightmare.
> 
> Basically, you want gPXE to pull its DHCP request, attempt to boot from SAN, and then of course fall back to gPXE.  After that, you'll want to do something like "chain boot\pxeboot.n12" from the gPXE CLI or a gPXE script.  
> 
> Even then, though, I had problems with Windows Setup that required me to bust open the wim file and edit a few things, then start setup.exe by hand from the PE's command prompt.
> 
> It's a bit of a pain, and I honestly can't remember specifically what I did to make it work right, but I'll try to give you some help along the way if you're willing to stumble along ;-)
> 
> Also, I was chainloading undionly.pxe from the built in pxe.  I think the key here for you is likely loading WinPE from the gPXE CLI, rather than jumping back out to SYSLINUX.
> 
> Best of luck to you.
> 
> -Andrew Bobulsky
> 
> On May 19, 2010, at 7:53 AM, Bernhard Steiner wrote:
> 
>> Hi gPXE fellas;
>> I hope its okay writing to you gPXE guys, knowing that I use gPXE out of the SYSLINUX package.  
>>  
>> I'm successfully using the SYSLINUX version of gPXE, called 'gpxelinux.0', to boot Windows from iSCSI.  Right now, I install Windows to a hard drive first, and then I use 'dd' to move the image of the HD to my iSCSI target.  But I like to go a step further…
>>  
>> I'd like to boot from network, connect to a iSCSI target, and then start the installation of the OS from network, too.
>>  
>> What I'm doing at the moment…
>>  
>> 1) Boot server hands 'gpxelinux.0' (chain-loading pxelinux after gpxe) to my PXE clients
>> 2) In my PXELINUX (using sanboot.c32 module of SYSLINUX) menu I select an empty iSCSI target
>> 3) I get a "SAN boot failed" message, because the iSCSI target I'm trying to boot is empty.
>> 4) Then I fall back to my PXELINUX menu, and now I select the entry to start WDS (Windows Deployment Services)
>> 5) But when Windows 7 Setup asks for an installation destination, there are no hard drives…
>>  
>> I already tried to set the "KEEP-SAN" option (175 gPXE_options: 08 01 01 FF) in my MS-DHCP server, but without any positive change.
>>  
>> My question to you guys is:
>> Is it possible to use gPXE to mount an empty iSCSI disk and then proceed with installing an OS (e.g. Linux, Windows, …) from network?
>>  
>> Thanks,
>> Bernhard
>>  
>> ------------------------------------------------------------------------------
>> 
>> _______________________________________________
>> Etherboot-discuss mailing list
>> Eth...@li...
>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
> 

[Etherboot-discuss] Network-Install Windows 7 to iSCSI target

[Bernhard S. <ber...@ee...>]

Hi gPXE fellas;
I hope its okay writing to you gPXE guys, knowing that I use gPXE out of the SYSLINUX package.  
 
I'm successfully using the SYSLINUX version of gPXE, called 'gpxelinux.0', to boot Windows from iSCSI.  Right now, I install Windows to a hard drive first, and then I use 'dd' to move the image of the HD to my iSCSI target.  But I like to go a step further…
 
I'd like to boot from network, connect to a iSCSI target, and then start the installation of the OS from network, too.
 
What I'm doing at the moment…
 
1) Boot server hands 'gpxelinux.0' (chain-loading pxelinux after gpxe) to my PXE clients 
2) In my PXELINUX (using sanboot.c32 module of SYSLINUX) menu I select an empty iSCSI target 
3) I get a "SAN boot failed" message, because the iSCSI target I'm trying to boot is empty.
4) Then I fall back to my PXELINUX menu, and now I select the entry to start WDS (Windows Deployment Services)
5) But when Windows 7 Setup asks for an installation destination, there are no hard drives…
 
I already tried to set the "KEEP-SAN" option (175 gPXE_options: 08 01 01 FF) in my MS-DHCP server, but without any positive change.
 
My question to you guys is:
Is it possible to use gPXE to mount an empty iSCSI disk and then proceed with installing an OS (e.g. Linux, Windows, …) from network?
 
Thanks,
Bernhard
 

[Etherboot-discuss] Booting from multiple Subnets

[Csabi N. <cn...@ea...>]

Hello everyone!

I am not so familiar with the PXE booting, I only use PXE image files to
write to CDs boot from them and load my application from a DHCP server,
which will do the rest of the job.
My question is if there is a way to boot a PC from a different Subnet, for
ex. the DHCP server is part of a subnet and the client machine which wants
to boot via PXE is part of another subnet? Can I configure gPXE so it can
see the other subnet and get the boot image file from there?

Thanks for your help.

[Etherboot-discuss] how to change MAC address

[Marco G. <gi...@si...>]

Hi at all,
I'm a sysadmin in an Italian college; for security reason, our PXE 
server allows only few and well known MAC addresses. When I change mac 
address with gPXE command:

gPXE> set net0/mac ff:ff:ff:11:22:33

and then I check new mac address with:

gPXE> show net0/mac
net0/mac = ff:ff:ff:11:22:33

it seems changed, but if I want to get a DHCP address, with:

gPXE>dhcp net0

I receive 'Connection timed out' error.
With Wireshark, I found that mac address is not changed, but is only 
spoofed; in fact, every ethernet frame send by the card has as source 
address the original network card mac address, but DHCP request has done 
with new mac address (ff:ff:ff:11:22:33). Of course, our dhcp server, 
replies with a DHCP offer to new mac address, so the network card cannot 
accept the offer.

My question is: is this behaviour right ? I mean, command 'set netX/mac' 
should be only use for spoofing mac address in network request, or 
should really change mac address, like unix command 'ifconfig eth0 hw 
ether ff:ff:ff:11:22:33' ??

Thank you,
    Marco

[Etherboot-discuss] Use off DD

[Romain V. V. <rom...@st...>]

Hello,
I wondered if gPXE uses the hard drive of the slave machine to increase its
perform, if there is hard drive of course ?
It can be usefull to save files that the OS or a software uses very often,
so that they didnt overload the network.
Thanks

Re: [Etherboot-discuss] ISCSI boot problem

[Romain V. V. <rom...@st...>]

Thanks , i have solve my problem :) you are right

2010/5/3 Kristof Van Doorsselaere <kva...@as...>

> That depends on what's configured on your SAN (in your case the windows
> machine with starwind iscsi target software)
>
> If you created a target with alias win2003, it probably is something like
> this: *iqn*.2008-08.com.starwindsoftware:win2003
>
> Kristof
>
> On Mon, May 3, 2010 at 6:35 PM, Romain Van Vooren <
> rom...@st...> wrote:
>
>> Thanks but what information should i put instead of exemple.com ?
>>
>> 2010/5/3 Kristof Van Doorsselaere <kva...@as...>
>>
>>> it looks like you are specifying a faulty iscsi IQN
>>>
>>>  "iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname>
>>>
>>> targetname should be a valid iscsi IQN eg:
>>>
>>> *iqn*.*example.com*:disk1
>>>
>>> Kristof
>>>
>>> On 03 May 2010, at 17:13, Romain Van Vooren wrote:
>>>
>>> "sanboot iscsi:192.168.1.101::::win2003" what is wrong ???
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Etherboot-discuss mailing list
>>> Eth...@li...
>>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>>>
>>>
>>
>

Re: [Etherboot-discuss] ISCSI boot problem

[Kristof V. D. <kva...@as...>]

That depends on what's configured on your SAN (in your case the windows
machine with starwind iscsi target software)

If you created a target with alias win2003, it probably is something like
this: *iqn*.2008-08.com.starwindsoftware:win2003

Kristof

On Mon, May 3, 2010 at 6:35 PM, Romain Van Vooren <
rom...@st...> wrote:

> Thanks but what information should i put instead of exemple.com ?
>
> 2010/5/3 Kristof Van Doorsselaere <kva...@as...>
>
>> it looks like you are specifying a faulty iscsi IQN
>>
>>  "iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname>
>>
>> targetname should be a valid iscsi IQN eg:
>>
>> *iqn*.*example.com*:disk1
>>
>> Kristof
>>
>> On 03 May 2010, at 17:13, Romain Van Vooren wrote:
>>
>> "sanboot iscsi:192.168.1.101::::win2003" what is wrong ???
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Etherboot-discuss mailing list
>> Eth...@li...
>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>>
>>
>

Re: [Etherboot-discuss] ISCSI boot problem

[Preston B. <pre...@gm...>]

Whatever your iSCSI target is named. A FQDN is the naming standard,
though I'm not sure you're required to adhere to it, just to whatever
your iSCSI target is set up as on your iSCSI server.

sanboot iscsi:<iSCSI server>::::<iscsi target name>

My /etc/ietd.conf on my iSCSI server (192.168.0.10) has:
Target iqn.ws2
    Lun 0 Path=/iscsi/ws2.img,Type=fileio

So my boot line for sanboot after setting up networking is:
sanboot iscsi:192.168.0.10::::iqn.ws2

On Mon, May 3, 2010 at 11:09 AM, Romain Van Vooren
<rom...@st...> wrote:
> Thanks but what information should i put instead of exemple.com ?
>
> 2010/5/3 Kristof Van Doorsselaere <kva...@as...>
>>
>> it looks like you are specifying a faulty iscsi IQN
>>  "iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname>
>> targetname should be a valid iscsi IQN eg:
>> iqn.example.com:disk1
>> Kristof
>> On 03 May 2010, at 17:13, Romain Van Vooren wrote:
>>
>> "sanboot iscsi:192.168.1.101::::win2003" what is wrong ???
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Etherboot-discuss mailing list
>> Eth...@li...
>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Etherboot-discuss mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>
>

Re: [Etherboot-discuss] ISCSI boot problem

[Romain V. V. <rom...@st...>]

Thanks but what information should i put instead of exemple.com ?

2010/5/3 Kristof Van Doorsselaere <kva...@as...>

> it looks like you are specifying a faulty iscsi IQN
>
>  "iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname>
>
> targetname should be a valid iscsi IQN eg:
>
> *iqn*.*example.com*:disk1
>
> Kristof
>
> On 03 May 2010, at 17:13, Romain Van Vooren wrote:
>
> "sanboot iscsi:192.168.1.101::::win2003" what is wrong ???
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Etherboot-discuss mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>
>

Re: [Etherboot-discuss] ISCSI boot problem

[Kristof V. D. <kva...@as...>]

it looks like you are specifying a faulty iscsi IQN

 "iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname>

targetname should be a valid iscsi IQN eg:

iqn.example.com:disk1

Kristof

On 03 May 2010, at 17:13, Romain Van Vooren wrote:

> "sanboot iscsi:192.168.1.101::::win2003" what is wrong ??? 

[Etherboot-discuss] ISCSI boot problem

[Romain V. V. <rom...@st...>]

Hello
I try to boot with gpxe windows XP without a dhcp server. I have follow your
tutorial on the site.
My computer run on winXPSP3, he have a iscsi target starwind, and i can
connect on the scsi with the Mirosoft isci initiator.
So, i have also a virtual machine with gPXE and a embedded script, I think
my problem is with the script because I see the error "Could not initialise
iscsi device : connection timed out."
Here is my call for iscsi booting : "sanboot iscsi:192.168.1.101::::win2003"
what is wrong ??? (sorry for my bad english, french here :p)

[Etherboot-discuss] Is multipath supported in gPXE iSCSI boot in Windows?

[Sonny Li <shi...@mi...>]

Have done some search, but don't get the suitable results. So ask here:

Situation:
iSCSI initiator machine has two NICs with separated IP address,  Init_ipA and init_ipB
iSCSI Target machine also has two NICs with separated IP address,  target_ipA and target_ipB

question:
Is it possible to set the following and how to setup them
Init_ipA gpxe iSCSI connect to target_ipA for iSCSI boot   as primary path
Init_ipA gpxe iSCSI connect to target_ipA for iSCSI boot  as secondary path

So if primary path is down, secondary path can take it over to continue for iSCSI boot. I have tried for Hardware NICs (like Intel PCI-E). they can support above situation, but not sure for gPXE iSCSI boot.

Thanks

Sonny

[Etherboot-discuss] DHCPDISCOVER and secs field

[Jason A. <ja...@oi...>]

Hello,

I apologize if this has been answered already, but my search didn't turn
anything up.

I'm assisting a colleague with problems PXE booting Xen clients.
Etherboot-5.4.2 is being used by Xen to do the boot. It seems, from my
packet captures, that the "secs" field (9th and 10th octets, "seconds
since client started trying to boot") of the DHCPDISCOVER packets is
never being incremented. I realize that this seems only to be a
suggestion in RFC 1541, but it does seem to be an oversight if this is,
in fact, normal.

Can anyone confirm that this is the case? If so, has it been fixed in
any later version?

Thanks,
Jason Antman
Rutgers University

[Etherboot-discuss] hangs after "gPXE (PCI 08:00.0) Starting execution".

[Jerome I. <ji...@gm...>]

Hello,

I'm using an Intel PRO/1000 XT card with a gPXE 1.0.0 payload (boot rom). I'm
using AoE to provide my client with a block device to boot from, which
is exported
by the dhcp+AoE server running Linux.

Upon boot, when I press CTRL+B, and then type "autoboot", almost
instantly the client
boots from the AoE exported boot device, in other words, everything works fine.

When I do not interrupt the boot process by pressing "CTRL+B", the PC
bios finishes
its initialization and then displays: "gPXE (PCI 08:00.0) Starting
execution" and then
hangs, nothing else is displayed.

What could be the issue?


Thank you,
J.

Re: [Etherboot-discuss] Intel D510MO board, gpxe chainloading problem and gpxe problem

[Stefan H. <ste...@gm...>]

Okay, I think I understand what is going on here.

First of all, for some reason this BIOS does not support the BIOS Boot
Specification and gPXE is falling back to hooking INT 19H.  This is
unfortunate because INT 19H does not give boot device ordering control
like you'd normally expect.

Now here is the interesting part: you are running on old gPXE ROM
which asks the user to press 'B' in order to boot.  This behavior was
changed in December 2008 to prompt the user to press 'N' to *skip*
booting from gPXE.

Here is the commit that changed this behavior, your gPXE ROM is built
from source code older than this commit:
http://git.etherboot.org/?p=gpxe.git;a=commitdiff;h=4d7c650164a759e3dadbcf8f83da6789165c68b7

The good news is that building an up-to-date gPXE ROM will allow
unattended boot:

http://rom-o-matic.net/gpxe/gpxe-git/gpxe.git/contrib/rom-o-matic/

Please let us know how it goes, if the hang initializing PCI devices
still occurs we can debug it with your help.

Stefan

Re: [Etherboot-discuss] Intel D510MO board, gpxe chainloading problem and gpxe problem

[Jörn R. <j....@fr...>]

Am Thu, 1 Apr 2010 13:19:22 +0200
hat Jörn Rink <j....@fr...> (Jörn Rink) folgendes geschrieben:

> Am Thu, 1 Apr 2010 12:11:40 +0100
> hat Stefan Hajnoczi <ste...@gm...> (Stefan Hajnoczi) folgendes
> geschrieben:
> 

> It is in my boot device order, it will boot, but the board told me to
> press b to boot from gPXE (PCI 01:00:00)
> 
> then, when i press b, gpxe is bootet and all is fine, but i dont want
> to press always the b on the keyboard.

I saw the prexx b on my generated gpxe image which is booted after pxe.
So it seems to be a gpxe option. In my gpxe image, the boot process is
not halted.

The intel support told me, even if gpxe is selectable, it is not
supported ;-)

So, i like to generate a new gpxe for the d510 mo and burn it into the
MB bios. Anyone here who made this in the past?




-- 
Nine (not 9)
Never trust a hippie