Indeed, sorry seems I haven't woken up properly yet. (or just missing coffee)
On Sat, Oct 22, 2016 at 12:12 PM, James Harper <ja...@ejbdigital.com.au> wrote: > It’s around 350MB - maybe if I put some punctuation in there it might help > > boot.wim : 347,125,546 bytes "boot.wim" > > :) > > > > James > > > > *From:* Christian Nilsson [mailto:nik...@gmail.com] > *Sent:* Saturday, 22 October 2016 9:04 PM > > *To:* James Harper <ja...@ejbdigital.com.au> > *Cc:* ipxe-devel@lists.ipxe.org > *Subject:* Re: [ipxe-devel] wimboot hang > > > > 34Gb wim file? I'm not expecting a wim over 2GiB working reliably, even > tho it probably should. > > There is some memory boundaries that bootmgr uses that wimboot might not > handle inte the same way. so > > > > Just to avoid any size issue, I would start out with a minimal wim with > the same drivers. > > One other thing to check is that the same wim works on a usb drive as a > replacement for the windows install boot.wim > > > > On Sat, Oct 22, 2016 at 11:54 AM, James Harper <ja...@ejbdigital.com.au> > wrote: > > 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 > > Features: DNS HTTP iSCSI NBD TFTP SRP AoE ELF MBOOT PXE bzImage Menu PXEXT > > > > 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: 172.16.3.104/255.255.255.0 gw 172.16.3.254 > > Next server: 172.16.3.200 > > Filename: 8384db47-704f-405a-bb51-b274f01de49d.ipxe > > tftp://172.16.3.200/8384db47-704f-405a-bb51-b274f01de49d.ipxe... 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: > > > > I wonder how easy it would be to get wimboot logging via serial… > > > > James > > > > > > *From:* Christian Nilsson [mailto:nik...@gmail.com] > *Sent:* Saturday, 22 October 2016 8:44 PM > *To:* James Harper <ja...@ejbdigital.com.au> > *Cc:* ipxe-devel@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 <ja...@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”. > > > > Thanks > > > James > > > > > _______________________________________________ > ipxe-devel mailing list > ipxe-devel@lists.ipxe.org > https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel > > > > >
_______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
