When trying to disaster recover a VM from backup files you need all the disk, partitions, LVM info to match up the new system with the old. When you get this error message:
Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
It usually mean that it is referencing a disk, partition or LVM volume that it can't fine. Check out the /etc/fstab and remove those entries. For example, the original VM had this fstab configuration:
#
# /etc/fstab
# Created by anaconda on Tue Jun 9 09:18:57 2015
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/centos-root / ext4 defaults 1 1
UUID=f3371e3a-e4f9-4423-9bf3-dd7242ce4de9 /boot ext4 defaults 1 2
UUID=F7BA-C6DF /boot/efi vfat umask=0077,shortname=winnt 0 0
/dev/mapper/centos-home /home ext4 defaults 1 2
/dev/mapper/centos-opt /opt ext4 defaults 1 2
/dev/mapper/centos-tmp /tmp ext4 defaults 1 2
/dev/mapper/centos-var /var ext4 defaults 1 2
/dev/mapper/centos-swap swap swap defaults 0 0
The restored files went on to a system that had no /dev/mapper/centos-tmp LVM volume. This caused the error at boot asking for root password for maintenance!
