>Number:         37370
>Category:       kern
>Synopsis:       xen dom0 kernel does not support guest domU's on dk wedges
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 12 17:35:00 +0000 2007
>Originator:     Ronald Roskens
>Release:        NetBSD 4.0RC4
>Organization:
>Environment:
NetBSD xendom0 4.0_RC4 NetBSD 4.0_RC4 (LOCAL_XEN3_DOM0) #0: Fri Nov  9 21:39:02 CST 2007  root@xendom0:/usr/src/sys/arch/i386/compile/LOCAL_XEN3_DOM0 i386
>Description:
After enabling dkwedges (adding drvctl, and the assorted DKWEDGE_* to the kernel config file), bootup into a XEN DOM0 environment using the /dev/dk* devices. Attempt to create a new domU, but watch it hang while probing disks. In dom0's dmesg:

xbdback backend/vbd/7/3: can't ioctl device 0xa805: 25
xvif7.0: Ethernet address aa:00:00:01:00:02
xbd backend: attach device vnd0d (size 495020) for domain 7
xbd backend 0x3 for domain 7 using event channel 28
xbd backend 0x603 for domain 7 using event channel 29

The xen dom0 device xbdback is attempting to do a DIOCGPART ioctl on the  dkwedge device and is failing.

==== xen config ====
#kernel = "/netbsd-XEN3_DOMU"
kernel = "/netbsd-INSTALL_XEN3_DOMU"

memory = 64
name = "nbsd"
vif = [ 'mac=aa:00:00:00:00:02, bridge=bridge1' ]
disk = [ 'phy:/dev/dk5,wd0d,w', 'file:/d/xen/ISOs/netbsd-4-0-rc4-i386cd.iso,cd0d
,r' ]

root = "/dev/wd0d"
==== end xen config ====


>How-To-Repeat:
1) Create a new XEN3_DOM0 kernel adding:

pseudo-device   drvctl
options         DKWEDGE_AUTODISCOVER
options         DKWEDGE_METHOD_BSDLABEL
options         DKWEDGE_METHOD_GPT
options         DKWEDGE_METHOD_MBR

2) Boot into new XEN3_DOM0 kernel, and setup a raw/phy partition for dom0

disklabel -e wd0
** add slice i
dkctl wd0 addwedge wd0i 64645056 21564144 unknown

3) Start up guest domU, and it hangs while probing devices. You have to hit ESC and run 'xm destroy <domu>' to kill the guest domU.


>Fix: