We suspect it may be a permissions bug in the way xenstore is set up by XAPI.
# list_domains id | uuid | state 5 | 0dae370c-753d-5ef0-e3e0-e3a5e93d6203 | B
# xenstore-ls -fp | grep /vm/0dae370c-753d-5ef0-e3e0-e3a5e93d6203/uuid /vm/0dae370c-753d-5ef0-e3e0-e3a5e93d6203/uuid = "0dae370c-753d-5ef0-e3e0-e3a5e93d6203" (n0,r1)
This suggests that even though the domain ID post-reboot has been updated, the xenstore permissions have not been updated (the domain was previously domain 1 - hence the r1 permission)
We suspect it may be a permissions bug in the way xenstore is set up by XAPI.
# list_domains 753d-5ef0- e3e0-e3a5e93d62 03 | B
id | uuid | state
5 | 0dae370c-
# xenstore-ls -fp | grep /vm/0dae370c- 753d-5ef0- e3e0-e3a5e93d62 03/uuid 753d-5ef0- e3e0-e3a5e93d62 03/uuid = "0dae370c- 753d-5ef0- e3e0-e3a5e93d62 03" (n0,r1)
/vm/0dae370c-
This suggests that even though the domain ID post-reboot has been updated, the xenstore permissions have not been updated (the domain was previously domain 1 - hence the r1 permission)