Windows 7 + Extension Pack - PXE not trying

[dmacvittie]

Hello,

Edit: added zipped log file.

I've searched and searched, cannot find an answer to this one. I use VirtualBox a lot, so it's not a new user issue, and the extension pack is installed, so all of the results searching brings up are not relevant.

I have a brand new HP zBook 17 running Windows 7 Professional that I installed VirtualBox 4.3.22 r98236 win.amd64 on, then added the extension pack.

When I try to PXE boot any server, It does not seem to actually try the PXE boot.

In the VirtualBox boot log, it shows loading the ROM DLL and failure of the boot (snippets at the end of post).

The boot screen simply says "Unable to read from boot medium", it doesn't even print the header.

So I used VBManage to capture the traffic on the VM, and it shows no DHCP traffic at all. It doesn't appear to even be trying.

Interesting bit: This exact same setup works flawlessly in OS-X, displaying the boot prompt and issuing the request.
I've tried pulling the OS-X VMs over, and they behave the same - no attempt to execute PXE.

Probably unrelated info:
I have tried turning off all host firewall services.
I have tried this setup on both host only and internal networks.
I have tried this with a variety of NICs. Most relevant, have tried with both Intel Pro and PCNet virtual cards.

My current suspicion is that the DLL is failing in some way, but I cannot find a more detailed log.

Any help - pointers at more detailed logging for PXE, resolution to similar problems, whatever - would be appreciated.

Snippets from the VM boot log that are relevant (trying to keep size down, can post entire log if needed):

Extension pack is loading

Code: Select all

VirtualBox VM 4.3.22 r98236 win.amd64 (Feb 12 2015 15:53:11) release log
00:00:00.719105 Log opened 2015-02-14T17:32:31.323561200Z
00:00:00.719106 Build Type: release
00:00:00.719108 OS Product: Windows 7
00:00:00.719108 OS Release: 6.1.7601
00:00:00.719109 OS Service Pack: 1
00:00:00.741851 DMI Product Name: HP ZBook 17
00:00:00.743985 DMI Product Version: A3009DD10303
00:00:00.743989 Host RAM: 32377MB total, 28889MB available
00:00:00.743991 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:00.743992 Process ID: 2284
00:00:00.743992 Package type: WINDOWS_64BITS_GENERIC
00:00:00.744877 Installed Extension Packs:
00:00:00.744900   Oracle VM VirtualBox Extension Pack (Version: 4.3.22 r98236; VRDE Module: VBoxVRDP)

e1000 configuration

Code: Select all

