Dear Maintainer,

This started when I upgraded from Debian 9 (Xen 4.8, Kernel 4.9) to Debian 10 (Xen 4.11, Kernel 4.19).
It still occurred after attempting a boot with the old Xen 4.8/Kernel 4.9.
Line 88 of vif-nat attempts to assign a "hostname" variable using xenstore_read.
This key "backend/vif/x/x/domain" does not exist in xenstore, so the script errors out, aborting the domU creation.
Upon further inspection, this "hostname" is only used when DHCP is enabled, so I commented out line 88 for my personal use.
The script still errored after that, but I believe that is a separate issue and I am submitting a separate bug for it.
I believe I even saw these "unable to read backend/vif/x/x/domain" messages on the console while shutting down the dom0 for the first reboot after installing Debian 10.
I looked into various things that might cause access restrictions, but it seems the real cause is just that key "backend/vif/x/x/domain" not existing (I don't know what's supposed to put those keys into that part of the xenstore), and the script trying to read it.


Thanks for your attention,
Paul