[Xen-devel] Fail to initialize dom0 state: permission denied

[Mathieu Tarral <mathieu.tarral@xxxxxxxxxxxxxx>]

Hi,

I'm facing a problem with the distro packaged Xen on Fedora 30 cloud edition.

I'm working with this image in a virtual machine, using Vagrant:
config.vm.box = "fedora/30-cloud-base"

If I fully-upgrade the VM (sudo dnf upgrade), install Xen, and reboot, Xen will 
not be working.
The xl toolstack will hang to list VMs.

Looking into the details, the xenstored.service failed to start, with the 
following error:

[vagrant@localhost ~]$ sudo systemctl status xenstored.service
● xenstored.service - The Xen xenstore
   Loaded: loaded (/usr/lib/systemd/system/xenstored.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: protocol) since Sun 2019-05-26 22:19:18 UTC; 2min 
42s ago
  Process: 514 ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities 
(code=exited, status=0/SUCCESS)
  Process: 518 ExecStart=/etc/xen/scripts/launch-xenstore (code=exited, 
status=0/SUCCESS)
 Main PID: 518 (code=exited, status=0/SUCCESS)

May 26 22:19:21 localhost.localdomain launch-xenstore[518]: Starting 
/usr/sbin/xenstored...
May 26 22:19:21 localhost.localdomain launch-xenstore[518]: FATAL: Failed to 
initialize dom0 state: Permission denied
May 26 22:19:18 localhost.localdomain systemd[1]: Starting The Xen xenstore...
May 26 22:19:18 localhost.localdomain systemd[1]: xenstored.service: Failed 
with result 'protocol'.
May 26 22:19:18 localhost.localdomain systemd[1]: Failed to start The Xen 
xenstore.

What is this fail with result "protocol" ??

$ sudo xl info
[vagrant@localhost ~]$ sudo xl info
host                   : localhost.localdomain
release                : 5.0.17-300.fc30.x86_64
version                : #1 SMP Mon May 20 15:36:26 UTC 2019
machine                : x86_64
nr_cpus                : 2
max_cpu_id             : 1
nr_nodes               : 1
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 2208.083
hw_caps                : 
0f8bfbff:f7fa3223:2c100800:00000121:0000000f:009c47ab:00000004:00000000
virt_caps              : hvm
total_memory           : 2047
free_memory            : 126
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 11
xen_extra              : .1
xen_version            : 4.11.1
...

Of course I reported the bug to Fedora, but in the end, they told me to check 
with the Xen community,
therefore this email.

For reference, the original bug report on Fedora bugzilla is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1701783

Thanks,
Mathieu Tarral

Sent with ProtonMail Secure Email.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel