Hi all... I have an error "try to free memory without Signature" at 4 of diskless machines. but other 5 machines work is ok. How can I fix it?
↧
Ipxe with iscsi
↧
Problem PXE booting from VM
Hi all, I am trying to use FOG to image machines on a LAN, but first I am practising on my own machine with VMs. I have followed the steps on "http://192.168.90.208/fog/management/index.php?node=about&sub=pxemenu" to install the FOG server. I have installed Oracle VM Virtual Box and I have loaded an Ubuntu Server virtual disk to the VM. I have set the system to boot from the network and I have set the network to use a bridged adaptor, however when I start up the VM it goes straight the Ubuntu login, seemingly missing the PXE boot from my FOG server altogether.
The connections between the FOG server and VM are there as I can successfully PING from the FOG client to the VM and from the VM to the FOG client
Any help would be greatly appreciated.
The connections between the FOG server and VM are there as I can successfully PING from the FOG client to the VM and from the VM to the FOG client
Any help would be greatly appreciated.
↧
↧
Booting from ROM crashes after ipxe.iso runs with timeout
A certain boot sequence always results in system crashes or freezes. In my case I was using E1000 network card with QEMU emulator and KVM. The guest was trying to boot with empty hard disk and CD-ROM image of ipxe.iso. The problem happens when DHCP server is not yet ready (or it does not provide boot file, etc.), so that after timeout, the BIOS falls back to ROM boot (which happens to be pxe-e1000.rom file in QEMU project) and there it crashes after displaying this message:
IPXE (PCI xx:xx:x) starting execution...
This crash apparently does not happen in two other cases:
1. Booting from ipxe.iso image when no rom image is supplied (i.e. pxe-e1000.rom file is missing or is not installed).
2. Booting without ipxe.iso image and with pxe-e1000.rom present.
In my opinion, running ipxe.iso code renders ROM boot unusable and results in guest code eventually to jump to code which looks like long sequence of zeroes.
In addition to the said above, I've previously seen some posts on the net complaining about crashes with pxe-e1000.rom and QEMU/KVM. Also, as additional information, I was using the most recent version of ipxe sources and different versions of QEMU (old and new ones) to verify that.
I'm not familiar well with this project. Any thoughts or (better) quick fixes would be welcome. A quick workaround would be like this : if using CDROM image, hide the pxe-e1000.rom file (and don't hide it when no CDROM image is given).
Thank you.
IPXE (PCI xx:xx:x) starting execution...
This crash apparently does not happen in two other cases:
1. Booting from ipxe.iso image when no rom image is supplied (i.e. pxe-e1000.rom file is missing or is not installed).
2. Booting without ipxe.iso image and with pxe-e1000.rom present.
In my opinion, running ipxe.iso code renders ROM boot unusable and results in guest code eventually to jump to code which looks like long sequence of zeroes.
In addition to the said above, I've previously seen some posts on the net complaining about crashes with pxe-e1000.rom and QEMU/KVM. Also, as additional information, I was using the most recent version of ipxe sources and different versions of QEMU (old and new ones) to verify that.
I'm not familiar well with this project. Any thoughts or (better) quick fixes would be welcome. A quick workaround would be like this : if using CDROM image, hide the pxe-e1000.rom file (and don't hide it when no CDROM image is given).
Thank you.
↧
Sanboot too slow
Hello,
I have a problem during the boot of an image of windows 7 from an iscsi target.
it lasts longer than two minutes, against 40 secondes with the local disk...
During startup, the iscsi is stopped for a moment and i can see "TCP Retransmission" with tcpdump(see below). After that, everything work fine...
I use the last ipxe from the git repository, all has been compiled on the same host.
tcpdump :
44487 7.124119 192.168.186.1 -> 192.168.186.22 TCP 66 3260→63830 [ACK] Seq=64411681 Ack=443841 Win=361 Len=0 TSval=111891447 TSecr=880913
44488 7.126793 192.168.186.1 -> 192.168.186.22 iSCSI 114 SCSI: Response LUN: 0x00 (Write(10)) (Good)
44489 7.126971 192.168.186.22 -> 192.168.186.1 TCP 66 63830→3260 [ACK] Seq=443841 Ack=64411729 Win=512 Len=0 TSval=880913 TSecr=111891447
44490 7.127016 192.168.186.22 -> 192.168.186.1 iSCSI 114 SCSI: Write(10) LUN: 0x00 (LBA: 0x002644bc, Len: 1)
44491 7.127064 192.168.186.1 -> 192.168.186.22 iSCSI 114 Ready To Transfer
44492 7.127217 192.168.186.22 -> 192.168.186.1 TCP 114 [TCP segment of a reassembled PDU]
44493 7.163899 192.168.186.1 -> 192.168.186.22 TCP 66 3260→63830 [ACK] Seq=64411777 Ack=443937 Win=361 Len=0 TSval=111891457 TSecr=880913
44494 7.164166 192.168.186.22 -> 192.168.186.1 iSCSI 578 SCSI: Data Out LUN: 0x00 (Write(10) Request Data)
44495 7.164193 192.168.186.1 -> 192.168.186.22 TCP 66 3260→63830 [ACK] Seq=64411777 Ack=444449 Win=369 Len=0 TSval=111891457 TSecr=880913
44496 7.234320 192.168.186.1 -> 192.168.186.22 iSCSI 114 SCSI: Response LUN: 0x00 (Write(10)) (Good)
44497 7.435896 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44498 7.639895 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44499 8.047899 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44500 8.863895 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44501 10.499898 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44502 18.487904 192.168.186.1 -> 192.168.186.22 iSCSI 102 Logout Response
44503 20.311904 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44504 24.055915 Intel_6e:45:a6 -> Broadcast AoE 32 Query Config Information Request
44505 33.399904 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44506 38.407895 Intel_6e:45:a6 -> HonHaiPr_87:51:e7 ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44507 39.407892 Intel_6e:45:a6 -> HonHaiPr_87:51:e7 ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44508 40.407890 Intel_6e:45:a6 -> HonHaiPr_87:51:e7 ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44509 59.575914 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44510 60.575904 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44511 61.575898 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44512 84.215923 Intel_6e:45:a6 -> Broadcast AoE 32 Query Config Information Request
44513 85.751900 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44514 86.751894 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44515 87.751893 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44516 101.631688 HonHaiPr_87:51:e7 -> Broadcast ARP 60 Who has 192.168.186.1? Tell 192.168.186.22
44517 101.631717 Intel_6e:45:a6 -> HonHaiPr_87:51:e7 ARP 42 192.168.186.1 is at 00:0e:0c:6e:45:a6
44518 101.631823 192.168.186.22 -> 192.168.186.1 TCP 66 [TCP Port numbers reused] 49152→3260 [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
44519 101.631862 192.168.186.1 -> 192.168.186.22 TCP 66 [TCP Retransmission] 3260→49152 [SYN, ACK] Seq=3176460178 Ack=2129312667 Win=29200 Len=0 MSS=1460 SACK_PERM=1 WS=128
44520 101.631994 192.168.186.22 -> 192.168.186.1 TCP 60 49152→3260 [ACK] Seq=1 Ack=1 Win=65536 Len=0
44521 101.632177 192.168.186.22 -> 192.168.186.1 iSCSI 254 Login Command
44522 101.632206 192.168.186.1 -> 192.168.186.22 TCP 54 3260→49152 [ACK] Seq=3176460179 Ack=2129312867 Win=30336 Len=0
44523 101.632378 192.168.186.1 -> 192.168.186.22 iSCSI 142 [TCP Retransmission] Login Response (Success)
44524 101.632815 192.168.186.22 -> 192.168.186.1 iSCSI 402 Login Command
44525 101.632944 192.168.186.1 -> 192.168.186.22 iSCSI 358 [TCP Retransmission] Login Response (Success)
44526 101.645772 192.168.186.22 -> 192.168.186.1 iSCSI 102 SCSI: Report LUNs LUN: 0x00
Here is the command use to launch the sanboot :
sleep 1
set keep-san 1
sanboot iscsi:192.168.186.1::::iqn.2015-03.xxxxx.xx:storage.smc
can someone help me to solve my probleme ? thanks
I have a problem during the boot of an image of windows 7 from an iscsi target.
it lasts longer than two minutes, against 40 secondes with the local disk...
During startup, the iscsi is stopped for a moment and i can see "TCP Retransmission" with tcpdump(see below). After that, everything work fine...
I use the last ipxe from the git repository, all has been compiled on the same host.
tcpdump :
44487 7.124119 192.168.186.1 -> 192.168.186.22 TCP 66 3260→63830 [ACK] Seq=64411681 Ack=443841 Win=361 Len=0 TSval=111891447 TSecr=880913
44488 7.126793 192.168.186.1 -> 192.168.186.22 iSCSI 114 SCSI: Response LUN: 0x00 (Write(10)) (Good)
44489 7.126971 192.168.186.22 -> 192.168.186.1 TCP 66 63830→3260 [ACK] Seq=443841 Ack=64411729 Win=512 Len=0 TSval=880913 TSecr=111891447
44490 7.127016 192.168.186.22 -> 192.168.186.1 iSCSI 114 SCSI: Write(10) LUN: 0x00 (LBA: 0x002644bc, Len: 1)
44491 7.127064 192.168.186.1 -> 192.168.186.22 iSCSI 114 Ready To Transfer
44492 7.127217 192.168.186.22 -> 192.168.186.1 TCP 114 [TCP segment of a reassembled PDU]
44493 7.163899 192.168.186.1 -> 192.168.186.22 TCP 66 3260→63830 [ACK] Seq=64411777 Ack=443937 Win=361 Len=0 TSval=111891457 TSecr=880913
44494 7.164166 192.168.186.22 -> 192.168.186.1 iSCSI 578 SCSI: Data Out LUN: 0x00 (Write(10) Request Data)
44495 7.164193 192.168.186.1 -> 192.168.186.22 TCP 66 3260→63830 [ACK] Seq=64411777 Ack=444449 Win=369 Len=0 TSval=111891457 TSecr=880913
44496 7.234320 192.168.186.1 -> 192.168.186.22 iSCSI 114 SCSI: Response LUN: 0x00 (Write(10)) (Good)
44497 7.435896 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44498 7.639895 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44499 8.047899 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44500 8.863895 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44501 10.499898 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44502 18.487904 192.168.186.1 -> 192.168.186.22 iSCSI 102 Logout Response
44503 20.311904 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44504 24.055915 Intel_6e:45:a6 -> Broadcast AoE 32 Query Config Information Request
44505 33.399904 192.168.186.1 -> 192.168.186.22 iSCSI 114 [TCP Retransmission] SCSI: Response LUN: 0x00 (Write(10)) (Good)
44506 38.407895 Intel_6e:45:a6 -> HonHaiPr_87:51:e7 ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44507 39.407892 Intel_6e:45:a6 -> HonHaiPr_87:51:e7 ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44508 40.407890 Intel_6e:45:a6 -> HonHaiPr_87:51:e7 ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44509 59.575914 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44510 60.575904 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44511 61.575898 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44512 84.215923 Intel_6e:45:a6 -> Broadcast AoE 32 Query Config Information Request
44513 85.751900 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44514 86.751894 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44515 87.751893 Intel_6e:45:a6 -> Broadcast ARP 42 Who has 192.168.186.22? Tell 192.168.186.1
44516 101.631688 HonHaiPr_87:51:e7 -> Broadcast ARP 60 Who has 192.168.186.1? Tell 192.168.186.22
44517 101.631717 Intel_6e:45:a6 -> HonHaiPr_87:51:e7 ARP 42 192.168.186.1 is at 00:0e:0c:6e:45:a6
44518 101.631823 192.168.186.22 -> 192.168.186.1 TCP 66 [TCP Port numbers reused] 49152→3260 [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
44519 101.631862 192.168.186.1 -> 192.168.186.22 TCP 66 [TCP Retransmission] 3260→49152 [SYN, ACK] Seq=3176460178 Ack=2129312667 Win=29200 Len=0 MSS=1460 SACK_PERM=1 WS=128
44520 101.631994 192.168.186.22 -> 192.168.186.1 TCP 60 49152→3260 [ACK] Seq=1 Ack=1 Win=65536 Len=0
44521 101.632177 192.168.186.22 -> 192.168.186.1 iSCSI 254 Login Command
44522 101.632206 192.168.186.1 -> 192.168.186.22 TCP 54 3260→49152 [ACK] Seq=3176460179 Ack=2129312867 Win=30336 Len=0
44523 101.632378 192.168.186.1 -> 192.168.186.22 iSCSI 142 [TCP Retransmission] Login Response (Success)
44524 101.632815 192.168.186.22 -> 192.168.186.1 iSCSI 402 Login Command
44525 101.632944 192.168.186.1 -> 192.168.186.22 iSCSI 358 [TCP Retransmission] Login Response (Success)
44526 101.645772 192.168.186.22 -> 192.168.186.1 iSCSI 102 SCSI: Report LUNs LUN: 0x00
Here is the command use to launch the sanboot :
sleep 1
set keep-san 1
sanboot iscsi:192.168.186.1::::iqn.2015-03.xxxxx.xx:storage.smc
can someone help me to solve my probleme ? thanks
↧
TFTP Access Denied
Hi,
I am trying to perform a Legacy PXE Boot of iPXE undionly.kpxe from a Windows 2012 Server running WDS. I have TFTP Enabled and accepting connections for all clients. Every time my client performs a PXE request it gets a DHCP reply to boot undionly.kpxe. Then it performs a TFTP Read of undionly.kpxe but the server sends back TFTP: Access Illegal Operation. Access Denied. If I stop WDS and run TFPTD32.EXE the transfer happens successfully but I need to use WDS because I want to use PXE chaining to boot a Windows 7 boot installation media after from WDS. I looked at everything on the WDS Server and cant find out why I am getting Access Denied. Is it possible to TFTP Boot undionly.kpxe from a Windows 2012 Server running DHCP Role and WDS Role?
Thanks,
Todd
I am trying to perform a Legacy PXE Boot of iPXE undionly.kpxe from a Windows 2012 Server running WDS. I have TFTP Enabled and accepting connections for all clients. Every time my client performs a PXE request it gets a DHCP reply to boot undionly.kpxe. Then it performs a TFTP Read of undionly.kpxe but the server sends back TFTP: Access Illegal Operation. Access Denied. If I stop WDS and run TFPTD32.EXE the transfer happens successfully but I need to use WDS because I want to use PXE chaining to boot a Windows 7 boot installation media after from WDS. I looked at everything on the WDS Server and cant find out why I am getting Access Denied. Is it possible to TFTP Boot undionly.kpxe from a Windows 2012 Server running DHCP Role and WDS Role?
Thanks,
Todd
↧
↧
Windows Server 2012 R2 iSCSI boot
Attempting to boot Windows from iSCSI target. I was able to successfully do it on an older laptop to validate proof of concept, but on this board and this board, I've been unsuccessful. Both Windows 7 Ultimate and Windows Server 2012 R2 install fine onto the iSCSI target, but reboot after the first startup (after sanboot).
Here's what I'm doing:
I have windows installation media on USB, boot order set PXE then to USB.
PXE Boot iPXE (chain) with iSCSI support
!#ipxe
dhcp
sanhook iscsi:<ip>:::<lun>:<iqn>
sanboot --no-describe --drive 0x81
It then skips to the next medium in the boot order (USB), and runs the windows installer. I then install windows onto the iSCSI target. On the svme1908, I have to load network drivers in Windows 7 before the iSCSI target presents itself as an install target, but on the C163, I don't. Window Server 2012 R2, no drivers are required, the target shows up fine.
Installation goes fine.
First reboot, I escape into the iPXE prompt and do:
dhcp
sanboot iscsi:<ip>:::<lun>:<iqn>
And it boots into the Windows logo, and eventually BSODs (both Win7 and Server 2012 R2)
I'm thinking I have the same woes as this thread - could it be because these boards each have 4 network ports, and the iBFT isn't being properly populated? The test laptop that worked had only one NIC.
Any ideas what I should try next? Hopefully something stupid and obvious.
Patrick
Here's what I'm doing:
I have windows installation media on USB, boot order set PXE then to USB.
PXE Boot iPXE (chain) with iSCSI support
!#ipxe
dhcp
sanhook iscsi:<ip>:::<lun>:<iqn>
sanboot --no-describe --drive 0x81
It then skips to the next medium in the boot order (USB), and runs the windows installer. I then install windows onto the iSCSI target. On the svme1908, I have to load network drivers in Windows 7 before the iSCSI target presents itself as an install target, but on the C163, I don't. Window Server 2012 R2, no drivers are required, the target shows up fine.
Installation goes fine.
First reboot, I escape into the iPXE prompt and do:
dhcp
sanboot iscsi:<ip>:::<lun>:<iqn>
And it boots into the Windows logo, and eventually BSODs (both Win7 and Server 2012 R2)
I'm thinking I have the same woes as this thread - could it be because these boards each have 4 network ports, and the iBFT isn't being properly populated? The test laptop that worked had only one NIC.
Any ideas what I should try next? Hopefully something stupid and obvious.
Patrick
↧
winboot request - injecting or patching wim
I only took a short look at the winboot source.. was trying to find out how to include or inject files into a wim.. I was unsuccessful.
Would be nice if we could use something like the patching function in winboot/wimpatch.c to
inject files into a boot.wim.
this would
- reduce the pains of managing multiple boot.wim files.
- remove the need for imagex to add small scripts
- add simple dynamic install scripts from a webservice
initrd bcd BCD
initrd boot.sdi boot.sdi
initrd boot.wim boot.wim
initrd http://service/winpeshl.py?mac=${m} Windows/System32/winpeshl.ini
chain wimboot
Or perhaps something like:
initrd http://service/winpeshl.py winpeshl.ini
chain wimboot patch=boot.wim:winpeshl.ini:Windows/System32/winpeshl.ini
[/undefined]
if it's not possible ill take a simple no for an answer![Smile]( "Smile")
Thanks.
Would be nice if we could use something like the patching function in winboot/wimpatch.c to
inject files into a boot.wim.
this would
- reduce the pains of managing multiple boot.wim files.
- remove the need for imagex to add small scripts
- add simple dynamic install scripts from a webservice
initrd bcd BCD
initrd boot.sdi boot.sdi
initrd boot.wim boot.wim
initrd http://service/winpeshl.py?mac=${m} Windows/System32/winpeshl.ini
chain wimboot
Or perhaps something like:
initrd http://service/winpeshl.py winpeshl.ini
chain wimboot patch=boot.wim:winpeshl.ini:Windows/System32/winpeshl.ini
[/undefined]
if it's not possible ill take a simple no for an answer
Thanks.
↧
DHCP Issues
We have some new Lenovo Thinkpad 11e's that are having issues with iPxe. I have been talking with Uncle Frank and Tom Elliot over at the FOG forums but I figured I would post up a thread here too. http://fogproject.org/forum/threads/inte...ing.12729/
So far we have got it past the stuck initializing issue but now it is not pulling down an IP adress from the DHCP. Here is a wireshark capture from a portable fog server running dhcp and connected straight to the laptop.
http://www.filedropper.com/wiresharkcapture
In the capture you can see on lines 161, 165, and 170 it is producing an error under Option 77. I am not very versed in what this might mean so that is why I have started this thread. Any help I could get would be very much appreciated.
So far we have got it past the stuck initializing issue but now it is not pulling down an IP adress from the DHCP. Here is a wireshark capture from a portable fog server running dhcp and connected straight to the laptop.
http://www.filedropper.com/wiresharkcapture
In the capture you can see on lines 161, 165, and 170 it is producing an error under Option 77. I am not very versed in what this might mean so that is why I have started this thread. Any help I could get would be very much appreciated.
↧
Booting to local partition / Boot grub from Pxe
Hey,
I plan to deploy iPxe to my machines.
Since I can't flash it into the NIC, I will boot iPxe from grub, no problem so far.
IPxe fetches a script from the server via https and I got that part working nicely.
However, I will then need to be able to boot from a local partition: I know I can use 'sanboot --no-describe --drive 0x80'. But that just reloads grub from the MBR.
If iPxe is the default entry, this will boot iPxe again and I have a boot-loop.
Is there a way to directly boot a kernel from a local partition? I did not find anything in the command list, so probably not, since Ipxe probably does not understand how to read those filesystems.
Alternatively, is there a way to boot into a grub image on the PXE server?
I tried to generate a grub pxeboot image, using
And then booting that entry via http with:
Grub starts, but reports 'error: file not found' and then goes into a rescue console.
If I could load a grub menu from the server, I will then be able to boot from a local partition.
Any help is appreciated
I plan to deploy iPxe to my machines.
Since I can't flash it into the NIC, I will boot iPxe from grub, no problem so far.
IPxe fetches a script from the server via https and I got that part working nicely.
However, I will then need to be able to boot from a local partition: I know I can use 'sanboot --no-describe --drive 0x80'. But that just reloads grub from the MBR.
If iPxe is the default entry, this will boot iPxe again and I have a boot-loop.
Is there a way to directly boot a kernel from a local partition? I did not find anything in the command list, so probably not, since Ipxe probably does not understand how to read those filesystems.
Alternatively, is there a way to boot into a grub image on the PXE server?
I tried to generate a grub pxeboot image, using
Code:
grub-mknetdir --net-directory=/tftpboot/ --subdir=grubpxeCode:
kernel http://.../files/grubpxe/i386-pc/core.0
bootIf I could load a grub menu from the server, I will then be able to boot from a local partition.
Any help is appreciated
↧
↧
UEFI Local boot to drive
Hello,
I was wondering if it's possible to boot to a local drive from UEFI iPXE. It's actually an NVMe drive which may complicate things but I can boot the drive during system boot without iPXE.
I was wondering if it's possible to boot to a local drive from UEFI iPXE. It's actually an NVMe drive which may complicate things but I can boot the drive during system boot without iPXE.
↧
11 sec per https:// connection?
I'm missing something, but I can't begin to guess what it is, I need help.
First I set up an insecure http connection between a kvm virtual machine guest with a blank little disk and Seabios garden variety pxe. DHCP served up an iPXE and further http:// requests were sub-second quick to establish. Large files transfer at near link speed. So far, so good.
Next I cooked up a 2048 bit RSA ca, nginx server cert, and built a ipxe with a 2048 bit private key. The ipxe has an embedded private key, embedded client cert, and embedded ca.
the ca does point to a local http:// server holding a certificate revocation list / crl. I have no idea whether the ipxe client checks the crl for the server's cert, but I know the server checks the ipxe cert against the crl before beginning the secure session.
When I issue an ipxe https:// request, the thing sits there for 10.7 seconds, then begins the transfer, which appears to complete quickly. I actually can't be sure it is the setup that takes 10.7 second or whether it does that quickly, loses its place somehow, then recovers and does the transfer.
Anyhow: The nginx setup ssl section is:
ssl_session_timeout 5m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers AES256-SHA256:AES256-SHA;
ssl_prefer_server_ciphers on;
ssl_verify_client on;
ssl_session_cache shared:ssl:2m;
ssl_verify_depth 1;
When I read the docs I was prepared for a 1 second added delay per transaction. 10.7 sec is a project killer delay. Occasionally I'll get a timeout on the ipxe side before the transfer completes. What am I missing? Why does it take so long to set up a https:// session?
While we're at it, does iPXE support the idea of reusing the setup of a SSL request completed moments before? Or is there no way to reuse and avoid the setup lag for subsequent quick https requests to the same server?
Thanks for any ideas!
First I set up an insecure http connection between a kvm virtual machine guest with a blank little disk and Seabios garden variety pxe. DHCP served up an iPXE and further http:// requests were sub-second quick to establish. Large files transfer at near link speed. So far, so good.
Next I cooked up a 2048 bit RSA ca, nginx server cert, and built a ipxe with a 2048 bit private key. The ipxe has an embedded private key, embedded client cert, and embedded ca.
the ca does point to a local http:// server holding a certificate revocation list / crl. I have no idea whether the ipxe client checks the crl for the server's cert, but I know the server checks the ipxe cert against the crl before beginning the secure session.
When I issue an ipxe https:// request, the thing sits there for 10.7 seconds, then begins the transfer, which appears to complete quickly. I actually can't be sure it is the setup that takes 10.7 second or whether it does that quickly, loses its place somehow, then recovers and does the transfer.
Anyhow: The nginx setup ssl section is:
ssl_session_timeout 5m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers AES256-SHA256:AES256-SHA;
ssl_prefer_server_ciphers on;
ssl_verify_client on;
ssl_session_cache shared:ssl:2m;
ssl_verify_depth 1;
When I read the docs I was prepared for a 1 second added delay per transaction. 10.7 sec is a project killer delay. Occasionally I'll get a timeout on the ipxe side before the transfer completes. What am I missing? Why does it take so long to set up a https:// session?
While we're at it, does iPXE support the idea of reusing the setup of a SSL request completed moments before? Or is there no way to reuse and avoid the setup lag for subsequent quick https requests to the same server?
Thanks for any ideas!
↧
After Last Update VMWare ESX slow download
After one of the last Updates i get "error: lzma.h: No such file or directory".
After i have installed liblzma-dev the error is gone, but now we have slow http downloads from vmxnet3. Any Ideas?
After i have installed liblzma-dev the error is gone, but now we have slow http downloads from vmxnet3. Any Ideas?
↧
Slow download after Last Update
With my version from 07.12.2014 all works fine. With one of the last Updates all our VMWare vmxnet3 http downloads are really slow.
Any Ideas?
Any Ideas?
↧
↧
BCD add entry to IPXE
Hello
Is it possible to run directly from the manager ipxe Microsoft?
- BCD add entry to IPXE
Thanks
Is it possible to run directly from the manager ipxe Microsoft?
- BCD add entry to IPXE
Thanks
↧
The problem with operation of IMA of images of HDD is more than 2GB
Im create HDD image from physical hdd 3,5 GB.
On this hdd one boot partition 3.5GB, FAT32 and installing DOS(from win98).
On this partition there is a lot of different files, the total size of all files is more than 2 GB.
Im Boot from an HTTP target:
samboot http://192.168.0.1/disk.ima
Perfectly booting DOS, everything works, very thanks to the author of ipxe![Wink]( "Wink")
Files which are located on a disk less than 2GB physical hdd addres(lba) - read perfectly.
But there is one problem:
The file which data are above to boundary of address space of HDD more 2GB, reads not correctly.
I have an assumption that somewhere in the IPXE program - addressing restriction is put (2GB maximum).
Please check the IPXE program and correct an error.
If additional clarification is necessary, I am ready to a discussion.
Thanks.
On this hdd one boot partition 3.5GB, FAT32 and installing DOS(from win98).
On this partition there is a lot of different files, the total size of all files is more than 2 GB.
Im Boot from an HTTP target:
samboot http://192.168.0.1/disk.ima
Perfectly booting DOS, everything works, very thanks to the author of ipxe
Files which are located on a disk less than 2GB physical hdd addres(lba) - read perfectly.
But there is one problem:
The file which data are above to boundary of address space of HDD more 2GB, reads not correctly.
I have an assumption that somewhere in the IPXE program - addressing restriction is put (2GB maximum).
Please check the IPXE program and correct an error.
If additional clarification is necessary, I am ready to a discussion.
Thanks.
↧
Adding a command to iPXE?
Is there an easy way to add extra commands to iPXE? I'd really like to extend it in a few ways in order to provide more host data to boot scripts. Tcpdump is one of the commands I'd like to add. How difficult would this be to accomplish?
↧
Windows 8 iSCSi Boot - INACCESSIBLE_BOOT_DEVICE
We are trying to boot Windows 8 from an iSCSI target. I have an i7 based diskless client. I used its PXE ROM to boot iPXE according to these steps:
http://ipxe.org/howto/msdhcp#pxe_chainloading
After iPXE loads I use a .ipxe script on my Web Server to have wimboot run and I can connect to and install Windows 8 (after patching my NIC driver into boot.wim and install.wim) to my iSCSi target as outlined here:
http://ipxe.org/wimboot
After Windows 8 installation to my iSCSI target my PXE rom boots iPXE, connects to the iSCSI SAN, then proceeds to boot Windows 8 from my iSCSI target. Just before I get to screen where I would expect Windows to ask my the final questions about users and computer name I get what appears to be a BSOD with INACCESSIBLE_BOOT_DEVICE (Your PC ran into a problem and needs to restart. If you'd like to know more,you can search online later for this error: INACCESSIBLE_BOOT_DEVICE).
Can somebody PLEASE tell me what I might need to do? Do I need to somehow get some iSCSI initiator drivers into my Windows 8 install.wim image?
Thanks,
Todd
http://ipxe.org/howto/msdhcp#pxe_chainloading
After iPXE loads I use a .ipxe script on my Web Server to have wimboot run and I can connect to and install Windows 8 (after patching my NIC driver into boot.wim and install.wim) to my iSCSi target as outlined here:
http://ipxe.org/wimboot
After Windows 8 installation to my iSCSI target my PXE rom boots iPXE, connects to the iSCSI SAN, then proceeds to boot Windows 8 from my iSCSI target. Just before I get to screen where I would expect Windows to ask my the final questions about users and computer name I get what appears to be a BSOD with INACCESSIBLE_BOOT_DEVICE (Your PC ran into a problem and needs to restart. If you'd like to know more,you can search online later for this error: INACCESSIBLE_BOOT_DEVICE).
Can somebody PLEASE tell me what I might need to do? Do I need to somehow get some iSCSI initiator drivers into my Windows 8 install.wim image?
Thanks,
Todd
↧
↧
Intel I219LM LAN chipset iPXE cannot find LAN card
Dear All,
we found an issue with Intel 219-LM lan chipset, when it boot to legacy model with undionly.kpxe it will show bellow error message, but it can boot UEFI model with snponly.efi. who can help me for this issue?
TFTP Download:boot\undionly.kpxe
PXE->EB:!PXE at 961B:0070,entry point at 961B:0106
UNDI code segment 961B:5F90, data segment 8FF6:6250 (575-625kB)
UNDI device is PCI 00:1F.6,type DIX+802.3
575kB free base memory after PXE unload
iPXE initialising devices...OK
iPXE 1.0.0 + --open source network...........
Features: HTTP iSCSI DNS TFTP..........
No more network devices
selected boot deivce failed. press any key to reboot the system
Bellow is LAN card ID:
PCI\VEN_8086&DEV_156F&SUBSYS_06DD1028&REV_10\3&11583659&0&FE: Intel® Ethernet Connection I219-LM
PCI\VEN_8086&DEV_15B7&SUBSYS_06D91028&REV_20\3&11583659&0&FE: Intel® Ethernet Connection (2) I219-LM
By the way, when we enter "Ctl+B", run config, all item, include busid,busloc,bustype,chip,mac,etc all show me "not specified"
we found an issue with Intel 219-LM lan chipset, when it boot to legacy model with undionly.kpxe it will show bellow error message, but it can boot UEFI model with snponly.efi. who can help me for this issue?
TFTP Download:boot\undionly.kpxe
PXE->EB:!PXE at 961B:0070,entry point at 961B:0106
UNDI code segment 961B:5F90, data segment 8FF6:6250 (575-625kB)
UNDI device is PCI 00:1F.6,type DIX+802.3
575kB free base memory after PXE unload
iPXE initialising devices...OK
iPXE 1.0.0 + --open source network...........
Features: HTTP iSCSI DNS TFTP..........
No more network devices
selected boot deivce failed. press any key to reboot the system
Bellow is LAN card ID:
PCI\VEN_8086&DEV_156F&SUBSYS_06DD1028&REV_10\3&11583659&0&FE: Intel® Ethernet Connection I219-LM
PCI\VEN_8086&DEV_15B7&SUBSYS_06D91028&REV_20\3&11583659&0&FE: Intel® Ethernet Connection (2) I219-LM
By the way, when we enter "Ctl+B", run config, all item, include busid,busloc,bustype,chip,mac,etc all show me "not specified"
↧
Can't iscsi boot windows 8 with undionly.kkpxe
Hi all.
I use undionly.kkpxe to chainload scripts and sanboot from iscsi.
kkpxe is much faster when "initialising devices", so there's no problem until i tried to boot windows 8 with it.
When i boot from Win8 with kkpxe, it reboots repeatedly.
I could boot windows 8 with undionly.kpxe but it has a delay with initialising.
So why can't i boot with kkpxe?
or
is there any solution to reduce delay with kpxe?
Thank you.
I use undionly.kkpxe to chainload scripts and sanboot from iscsi.
kkpxe is much faster when "initialising devices", so there's no problem until i tried to boot windows 8 with it.
When i boot from Win8 with kkpxe, it reboots repeatedly.
I could boot windows 8 with undionly.kpxe but it has a delay with initialising.
So why can't i boot with kkpxe?
or
is there any solution to reduce delay with kpxe?
Thank you.
↧
ipxe in VM unable to communicate to host
Hi.
I have two VMs both having 2 network configs as below:
one using vboxnet0 that is host only
and the other is NAT
one VM-Redhat runs redhat linux 6.5 and is able to communicate to host,
but the other when booted with ipxe (latest) is not able to communicate to host but is able to communicate to VM-Redhat ( has the dhcp,tftp and http with ipxe in it ).
Thanks.
I have two VMs both having 2 network configs as below:
one using vboxnet0 that is host only
and the other is NAT
one VM-Redhat runs redhat linux 6.5 and is able to communicate to host,
but the other when booted with ipxe (latest) is not able to communicate to host but is able to communicate to VM-Redhat ( has the dhcp,tftp and http with ipxe in it ).
Thanks.
↧