Re: Solved: run_hotplug_scripts=0 considered unhelpful with xentools45, was: Re: guests not starting properly on 7/amd64 dom0 freshly with xen45

[John Nemeth <jnemeth%cue.bc.ca@localhost>]

On Dec 30,  1:21pm, "S.P.Zeidler" wrote:
}
} So, to recap:
} 
} Symptom: all domU hang in kernel boot
} 
} Log:
} [...]
} xenbus0 at hypervisor0: Xen Virtual Bus Interface
} xencons0 at hypervisor0: Xen Virtual Console Driver
} xenbus: can't get state for device/suspend/event-channel (2)
} xbd0 at xenbus0 id 1: Xen Virtual Block Device Interface
} xennet0 at xenbus0 id 0: Xen Virtual Network Interface
} xennet0: MAC address 00:16:3e:30:30:61
} balloon0 at xenbus0 id 0: Xen Balloon driver
} balloon0: current reservation: 8388608 KiB
} xennet0: using RX copy mode
} xenbus: can't get state for device/suspend/event-channel (2)
} balloon0: current reservation: 2097152 pages => target: 2097152 pages
} ignore shutdown request: 
} xenbus: can't get state for device/suspend/event-channel (2)
} <- here
} 
} and upon inspection one sees that the xbd config thread has died instead
} of finishing work and reporting:
} 
} boot device: xbd0
} 
} 
} In this situation, running xbackendd allows one to start exactly one vm,
} and then further "xl create" calls will report that the hotplug setting
} cannot be changed while domains are running.

     xbackendd is leftover cruft for supporting the xm toolstack.
It should never be run when using the xl toolstack.  It will
definitely interfere with the operation of the xl toolstack.  I
have changed the xentools45 package to no longer build it, and am
planning on asking upstream to remove it.

} This is the hint with a tent pole that the hotplug setting for xl is wrong,
} and setting
} run_hotplug_scripts=1 
} (or commenting out the line) in /usr/pkg/etc/xen/xl.conf and a reboot
} will produce a "clean" dom0 that runs domUs as intended.

     I am confused by this.  The system I am running Xen 4.5 on is
using a completely stock xl.conf file and doesn't have any problems.
That system has xentools45-4.5.1nb5, which is the version that was
available when I setup the system.  What version of xentools are
you using?  Was your xl.conf modified in any way from the stock
one?

} For the benefit of people also upgrading from 4.2 to 4.5:
} 
} the disk specification syntax changes,
} disk = [ 'phy:/dev/sd0k,0x1,w' ] # old
} becomes
} disk = [ '/dev/sd0k,raw,0x1,rw' ] # new, for xl

     I still use the old syntax.  It is supported for compatibility.
This is not to discourage anybody from switching to the new syntax,
just to mention that it is possible to continue using the syntax
that you know.  The full documentation for the new syntax is
installed in /usr/pkg/share/doc/xen/xl-disk-configuration.txt for
recent versions of xentools45.

} The start scripts in /etc/rc.d should be copied freshly from
} /usr/pkg/share/examples/rc.d, and old xen rc.d scripts no longer present
} ought to be deleted. Also /usr/pkg/etc/xen/scripts should be checked for
} old scripts. Finally, there's no more xend and no more xm, use xl instead.

     I'll just re-iterate these points.  It is very important to
use the new rc.d scripts.

}-- End of excerpt from "S.P.Zeidler"