Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello Bruno, I ran into the same bug as you and after searching the web I found this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591456#40 The file /etc/xen/scripts/hotplugpath.sh is missing in xen-utils-common_4.0.0-1_all.deb and it contains: SBINDIR="/usr/sbin" BINDIR="/usr/bin" LIBEXEC="/usr/lib/xen/bin" LIBDIR="/usr/lib64" SHAREDIR="/usr/share" PRIVATE_BINDIR="/usr/lib64/xen/bin" XENFIRMWAREDIR="/usr/lib/xen/boot" XEN_CONFIG_DIR="/etc/xen" XEN_SCRIPT_DIR="/etc/xen/scripts" You can create /etc/xen/scripts/hotplugpath.sh manually or maybe install xen-utils-common (4.1.0~rc6-1) from unstable. Hope that helps you although since your message are 10 weeks gone. Regards, Matthias 2011/1/17 Bruno Voigt <bruno at voigt.tv>: > Hi all, > > I've upgraded an xen+drbd+lvm debian system to squeeze. > The DomUs utilize DRBD-ressources for storage (based on local LV) > Unfortunately the block-drbd helper script provided by drbd8-utils > doesn't seem to work anymore: > > root at xena:~# xm create -c /etc/xen/bldlenny32.cfg > Using config file "/etc/xen/bldlenny32.cfg". > root at xena:~# Error: Device 51714 (vbd) could not be connected. Hotplug > scripts not working. > > I can start the DomU if a change the domU cfg > > from > disk = [ 'drbd:bldlenny32-disk,xvda2,w', 'drbd:bldlenny32-swap,xvda1,w'] > to > disk = [ 'phy:/dev/drbd/by-res/bldlenny32-disk,xvda2,w', > 'phy:/dev/drbd/by-res/bldlenny32-swap,xvda1,w'] > > and of course then having to manually changing the DRBD ressource states > to primary before start: > drbdadm primary bldlenny32-disk bldlenny32-swap > > The block-drbd helper script works on an older system with debian/lenny > (+ some parts of older sid) > > I also tried the newest block-drbd from the drbd 8.3 git repository, > it is identical to the one in the debian-package. > > Does anyone have a working configuration using the drbd: naming scheme? > > Installed packages: > > ii drbd8-utils 2:8.3.7-2.1 > ii linux-image-2.6.32-5-xen-amd64 2.6.32-30 > ii linux-image-xen-amd64 2.6.32+28 > ii linux-modules-2.6.26-2-xen-amd64 > ii xen-docs-4.0 4.0.1-2 > ii xen-hypervisor-4.0-amd64 4.0.1-2 > ii xen-linux-system-2.6.32-5-xen-amd64 2.6.32-30 > ii xen-qemu-dm-4.0 4.0.1-2 > ii xen-utils-4.0 4.0.1-2 > ii xen-utils-common 4.0.0-1 > ii xenstore-utils 4.0.1-2 > > /etc/xen/bldlenny32.cfg: > > name = 'bldlenny32' > kernel = '/boot/vmlinuz-2.6.26-2-xen-amd64' > ramdisk = '/boot/initrd.img-2.6.26-2-xen-amd64' > extra = 'clocksource=jiffies' > memory = '1024' > root = '/dev/xvda2 ro' > disk = [ 'drbd:bldlenny32-disk,xvda2,w', > 'drbd:bldlenny32-swap,xvda1,w', > ] > dhcp = 'dhcp' > vif = [ 'bridge=brvlan1, mac=00:16:3E:40:FB:EE' ] > > Thanks in advance for any hints, > Bruno > -- bruno a t voigt.tv