|
@@ -1,16 +1,18 @@
|
1
|
1
|
Build using this command line:
|
2
|
2
|
|
3
|
|
-make CONFIG=vbox EMBED=config/vbox/embedded.ipxe bin/intel--virtio-net--pcnet32.rom
|
|
3
|
+make CONFIG=vbox bin/intel--virtio-net--pcnet32.isarom
|
4
|
4
|
|
5
|
5
|
Max size of a VirtualBox ROM is 56KB, 57344 bytes. There should be no need
|
6
|
6
|
to pad the image as long as the binary is smaller or equal to this size.
|
7
|
7
|
|
8
|
|
-The embedded script is required because VirtualBox uses the ROM as an ISA
|
9
|
|
-ROM, which will not perform any autoboot behavior. The bundled embedded
|
10
|
|
-script reproduces the default autoboot behavior.
|
11
|
|
-
|
12
|
8
|
To use the ROM in VirtualBox you need to enable it using this command:
|
13
|
9
|
|
14
|
10
|
vboxmanage setextradata global \
|
15
|
11
|
VBoxInternal/Devices/pcbios/0/Config/LanBootRom \
|
16
|
|
- path/to/intel--virtio-net--pcnet32.rom
|
|
12
|
+ /absolute/path/to/intel--virtio-net--pcnet32.isarom
|
|
13
|
+
|
|
14
|
+NB: If you build the ROM using the .rom prefix then it'll be built as a PCI
|
|
15
|
+ROM, which won't work properly in VirtualBox. The error message you'll see
|
|
16
|
+is "No more network devices", which is somewhat confusing. If you enter the
|
|
17
|
+shell and use the "autoboot" command things will work as intended. Remember
|
|
18
|
+to always build as a .isarom to avoid this issue.
|