On Jul 22, 2013 5:27 PM, "Gene Cumm" <gene.cumm at gmail.com> wrote:> > On Mon, Jul 22, 2013 at 11:36 AM, Matt Fleming <matt at console-pimps.org>wrote:> > On Sat, 20 Jul, at 09:48:38AM, Victor Sudakov wrote: > >> Negative. > >> > >> I have changed the stanza into > >> > >> label WDS > >> menu LABEL ^4. Windows Deployment Service > >> com32 pxechn.c32 > >> append 10.14.140.128::boot\x86\wdsnbp.com -W > >> > >> and got the following result on VirtualBox: > >> > >> pxechn.c32: Attempting to load '10.14.140.128::boot\x86\wdsnbp.com':10.14.140.128 is not in my arp table!> >> 10.14.140.128 is not in my arp table! > >> 10.14.140.128 is not in my arp table! > >> 10.14.140.128 is not in my arp table! > >> 10.14.140.128 is not in my arp table! > >> 10.14.140.128 is not in my arp table! > > > > Gene, any more ideas? > > > > -- > > Matt Fleming, Intel Open Source Technology Center > > I have no clue where these messages come from. Likely VirtualBox's stack > > -- > -GeneBingo: https://www.virtualbox.org/ticket/3619 Victor, could you try Suslinux 6.02-pre14? I see you're already in the latest VirtualBox. What NIC type? Does the guest OS hint influence this? Does anyone else with VirtualBox use multiple tftpds (or could quickly test) to say if there's a known functioning version of VirtualBox? --Gene
On 07/26/2013 02:59 PM, Gene Cumm wrote:> > Bingo: https://www.virtualbox.org/ticket/3619 >Please don't advocate gPXE anymore... that project is dead. Anyone switching should be switching to iPXE. -hpa
On Fri, Jul 26, 2013 at 7:01 PM, H. Peter Anvin <hpa at zytor.com> wrote:> On 07/26/2013 02:59 PM, Gene Cumm wrote: >> >> Bingo: https://www.virtualbox.org/ticket/3619 >> > > Please don't advocate gPXE anymore... that project is dead. Anyone > switching should be switching to iPXE.I didn't meant to endorse/advocate either. I only was stating that looked like the exact error (which appears to be Etherboot and not gPXE). -- -Gene
Gene Cumm wrote:> > >> Negative. > > >> > > >> I have changed the stanza into > > >> > > >> label WDS > > >> menu LABEL ^4. Windows Deployment Service > > >> com32 pxechn.c32 > > >> append 10.14.140.128::boot\x86\wdsnbp.com -W > > >> > > >> and got the following result on VirtualBox: > > >> > > >> pxechn.c32: Attempting to load '10.14.140.128::boot\x86\wdsnbp.com': > 10.14.140.128 is not in my arp table! > > >> 10.14.140.128 is not in my arp table! > > >> 10.14.140.128 is not in my arp table! > > >> 10.14.140.128 is not in my arp table! > > >> 10.14.140.128 is not in my arp table! > > >> 10.14.140.128 is not in my arp table! > > > > > > Gene, any more ideas? > > > > > > -- > > > Matt Fleming, Intel Open Source Technology Center > > > > I have no clue where these messages come from. Likely VirtualBox's stack > > > > Bingo: https://www.virtualbox.org/ticket/3619Are you sure? From what I could gather, this bug involves multiple DHCP servers. I have only one.> > Victor, could you try Suslinux 6.02-pre14? I see you're already in the > latest VirtualBox. What NIC type? Does the guest OS hint influence this? > Does anyone else with VirtualBox use multiple tftpds (or could quickly > test) to say if there's a known functioning version of VirtualBox?I am on vacation presently. If I happen to be at my workplace next week, I will. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov at sibptus.tomsk.ru
On Fri, Jul 26, 2013 at 11:37 PM, Victor Sudakov <vas at mpeks.tomsk.su> wrote:> Gene Cumm wrote: >> > >> Negative. >> > >> >> > >> I have changed the stanza into >> > >> >> > >> label WDS >> > >> menu LABEL ^4. Windows Deployment Service >> > >> com32 pxechn.c32 >> > >> append 10.14.140.128::boot\x86\wdsnbp.com -W >> > >> >> > >> and got the following result on VirtualBox: >> > >> >> > >> pxechn.c32: Attempting to load '10.14.140.128::boot\x86\wdsnbp.com': >> 10.14.140.128 is not in my arp table! >> > >> 10.14.140.128 is not in my arp table! >> > >> 10.14.140.128 is not in my arp table! >> > >> 10.14.140.128 is not in my arp table! >> > >> 10.14.140.128 is not in my arp table! >> > >> 10.14.140.128 is not in my arp table! >> > > >> > > Gene, any more ideas? >> > > >> > > -- >> > > Matt Fleming, Intel Open Source Technology Center >> > >> > I have no clue where these messages come from. Likely VirtualBox's stack >> > >> >> Bingo: https://www.virtualbox.org/ticket/3619 > > Are you sure? From what I could gather, this bug involves multiple > DHCP servers. I have only one.1) It's more that I see the source of the messages. 2) It feels to me that once VirtualBox's stack loads a NBP via TFTP from one IPv4 address, it has difficulty with any other IPv4 address. It's as if it either ignores other ARP responses (perhaps by not listening or by only having a table for 1) or can't send the ARP request.>> Victor, could you try Suslinux 6.02-pre14? I see you're already in the >> latest VirtualBox. What NIC type? Does the guest OS hint influence this? >> Does anyone else with VirtualBox use multiple tftpds (or could quickly >> test) to say if there's a known functioning version of VirtualBox? > > I am on vacation presently. If I happen to be at my workplace next > week, I will.No problem. I have a feeling that VirtualBox bug has existed across versions but can't be sure. -- -Gene