What is the error when trying to start a new DomU in Xen?

Question

linux

Good day, colleagues.
I set up a new Xen host, I create a virtual machine, the virtual machine section is still empty. config (IP changed just in case):

memory = 2048
maxmem = 10000
name = 'test1'
vif = [ 'ip=77.77.1.1,mac=00:16:3e:58:70:15' ]
address = '77.77.1.1'
netmask = '255.255.255.0'
disk = ['phy:/dev/vg_ssd/test1_img,xvda1,w']
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra = "(hd0)/boot/grub/grub.conf"
vnc = 1
vnclisten = "0.0.0.0"
vncunused = 1
vncpasswd = "test___"
vfb = ['type=vnc,vncunused=1,vncpasswd=ch4t___,vnclisten=0.0.0.0']
vcpus = 2

and I get:

[[email protected] ~]# xl create /xen/test1.cfg
Parsing config from /xen/test1.cfg
libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 2: Bad file descriptor
libxl: error: libxl_create.c:745:initiate_domain_create: cannot make domain: -3
libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 2: Bad file descriptor
libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 2: Bad file descriptor
libxl: error: libxl.c:1370:domain_destroy_callback: unable to destroy guest with domid 2
libxl: error: libxl_create.c:1328:domcreate_destruction_cb: unable to destroy domain 2 following failed creation

I've been googling for a couple of hours now, but I still don't understand anything. Has anyone come across?
xl info:

host                   : xen
release                : 4.4.27-1.el6xen.x86_64
version                : #1 SMP Mon Oct 24 16:16:46 AEDT 2016
machine                : x86_64
nr_cpus                : 24
max_cpu_id             : 23
nr_nodes               : 2
cores_per_socket       : 6
threads_per_core       : 2
cpu_mhz                : 2666
hw_caps                : bfebfbff:2c100800:00000000:00003f00:009ee3fd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 49090
free_memory            : 47529
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 4
xen_extra              : .4
xen_version            : 4.4.4
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          :
xen_commandline        : dom0_mem=1024M cpufreq=xen dom0_max_vcpus=1 dom0_vcpus_pin
cc_compiler            : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-17)
cc_compile_by          : mockbuild
cc_compile_domain      : (none)
cc_compile_date        : Sat Oct  1 13:53:57 AEST 2016
xend_config_format     : 4

xml list:

Name                                        ID   Mem VCPUs      State   Time(s)
(null)                                       0  1024     1     r-----     311.8
(null)                                       1     0     0     --p---       0.0
(null)                                       2     0     0     --p---       0.0

Answer 1

And again I asked myself, I'm answering myself...)) When the server was loaded, DNS was probably not configured and this caused problems when starting some Xen services.
In general, it was enough to reboot. Facepalm...