Re: [ipxe-devel] vmxnet3 port
so, ipxe never does polling for packets. a la Linux NAPI? thanks! -Alessandro- Here i am, A young man, A crashing computer program, Here is a pen, write out my name... (from: The Servant - Orchestra) On Thu, Jan 5, 2012 at 05:31, Christopher Barry christopher.ba...@rackwareinc.com wrote: 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 vmxnet3 driver seems to require far more memory (by default somewhere between 1-2 MB) from the heap than ipxe normally has (128K) for setting up all of its DMA structures. I am currently hacking malloc.c to up the heap size but I'm wondering if there is a 'correct' way of doing this in terms of ipxe development (since, if I'm successful, I'd like to contribute the port to the project). The second problem is that I am at the point where I have set up the BARs correctly (as I can read/write the MAC address, link state is readable, and resetting the device seems to jigger some logs into vmware.log indicating that it is successfully doing the reset), however 'activating' the device fails (with no indication in vmware.log or hostd.log as to why). At this point, I'm about to go hat-in-hand to the vmware dev responsible for the Linux vmxnet3 driver for some insight, but I figured I'd ask if anyone else here has tried this before, heard of anyone trying this, or otherwise has a thought on the matter. I tried writing a vmxnet3 driver about a month ago. Latest version is attached. This is a written-from-scratch iPXE driver rather than a Linux port, and it doesn't use unusual amounts of memory. The driver basically works, but has an unusual problem: the (virtual) hardware reports TX completions immediately but reports RX completions only after every two packets. Consequently, everything works fine only as long as there is additional traffic on the interface (e.g. a flood ping from the host). If you can fix the RX completion problem, that would be fantastic! Michael + +/** Driver shared area magic */ +#define VMXNET3_SHARED_MAGIC 0xbabefee1 + now THAT's magic... :) ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Re: [ipxe-devel] Query on UEFI iPXE boot
Hi All,
Do we have any readme that suggests how we can execute iPXE UEFI boot?
We tried UEFI IPXE boot with an Intel igb CNA. The device ID was 10c9. We
built 808610c9.efi. However while trying the UEFI iPXE boot using the .efi file
we could see that the client is able to successfully download the.efi file. The
client hangs after that. It never tries to get the bootx64.efi (required for
booting to the EFI mode) file after that.
We were trying the UEFI boot with Sles11sp164.
Has anyone executed chain loading using iPXE in UEFI environment?
Regards
Sanjeev
-Original Message-
From: Roy, Sanjeev
Sent: Thursday, December 22, 2011 12:32 AM
To: Michael Brown; ipxe-devel@lists.ipxe.org
Subject: RE: [ipxe-devel] Query on UEFI iPXE boot
Hi All,
We tried UEFI IPXE boot with an Intel igb CNA. The device ID was 10c9. We
built 808610c9.efi. However while trying the UEFI iPXE boot using the .efi file
we could see that the client is able to successfully download the.efi file. The
client 808610c9hangs after that. It never tries to get the bootx64.efi
(required for booting to the EFI mode) file after that.
We were trying the UEFI boot with Sles11sp164.
Has anyone executed chain loading using iPXE in UEFI environment?
Regards
Sanjeev
-Original Message-
From: Michael Brown [mailto:mbr...@fensystems.co.uk]
Sent: Saturday, December 17, 2011 1:02 AM
To: ipxe-devel@lists.ipxe.org
Cc: Roy, Sanjeev
Subject: Re: [ipxe-devel] Query on UEFI iPXE boot
On Wednesday 14 Dec 2011 12:32:10 sanjeev@emulex.com wrote:
We are using Emulex adapter.
We tried chainloading for EFI using iPXE similar to legacy boot, legacy
boot works fine.
The configuration change in dhcpd.conf is
if exists user-class and option user-class = iPXE {
filename bootx64.efi; # bootx64.efi is located @ tftp root
} else {
filename 808610de.efi; #808610de.efi is located @ tftp root
}
also tried with e1000e--r8169.efi and ipxe.efi instead of 808610de.efi
8086:10de is an Intel e1000 card. You need to use the PCI IDs for your Emulex
card instead.
Is there any specific way to generate the binary for Emulex adapter, which
is not been specified in e1000e_ich8lan.c, In this case how do we build
the driver image specific for this adapter.
Emulex adapters are not (as far as I am aware) direct equivalents of Intel
e1000 adapters. You need to create an iPXE driver for Emulex adapters (or pay
to have one created).
Michael
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Re: [ipxe-devel] SAN iso boot to install Win8 to SAN question..
On Friday 06 Jan 2012 02:30:23 Jarrod Johnson wrote: 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 0x81 for the optical drive. sanboot --drive 0x81 goes blank and reboots shortly. Then I swapped and hooked 0x80 as the optical and 0x81 as the hard drive. Installer started, Windows presented the blank disk I had provided, but Windows then refuses to install to the disk saying 'ensure that the disk's controller is enabled in the computer's BIOS menu'. I assume it's somehow unhappy with the state of what it determined through EDD, but Windows is fairly unhelpful in this regard. So two questions, has anyone tried windows install to 0x81 iscsi drive by ipxe? Alternatively, why wasn't I able to boot the iso if I hooked it to 0x81 instead of 0x80? Did you use --no-describe for the sanboot/sanhook commands referring to the ISO? Michael ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Re: [ipxe-devel] vmxnet3 port
On Friday 06 Jan 2012 08:51:47 Alessandro Salvatori wrote: so, ipxe never does polling for packets. a la Linux NAPI? It does; the problem is that the RX completion descriptors for the first packet is not written into the guest's memory until the second packet has been received. So far, I have been unable to think of a reason why this might be happening. Michael ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Re: [ipxe-devel] double null byte in dns_make_name()
On Wednesday 28 Dec 2011 07:50:56 Christian Hesse wrote: the dns resolver from current git does not work for me. Taking a look at the network layer I found there's a double null byte added in dns_make_name() causing the nameserver to not understand the query type and class. The attached patch fixes this. Applying your patch causes malformed DNS requests for me. That trailing NUL marks the end of the name being queried. Could you send a packet capture showing the double null behaviour that you describe? http://ipxe.org/howto/pcap Thanks, Michael ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
