We've identified a workaround that can get the VM uuid:
root@ubuntulucidlynx1004:~# xenstore-read domid 2 root@ubuntulucidlynx1004:~# xenstore-read /local/domain/2/vm /vm/6fddd486-b376-647d-d7d4-9acf0e164722
It is the /vm/<uuid> path which has the incorrect permissions, however the UUID is in /local/domain/<domid>/vm which is all that is needed for nova to identify itself to the host.
We've identified a workaround that can get the VM uuid:
root@ubuntuluci dlynx1004: ~# xenstore-read domid dlynx1004: ~# xenstore-read /local/domain/2/vm b376-647d- d7d4-9acf0e1647 22
2
root@ubuntuluci
/vm/6fddd486-
It is the /vm/<uuid> path which has the incorrect permissions, however the UUID is in /local/ domain/ <domid> /vm which is all that is needed for nova to identify itself to the host.