Re: [ipxe-devel] SAN iso boot to install Win8 to SAN question..

2012-01-05 Thread Andrew Bobulsky
Hello Jarrod, While I can't speak to your iPXE question, I'd suggest you try hooking the HDD LUN as 0x80, and the ODD LUN as a traditional ODD bios drive number (0xE0 I think? Not sure off the top of my head :P), and try booting that. You might also have some luck by doing a SAN attach of the HD

[ipxe-devel] SAN iso boot to install Win8 to SAN question..

2012-01-05 Thread Jarrod Johnson
So normally I'd do a typical PXE boot of WinPE to install to a new san, but in this case I have a little complexity that prevents that at the moment. So I used tgtd to give me two luns, a blank drive as lun 1 and a windows install ISO as lun 2. I tried hooking it as 0x80 for the hard drive and 0x

Re: [ipxe-devel] vmxnet3 port

2012-01-05 Thread Christopher Barry
On Thu, 2012-01-05 at 10:43 +, Michael Brown wrote: > On Thursday 05 Jan 2012 05:22:56 Pete Holland wrote: > > So I'm working on a port of the vmxnet3 driver to ipxe (mainly because > > the default pxe client in ESX is not suitable for my needs). > > One problem I've run into is that the vmxnet

Re: [ipxe-devel] lkrn command line issues

2012-01-05 Thread Kenneth MacDonald
On Wed, 2012-01-04 at 09:25 -0800, Dave Hansen wrote: > I was trying the lkrn command-line on some different hardware than I > normally use, and I'm seeing some issues. I seem to just get jibberish > instead of the command-line that I passed in: > > cmdline_phys: 99000 > cmdline_user: 80b28f90 >

Re: [ipxe-devel] vmxnet3 port

2012-01-05 Thread Michael Brown
On Thursday 05 Jan 2012 05:22:56 Pete Holland wrote: > So I'm working on a port of the vmxnet3 driver to ipxe (mainly because > the default pxe client in ESX is not suitable for my needs). > One problem I've run into is that the vmxnet3 driver seems to require > far more memory (by default somewher