Date: Fri, 02 Mar 2012 00:29:33 +1000 From: Da Rock <freebsd-questions@herveybayaustralia.com.au> To: freebsd-questions@freebsd.org Subject: Re: VBox network boot Message-ID: <4F4F87CD.2060505@herveybayaustralia.com.au> In-Reply-To: <4F4EA742.5030104@gmail.com> References: <4F4CD476.4020005@herveybayaustralia.com.au> <alpine.BSF.2.00.1202280910180.72698@wonkity.com> <87d38yc2is.fsf@oak.localnet> <4F4D6C99.1000604@herveybayaustralia.com.au> <4F4EA742.5030104@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/01/12 08:31, Andrei Brezan wrote: > On 29/02/2012 01:08, Da Rock wrote: >> On 02/29/12 03:04, Carl Johnson wrote: >>> Warren Block<wblock@wonkity.com> 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! >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" > Hi all, > > You can also look at https://www.virtualbox.org/wiki/Downloads and > https://www.virtualbox.org/manual/ch01.html#intro-installing 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 The extensions don't work with FBSD. Period. End of story. Oracle is _very_ clear about that- they won't support FBSD at all, and show no mercy to those who complain. It is possible to write your own though... BTW, is anyone aware if the patches are still required? I'm getting "<address> is not in my arp table". I'm using booting techniques as describe by Warren (gpxelinux.0, menu, and chain loading), and I have pxeboot sent over using tftp and boot off nfs. And that is why the error shows up - the address is the nfs server. I'm not sure the patches help this though... This works (mostly) using real hardware. It snags on the next stage.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F4F87CD.2060505>