[ipxe-devel] wimboot hang

James Harper james at ejbdigital.com.au
Sat Oct 22 09:54:00 UTC 2016

sectors = 0xff80040 which is definitely 127GB. The 1024*255*63 is a legacy holdover from the old 8GB disk limit. I think.

Boot with imgstat in looks like:
iPXE 1.0.0+ (93224) -- Open Source Network Boot Firmware -- http://ipxe.org

net0: 00:15:5d:00:89:04 using netvsc on {bd959f1e-e64b-4d55-a501-a1e8d453f4e0} (open)
  [Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 00:15:5d:00:89:04).... ok
net0: gw
Next server:
Filename: 8384db47-704f-405a-bb51-b274f01de49d.ipxe
tftp:// ok
8384db47-704f-405a-bb51-b274f01de49d.ipxe : 148 bytes [script]
wimboot-2.5.2... ok
boot/bcd... ok
boot/boot.sdi... ok
sources/boot.wim... ok
wimboot-2.5.2 : 42496 bytes [bzImage] [SELECTED] "pause"
bcd : 262144 bytes [PXE-NBP] "BCD"
boot.sdi : 3170304 bytes "boot.sdi"
boot.wim : 347125546 bytes "boot.wim"

Not sure if screenshots work on this list, but then wimboot takes over and looks like this:
[cid:image001.png at 01D22CA6.48301670]

I wonder how easy it would be to get wimboot logging via serial…


From: Christian Nilsson [mailto:nikize at gmail.com]
Sent: Saturday, 22 October 2016 8:44 PM
To: James Harper <james at ejbdigital.com.au>
Cc: ipxe-devel at lists.ipxe.org
Subject: Re: [ipxe-devel] wimboot hang

wimboot emulates a disk with a fat fs on it, which windows bootmgr uses to load it's files.
in this case it is 1024*255*63*512 = ~8Gb

it would be interesting to see what imgstat in ipxe gives you just before your boot line

On Sat, Oct 22, 2016 at 8:31 AM, James Harper <james at ejbdigital.com.au<mailto:james at ejbdigital.com.au>> wrote:
Wimboot is hanging on boot in a hyper-v VM. The screen it stops at says:

Get parameters: C/H/S = 1024/255/63, drives = 1
Get disk type: sectors = 0xff80040, type = 3
Extensions installation check
Get Extended parameters: C/H/S = 1024/255/63, sectors = 0xfff80040 (512 bytes)
Get parameters: C/H/S = 1024/255/63, drives = 1

The reported number of sectors would be correct if the VM had a disk attached, but it doesn’t so I’m a little curious as to why it thinks there is, unless wimboot fakes a 127GB disk too?

Any idea why it might be hanging? I have windbg running and windbg reports that it gets as far as “Boot Debugger Initialized”.



ipxe-devel mailing list
ipxe-devel at lists.ipxe.org<mailto:ipxe-devel at lists.ipxe.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20161022/476b0da6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9434 bytes
Desc: image001.png
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20161022/476b0da6/attachment.png>

More information about the ipxe-devel mailing list