Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
appnotes:gpxeonvmware [2010/04/12 20:24]
rulerof Changed first screenshot to one of the BIOS showing gPXE instead of the boot menu.
appnotes:gpxeonvmware [2010/06/04 01:46] (current)
bradskins
Line 31: Line 31:
  * On the image creation page, set the options to:  * On the image creation page, set the options to:
  - Output format: **ROM binary (flashable) image (.rom)**  - Output format: **ROM binary (flashable) image (.rom)**
- - NIC type: **e1000_84250**+ - NIC type: **e1000_82540**
  - PCI Vendor Code: **8086**  - PCI Vendor Code: **8086**
  - PCI Device Code: **100f**  - PCI Device Code: **100f**
Line 37: Line 37:
 <​code>​gpxe-1.0.0+-8086100f.rom</​code>​ <​code>​gpxe-1.0.0+-8086100f.rom</​code>​
  * Now, let's skip to [[#​locating_the_vm_s_.vmx_configuration_file|locating your VM's configuration file.]] \\ \\  * Now, let's skip to [[#​locating_the_vm_s_.vmx_configuration_file|locating your VM's configuration file.]] \\ \\
- 
- 
 ==== > Option 2 (Advanced): Compile the binary ROM from source ==== ==== > Option 2 (Advanced): Compile the binary ROM from source ====
 ---------- ----------
Line 51: Line 49:
 user@user-ubuntu:​~/​gpxe-1.0.0+/​gpxe/​src$ user@user-ubuntu:​~/​gpxe-1.0.0+/​gpxe/​src$
 </​code>​ </​code>​
- * Now, copy the output file, **bin/​8086100f.bin**, to the directory your VM resides in+ * Now, copy the output file, **bin/​8086100f.rom**, to the directory your VM resides in
 <​code>​ <​code>​
 user@user-ubuntu:/​home/​user/​gpxe-1.0.0+/​gpxe/​src#​ cp bin/​8086100f.rom /​home/​user/​Virtual\ Machines/​WinXP/​ user@user-ubuntu:/​home/​user/​gpxe-1.0.0+/​gpxe/​src#​ cp bin/​8086100f.rom /​home/​user/​Virtual\ Machines/​WinXP/​
Line 77: Line 75:
  * You should now have your ROM image, which as per the example pictured here is **gpxe-1.0.0+-8086100f.rom**,​ in the same folder as the .vmx file.\\  * You should now have your ROM image, which as per the example pictured here is **gpxe-1.0.0+-8086100f.rom**,​ in the same folder as the .vmx file.\\
 {{:​appnotes:​rom-copied.jpg}}\\ {{:​appnotes:​rom-copied.jpg}}\\
- 
 ===== Editing the .vmx file ===== ===== Editing the .vmx file =====
 Now we need to open the .vmx file in your text editor of choice. ​ Unfortunately for us, .vmx files are set to open with VMware Workstation by default, so, if you're using Windows, you need to right click the .vmx file and click "Open With..."​.\\ ​ If a sub-menu comes up from clicking "Open With", click "​Choose Default Program..."​\\ ​ Now we need to open the .vmx file in your text editor of choice. ​ Unfortunately for us, .vmx files are set to open with VMware Workstation by default, so, if you're using Windows, you need to right click the .vmx file and click "Open With..."​.\\ ​ If a sub-menu comes up from clicking "Open With", click "​Choose Default Program..."​\\ ​
Line 88: Line 85:
  * The second line adds the gPXE ROM to the Virtual NIC's ROM:  * The second line adds the gPXE ROM to the Virtual NIC's ROM:
 <​code>​e1000bios.filename = "​gpxe-1.0.0+-8086100f.rom"</​code>​ <​code>​e1000bios.filename = "​gpxe-1.0.0+-8086100f.rom"</​code>​
-__Note__: The text "​**gpxe-1.0.0+-8086100f.rom**"​ corresponds to the file that you downloaded from ROM-o-matic and then copied to the VM's folder in the above steps. ​ Your ROM's filename will likely be different.\\ \\+__Note__: The text "​**gpxe-1.0.0+-8086100f.rom**"​ corresponds to the file that you downloaded from ROM-o-matic and then copied to the VM's folder in the above steps. ​ Your ROM's filename will likely be //​slightly// ​different.\\ \\
 {{:​appnotes:​vmx-file-modified.jpg|Example of edited .vmx file}}\\ {{:​appnotes:​vmx-file-modified.jpg|Example of edited .vmx file}}\\
  * Once you've finished adding those lines to your .vmx file, save it and close it. \\  * Once you've finished adding those lines to your .vmx file, save it and close it. \\
Line 118: Line 115:
  * To this author'​s knowledge, aside from watching while booting the VM or editing the .vmx file, there'​s no way to determine from the Workstation (or Infrastructure Manager) UI that a modified NIC ROM has been applied to a VM.  * To this author'​s knowledge, aside from watching while booting the VM or editing the .vmx file, there'​s no way to determine from the Workstation (or Infrastructure Manager) UI that a modified NIC ROM has been applied to a VM.
  * Lines in the .vmx file can be commented out with a semicolon (;) and the next setting begins on the next non-blank new line.  If you'd like to switch back and forth between settings introduced through manual .vmx file editing, like if you had several different ROM images each with a different embedded script, you can change between them by commenting in and out different settings.  * Lines in the .vmx file can be commented out with a semicolon (;) and the next setting begins on the next non-blank new line.  If you'd like to switch back and forth between settings introduced through manual .vmx file editing, like if you had several different ROM images each with a different embedded script, you can change between them by commenting in and out different settings.
- 

QR Code
QR Code appnotes:gpxeonvmware (generated for current page)