problems with vnc

["Michael Litchard" <michael%schmong.org@localhost>]

I'm trying to create a framebuffer device using vnc, following the
example scripts in the latest pkgsrc.
Here's what my script looks like


<snip>
# Kernel image file.
#kernel = "/usr/pkg/etc/xen/kernels/netbsd-XEN3_DOMU.gz"
#kernel = "/netbsd-INSTALL_XEN3_DOMU.gz"
kernel = "/netbsd-XEN3_DOMU2"

# Initial memory allocation (in megabytes) for the new domain.
memory = 384

# A name for your domain. All domains must have different names.
name = "netbsd2"

vfb = [ 'type=vnc' ]
#----------------------------------------------------------------------------
# network configuration.
# The mac address is optionnal, it will use a random one if not specified.
# By default we create a bridged configuration; when a vif is created
# the script /usr/pkg/etc/xen/scripts/vif-bridge is called to connect
# the bridge to the designated bridge (the bridge should already be up)
vif = [ 'bridge=bridge0' ]

#it's possible to use a different script when the vif is created;
# for example to use a routed setup instead of bridged:
#vif = [ 'mac=00:16:3e:00:00:11, ip=10.0.0.1 netmask 255.255.255.0,
script=vif-ip'
 ]

#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
# For NetBSD guest DEV doesn't matter, so we can just use increasing numbers
# here. For linux guests you have to use a linux device name (e.g. hda1)
# or the corresponding device number (e.g 0x301 for hda1)

#disk = [ 'file:/home/domains/netbsd1,0x1,w' ]
disk = ['phy:/dev/wd0h,0x1,w']

<snip>

This is the error I get

# /usr/pkg/sbin/xm create -c /usr/pkg/share/examples/xen/netbsd2
Using config file "/usr/pkg/share/examples/xen/netbsd2".
Error: Device 0 (vkbd) could not be connected. Hotplug scripts not working

I did some googling and all I could find were some problems from
january of this year.
Is this a known issue? What can I do to troubleshooting this?

Thanks,
           Michael Litchard