flash10 vs f10; em(4) now broken in -current in qemu/vbox

Hi!

 I just made a new vbox/qemu -current guest to look at flash10 vs f10
(I made a raw image using qemu-img and gave that to vbox as per this
description,
	http://www.virtualbox.org/manual/UserManual.html#rawdisk
so that I can also mount it from the host using mdconfig and boot it
in qemu too), and noticed em(4) in both vbox and qemu now report
`Invalid MAC address' and consequently don't attach:

vbox:
em0: <Intel(R) PRO/1000 Network Connection 6.9.9> port 0xd010-0xd017 mem 0xf0000
000-0xf001ffff irq 19 at device 3.0 on pci0
em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xf0000000
em0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xd010
em0: Invalid MAC address
device_attach: em0 attach returned 5

qemu:
em0: <Intel(R) PRO/1000 Network Connection 6.9.9> port 0xc040-0xc07f mem 0xf2020
000-0xf203ffff irq 11 at device 3.0 on pci0
em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xf2020000
em0: Reserved 0x40 bytes for rid 0x14 type 4 at 0xc040
em0: Invalid MAC address
device_attach: em0 attach returned 5

 I had to switch to PCnet-PCI II in vbox and model=pcnet in qemu, both
driven by le(4) in the guest.  Btw, PCnet-FAST III in vbox also doesn't
work (driven by pcn(4)), it fails to dhcp, but that breakage also exists
in 7.2 so its much older.

 head snapshot where em(4) works: 8.0-HEAD-20090403-JPSNAP
 head snapshot where em(4) is broken: 8.0-HEAD-20090605-JPSNAP

 Anyway, on to www/linux-f8-flashplugin10 with OVERRIDE_LINUX_BASE_PORT
and OVERRIDE_LINUX_NONBASE_PORTS both f10:  I got that going after
removing libidn from the port's USE_LINUX_APPS (its part of linux_base-f10)
and installing two new dependencies of f10's libcurl:
	libldap-2.4.so.2 in openldap-2.4.12-1.fc10.i386.rpm
and
	libsasl2.so.2 in cyrus-sasl-lib-2.1.22-19.fc10.i386.rpm
(so we'll need two new ports for these), and then finally to get
libflashsupport working too (i.e., audio) I had to
	ln -s libssl.so.7 /compat/linux/lib/libssl.so.6
- so we probably need a new linux-f10-flashsupport too if we want to
avoid that symlink.

 Oh and btw I got a weird audio issue in vbox also: most of the times
audio plays too fast and sounds ugly (using snd_ich; this stays until
guest reboot), but I also had the guest boot a few times with proper
audio...

 Cheers,
	Juergen