Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Feb 2012 23:31:30 +0100
From:      Andrei Brezan <>
Subject:   Re: VBox network boot
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <87d38yc2is.fsf@oak.localnet> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 29/02/2012 01:08, Da Rock wrote:
> On 02/29/12 03:04, Carl Johnson wrote:
>> Warren Block<>  writes:
>>> On Tue, 28 Feb 2012, Da Rock wrote:
>>>> I'm starting to believe this dog won't hunt (in fact is dead,
>>>> bloated, and full of worms...); but has anyone got a solution for
>>>> network booting in VBox on FBSD host?
>>> To PXE-boot a VM guest, set networking to to Bridged and use the
>>> PCnet-PCI II (Am79C970A) adapter type.  If the host is FreeBSD, the
>>> vboxnet kernel module has to be loaded.
>> Please emphasize that the PCnet-PCI II card emulation is necessary.  I
>> was trying the Intel emulation and making no progress.  I then noticed
>> your page and tried the PCnet-PCI II card and it started working.  I
>> would guess that means their Intel card emulation is incomplete.
> I took it for granted the bridge part (I usually use it anyway), but I 
> would never have guessed the PCnet card in a blue fit! There was even 
> a PR on virtualbox for the issue of the lack of PXE with Oracle 
> basically saying "too bad, so sad...". Apparently PXE licensing didn't 
> allow them to distribute it directly, but offer an extension pack 
> (which doesn't work on FBSD) instead. Ergo my conclusion. Apparently 
> (based on this thread) it only affects intel cards though...
> Where is your page Warren, and why didn't it show up in my searches? 
> ;) I'll follow it from here on out I think...
> Thanks guys... saved me a lot more fussing!
> _______________________________________________
> mailing list
> To unsubscribe, send any mail to 
> ""
Hi all,

You can also look at and for info 
related to the extension pack where you can find the PXE boot ROM for 
the Intel E1000 cards, unfortunately it's PUEL, virtualbox on FBSD is 
OSE. My worst case scenario was with a custom linux kernel on the guest 
that didn't had drivers for Amd cards, I had to do something like this:

NIC 1:           MAC: 0800276F42C6, Attachment: Bridged Interface 
'bridge0', Cable connected: on, Trace: off (file: none), Type: 
Am79C970A, Reported speed: 0 Mbps, Boot priority: 0
NIC 2:           MAC: 0800276F42C6, Attachment: Bridged Interface 
'bridge0', Cable connected: on, Trace: off (file: none), Type: 82540EM, 
Reported speed: 0 Mbps, Boot priority: 0


Andrei Brezan
email<andrei693 [at]>

Want to link to this message? Use this URL: <>