00:00:00.856936 [/Devices/e1000/] (level 2)
00:00:00.856936 
00:00:00.856936 [/Devices/e1000/0/] (level 3)
00:00:00.856937   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:00.856938   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:00.856938   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:00.856939   Trusted       <integer> = 0x0000000000000001 (1)
00:00:00.856939 
00:00:00.856939 [/Devices/e1000/0/Config/] (level 4)
00:00:00.856940   AdapterType    <integer> = 0x0000000000000000 (0)
00:00:00.856941   CableConnected <integer> = 0x0000000000000001 (1)
00:00:00.856941   LineSpeed      <integer> = 0x0000000000000000 (0)
00:00:00.856942   MAC            <bytes>   = "08 00 27 6a ca 2f" (cb=6)
00:00:00.856943 
00:00:00.856943 [/Devices/e1000/0/LUN#0/] (level 4)
00:00:00.856944   Driver <string>  = "NetSniffer" (cb=11)
00:00:00.856945 
00:00:00.856945 [/Devices/e1000/0/LUN#0/AttachedDriver/] (level 5)
00:00:00.856946   Driver <string>  = "IntNet" (cb=7)
00:00:00.856946 
00:00:00.856947 [/Devices/e1000/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:00.856948   IfPolicyPromisc <string>  = "deny" (cb=5)
00:00:00.856948   Network         <string>  = "BigData" (cb=8)
00:00:00.856949   TrunkType       <integer> = 0x0000000000000002 (2)
00:00:00.856949 
00:00:00.856950 [/Devices/e1000/0/LUN#0/Config/] (level 5)
00:00:00.856951   File <string>  = "Documents\Node1.pcap" (cb=21)
00:00:00.856951 
00:00:00.856951 [/Devices/e1000/0/LUN#999/] (level 4)
00:00:00.856952   Driver <string>  = "MainStatus" (cb=11)
00:00:00.856953 
00:00:00.856953 [/Devices/e1000/0/LUN#999/Config/] (level 5)
00:00:00.856954   First   <integer> = 0x0000000000000000 (0)
00:00:00.856954   Last    <integer> = 0x0000000000000000 (0)
00:00:00.856955   papLeds <integer> = 0x0000000004be8f18 (79 597 336)
00:00:00.856956 

Netboot config

Code: Select all

00:00:00.857003 [/Devices/pcbios/0/Config/NetBoot/0/] (level 6)
00:00:00.857004   NIC           <integer> = 0x0000000000000000 (0)
00:00:00.857005   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:00.857006   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:00.857006   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:00.857007 

Loading Extensions

Code: Select all

00:00:01.036289 DevPcBios: Using LAN ROM 'C:\Program Files\Oracle\VirtualBox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/PXE-Intel.rom' with a size of 0xc000 bytes
00:00:01.041877 SUP: Loaded VBoxDDR0.r0 (C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0) at 0xfffff8800e600000 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000 using the native ring-0 loader
00:00:01.041887 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0=0xfffff8800e600000
00:00:01.045762 SUP: Loaded VBoxDD2R0.r0 (C:\Program Files\Oracle\VirtualBox\VBoxDD2R0.r0) at 0xfffff8800e629000 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000 using the native ring-0 loader
00:00:01.045769 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VBoxDD2R0.r0=0xfffff8800e629000
00:00:01.045793 Activating Local APIC

Totality of the error message

Code: Select all

00:00:04.335627 Guest Log: BIOS: Boot : bseqnr=1, bootseq=0234
00:00:04.336172 Guest Log: BIOS: Boot from LAN failed
00:00:04.336968 Guest Log: BIOS: Boot : bseqnr=2, bootseq=0023
00:00:04.338559 Guest Log: BIOS: CDROM boot failure code : 0003
00:00:04.339204 Guest Log: BIOS: Boot from CD-ROM failed
00:00:04.339904 Guest Log: BIOS: Boot : bseqnr=3, bootseq=0002
00:00:04.346121 Guest Log: BIOS: Booting from Hard Disk...

[socratis]

I haven't tried PXE booting, so I wouldn't be able to help you directly, but I do know from experience that a chopped up VBox.log is not the greatest way in the world to debug the problem. So, please zip and attach the full VBox.log of the failure.

[dataKEKS]

Same Problem on several systems. With Version 4.3.20 everything worked, after update to the new Version 4.3.22 PXE doesn´t work anymore

Best regards from Germany
dataKEKS

[dmacvittie]

Thanks socratis, will zip and attach ASAP.

dataKEKS... That's interesting, my MacBook (which works) is running 4.3.20. I may downgrade and try it out.

Thanks.
Don.

[Perryg]

These kinds of problems that are reproducible should be reported to bugtracker.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.

[dmacvittie]

Thank you dataKEKs, that got me going again. The link to download 4.3.20 Windows is broken, so I went back to 4.3.18. Since all of my environment from hardware up was new, and haven't had VB problems with PXE in a while, I assumed it as some odd zBook or Win7 config issue I'd missed, since there are enough of them.

Perryg: WIll report it when I have a few minutes to breath. This put me behind on a project, so catchup first, then I'll get it submitted. Until dataKEKs mentioned he had the same issue on upgrade, thought it was a localized problem.

Thanks again,
Don.

[michaln]

The link to download 4.3.20 Windows is broken, so I went back to 4.3.18

Which link is that? Something on https://www.virtualbox.org/wiki/Download_Old_Builds_4_3 ?

[michaln]

Reproduced the problem. Unfortunately there is no workaround I can think of except downgrading; it's the system BIOS that's slightly broken in a way that only affects PXE booting.

[CharonIDRONES]

Having the same issue on both Windows and Mac hosts PXE booting WDS/MDT server. Have downgraded on both and now working fine as it was before using 4.3.20 instead of 4.3.22.

[michaln]

Having the same issue on both Windows and Mac hosts PXE booting WDS/MDT server. Have downgraded on both and now working fine as it was before using 4.3.20 instead of 4.3.22.

If you really have a problem with PXE on an OS X host, please provide a VBox.log from an unsuccessful attempt to PXE boot. And probably post in the OS X host forum, too

I don't see any problem on a Mac -- but it is broken on Windows (VM doesn't even attempt to boot from network).

[dmacvittie]

For everyone who has joined the thread or is looking for a solution...

I finally found a minute to go enter this in bug tracker, and it appears someone else did, and it was fixed.

https://www.virtualbox.org/ticket/13842

The resolution says it was fixed in 4.3.24.

I have an exact duplicate of my laptop (HP zBook 17) that I will be trying it out on later this week, setting it up the same as the one I downgraded on, except for using the newest VirtualBox. Will post back here with results.

Don.