[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] problem with running xen


  • To: xen-devel <Xen-devel@xxxxxxxxxxxxx>
  • From: Aastha Mehta <aasthakm@xxxxxxxxx>
  • Date: Thu, 29 Aug 2013 22:36:36 +0200
  • Delivery-date: Thu, 29 Aug 2013 20:37:35 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

A gentle reminder on this, in case it got missed.
Here is some more information. When I run
systemctl status xencommons.service - it shows that xencommons is up and running.
Similar query for xend.service shows that it is in failed state. But I am able to run systemctl start xend.service and then the status shows as running.

However, xendomains.service is in exited state and does not restart. Also, xenconsoled and xenstored are missing in /etc/init.d.

Please let me know if I should provide any other information.

Thanks,
Aastha.


On 28 August 2013 16:23, Aastha Mehta <aasthakm@xxxxxxxxx> wrote:
Hello,

I have openSUSE 12.1 with kernel 3.10.9-1.29, which I have configured for Dom0 as well as DomU installation. And I have built the latest Xen code from the git master branch. However, I am not able to start xencommons and therefore xend. This is what I see in the dmesg after booting the hypervisor -

[    4.938634] systemd[1]: systemd 37 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; suse)
...
[    6.358927] systemd[1]: [/etc/init.d/xencommons:10] Failed to add LSB Provides name xenstored.service, ignoring: File exists
[    6.358944] systemd[1]: [/etc/init.d/xencommons:10] Failed to add LSB Provides name xenconsoled.service, ignoring: File exists
[    6.717809] systemd-readahead-replay[337]: Bumped block_nr parameter of 8:0 to 16384. This is a temporary hack and should be removed one day.
[   13.447647] systemd-fsck[733]: /dev/sda7: clean, 280149/6725632 files, 4826217/26896996 blocks
[   16.645864] systemd[1]: xend.service: control process exited, code=exited status=1
[   16.646564] systemd[1]: Unit xend.service entered failed state.

Also, when trying to start xencommons manually -
# /etc/init.d/xencommons start
Starting xenconsoled...
Starting QEMU as disk backend for dom0
Could not acquire pidfile: Inappropriate ioctl for device

What could the problem be? Please let me know if there is any other information needed.

Thanks,
Aastha.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.