Kb273

Emulab FAQ: Software Setup: What device drivers do I need in my operating system to run in Emulab?

NOTE: this entry refers to the Utah Emulab only.

FreeBSD

The easiest thing to do is to use a GENERIC kernel. All current Emulab hardware is supported by this configuration. Note that some newer node types require recent versions of drivers. FreeBSD 6 (aka STABLE), as of 5/1/07 should work with all current Emulab hardware.

Critical device drivers (disk, network) should be linked into the kernel, there is no boot time support for including needed device drivers.

If you are customizing your kernel, use /share/freebsd/''<version>''/src/sys/i386/conf/TESTBED as an example.

The particular hardware, and the drivers required follows.

• pc600, pc850:
  • disk: ata, atadisk
  • network: fxp
  • other: atkbdc, atkbd, psm, kbdmux, vga, sio, loop, random, ether, tun, pty, md, bpf
  • notes: uniprocessor
• pc2000:
  • disk: ata, atadisk
  • network: fxp, em
  • other: atkbdc, atkbd, psm, kbdmux, vga, sio, loop, random, ether, tun, pty, md, bpf
  • notes: uniprocessor, ACPI support should be disabled, there is an unconnected 'xl' NIC in each
• pc3000:
  • disk: mpt, scbus, da, pass, ses
  • network: em
  • other: atkbdc, atkbd, psm, kbdmux, vga, sio, loop, random, ether, tun, pty, md, bpf
  • notes: uniprocessor, 64-bit
• pc3000w:
  • disk: ata, atadisk
  • network: em, ath
  • other: atkbdc, atkbd, psm, kbdmux, vga, sio, loop, random, ether, tun, pty, md, bpf
  • notes: uniprocessor, 64-bit, requires FreeBSD 5+ for SATA support, wireless interfaces

Linux

Network drivers are loaded dynamically via /etc/sysconfig/network-scripts/ifcfg-eth99 and should not be statically linked into the kernel.

Windows

Don't even try...