On 8/16/2013 at 01:16 PM, in message <1376680595.31373.10662789.2FC45E8F@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote: And that looks to be written by the do_start() function in xencommons. Maybe you can poke around there and see why
${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0"
is not being executed.
1st check, the write works @shell, but is not sticky at boot
xenstore-ls /local/domain/0 | grep "Domain-0" (empty) /usr/bin/xenstore-write "/local/domain/0/name" "Domain-0"
xenstore-ls /local/domain/0 | grep "Domain-0" -B3 -A3 feature-rx-copy = "1" feature-rx-flip = "0" hotplug-status = "connected" name = "Domain-0" xl list Name ID Mem VCPUs State Time(s) Domain-0 0 1241 4 r----- 57.2 test1 1 1024 2 -b---- 12.6 test2 2 1024 4 -b---- 32.7 shutdown -r now ... xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 43.5 test1 1 1024 2 -b---- 8.0 test2 2 1024 4 -b---- 29.1
checking in /etc/init.d/xencommons, the if clause that wraps it
if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1` then ...
echo Setting domain 0 name... ${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0" fi
I don't see the "Setting domain 0 name" @ boot
journalctl -b | grep -i xenstore Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store ... Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store complete. Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store ... Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store complete. Aug 16 12:00:44 testsvr.loc logger[4201]: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-status connected to xenstore. Aug 16 12:00:52 testsvr.loc logger[4420]: /etc/xen/scripts/vif-bridge: Writing backend/vif/2/0/hotplug-status connected to xenstore. Aug 16 12:00:52 testsvr.loc logger[4426]: /etc/xen/scripts/vif-bridge: Writing backend/vif/2/1/hotplug-status connected to xenstore.
testing, here, @ shell,
xenstore-read -s / (empty)
i'm staring at
if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1`
what exactly is the intent here?
It checks the status of xenstore to see if it is running by reading from the socket (-s). On failure, it executes the code to start xenstored. After loading xenstored it then hits a while loop checking for up to 30 seconds to see if things were properly setup. The only failure points are if xenstored is already running, xenstored could not be found, or it times out. - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org