Created attachment 1557871 [details] sudo xl list hangs I'm running Fedora 29 using the Vagrant image "fedora/29-cloud-base" If i start the VM and install the Xen package and reboots, Xen works. However, if i decide to fully upgrade Fedora, and then install Xen, the VM will, but the xl toolstack will hang for no reasons. Version-Release number of selected component (if applicable): 4.11.1-4.fc29 How reproducible: always Steps to Reproduce: 1. use "fedora/29-cloud-base" 2. fully upgrade the image 3. install Xen 4. reboot 5. sudo xl list 6. hangs You can find the vagrantfiles and playbook here to reproduce the bug: https://github.com/Wenzel/vagrant-xen-pyvmidbg/tree/master/fedora Thanks !
Created attachment 1557883 [details] xl list hangs ssh into the vm displaying Xen version displaying package info running xl list to see it hang
Could you get more information on the status of xen? Try running systemctl | grep xen ps -ef | grep xen ls -al /proc/xen ls -al /dev/xen mount | grep xen
I provided the information you asked for in a new attachment.
Created attachment 1558398 [details] Information about Xen environment Informations asked by Michael Young: https://bugzilla.redhat.com/show_bug.cgi?id=1702495#c2
It looks like the xenstored service failed to initialize: [vagrant@localhost ~]$ sudo systemctl status xenstored ● xenstored.service - The Xen xenstore Loaded: loaded (/usr/lib/systemd/system/xenstored.service; enabled; vendor preset: enabled) Active: failed (Result: protocol) since Wed 2019-04-24 21:21:24 UTC; 4min 35s ago Process: 527 ExecStart=/etc/xen/scripts/launch-xenstore (code=exited, status=0/SUCCESS) Process: 512 ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities (code=exited, status=0/SUCCESS) Main PID: 527 (code=exited, status=0/SUCCESS) Apr 24 21:21:24 localhost.localdomain systemd[1]: Starting The Xen xenstore... Apr 24 21:21:24 localhost.localdomain xenstored[536]: Checking store ... Apr 24 21:21:24 localhost.localdomain launch-xenstore[527]: Starting /usr/sbin/xenstored... Apr 24 21:21:24 localhost.localdomain xenstored[536]: Checking store complete. Apr 24 21:21:24 localhost.localdomain launch-xenstore[527]: FATAL: Failed to initialize dom0 state: Permission denied Apr 24 21:21:24 localhost.localdomain systemd[1]: xenstored.service: Failed with result 'protocol'. Apr 24 21:21:24 localhost.localdomain systemd[1]: Failed to start The Xen xenstore.
Hi, did you had the time to investigate the bug ? do you need more information from my side ? it's easy to reproduce though. Thanks.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still a problem with Fedora 32, see the following... # systemctl status xenstored ● xenstored.service - The Xen xenstore Loaded: loaded (/usr/lib/systemd/system/xenstored.service; enabled; vendor preset: enabled) Active: failed (Result: protocol) since Mon 2020-10-05 21:49:57 AEDT; 10h ago Process: 1106 ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities (code=exited, status=0/SUCCESS) Process: 1107 ExecStart=/etc/xen/scripts/launch-xenstore (code=exited, status=0/SUCCESS) Main PID: 1107 (code=exited, status=0/SUCCESS) CPU: 10ms Oct 05 21:49:57 host2.crowie.net systemd[1]: Starting The Xen xenstore... Oct 05 21:49:57 host2.crowie.net systemd[1]: xenstored.service: Failed with result 'protocol'. Oct 05 21:49:57 host2.crowie.net systemd[1]: Failed to start The Xen xenstore.
I'm also hitting this on Fedora Workstation 35. Would it be possible to open this again? Or has someone found a solution?
I was able to get xenstored to start by disabling SELinux. Is there a way to start xenstored without doing that?
Instead of disabling selinux, you can put it in permissive mode, and use that to build a custom selinux module using audit2allow
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days