NetBSD DOMU Xen 4.2 xl lvm disk

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

I had a working NetBSD DOMU Xen 4.2 xl using a vnd as a disk. I thought
I would try out lvm for the first time, but I get

  xenbus: can't get state for device/suspend/event-channel (2)

which was an issue in an earlier thread of the same name - except here
I think that the volume is accessible...

# more quantz.cfg 
name = "quantz"
kernel = "/usr/pkg/etc/xen/quantz/netbsd-XEN3_DOMU.gz"
vcpus = 1
memory = 512
disk = ['phy:/dev/vg0/quantz,hda,w']
vif = ['bridge=bridge0']
on_reboot = 'restart'
on_crash = 'destroy'
# lvm lvdisplay
  --- Logical volume ---
  LV Name                /dev/vg0/quantz
  VG Name                vg0
  LV UUID                Hxsogk-cGeo-Yrrp-V0HU-KFUo-Aec5-99tHwg
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                20.00 GiB
  Current LE             5120
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     0
  Block device           169:1
# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0   512     1     r-----    1111.3
quantz                                       8   512     1     -b----       1.1
# xl block-list 8
Vdev  BE  handle state evt-ch ring-ref BE-path                       
768   0   8      3     6      511      /local/domain/0/backend/vbd/8/768
# ps axw | grep xen
 1371 ?       Il    0:00.14 /usr/pkg/sbin/xenconsoled 
 5327 ?       I     0:00.49 /usr/pkg/sbin/xenstored --pid-file 
/var/run/xenstored.pid 
14733 ttyp0   Il+   0:00.00 /usr/pkg/bin/xenconsole --num 0 --type pv 8 
  883 xencons Is+   0:00.00 /usr/libexec/getty Pc console 

(I tried running xenbackend too just in case, but isn't it replaced by
xenstored in the new world of xl?)

Is that the right "disk=" syntax?

Cheers,

Patrick