Issues (network, drive) with NetBSD5.0.1/amd64 as HVM guest

[Erik Berls <cyber%netbsd.org@localhost>]

Hi all,

I tried to fire up one of my domUs as an HVM.

I ran into the expected issues with network timeouts on re0, but poked
at the other models:
e1000: detects as wm0, but fails to probe mac address, thus not configured
e100: detects as fxp0, but fails to detect EEPROM size (also wrong mac address)
ne2k_pci, pcnet: were 10baseT-FDX, probed, but not tested ne0?, pcn0)

(anyone know what the actual model is for the re0?  I got it by not
specifying a model= line.  Any I missed?)

The big fatal problem I ran into was the non-ability to use the second
drive.  I just got hit with timeouts.  It would disklabel but not
mount.

Anyone else see this?  Did I just do something stupid?


- dom0 is NetBSD5.0.1
- (XEN) Xen version 3.3.0 (bouyer@) (gcc version 4.1.3 20080704
prerelease (NetBSD nb2 20081120)) Sat Jan 17 08:05:27 UTC 2009
- config file for my domU:

name = "dev0-hvm"
memory = 2048
cpus = ["0", "1"]
vcpus = 2

kernel = "/usr/pkg/lib/xen/boot/hvmloader"
builder = 'hvm'
device_model = '/usr/pkg/libexec/qemu-dm'

disk = [ 'file:/n/xen/IMG/dev0,ioemu:hda,w', 'phy:/dev/wd0e,hdb,w' ]

vif = [ 'mac=00:16:3e:00:00:13, bridge=bridge0, type=ioemu' ]

vnc = 1
vncdisplay = 0
vncunused = 0

boot = "c"
extra = "-s"

Thanks,
-=erik.

-- 
"Exactly two things have made airline travel safer since 9/11:
reinforcement of cockpit doors, and passengers who now know that they
may have to fight back. Everything else ... is security theater."
--Bruce Schneier