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