On Wed, 2013-02-13 at 12:50 +0100, Dario Faggioli wrote:
> That being said, what do you think about the xend issues I was also
> talking about in the original mail (which are more or less the same that
> were already here https://bugzilla.redhat.com/show_bug.cgi?id=893699) ? 
> 
> I'm talking about steps 18 to 32 there, where I say that I'm still not
> able to get xend starting properly and automatically ? I'd really prefer
> libxl to work and xend to "die", but until we're not there, I think we
> should have at least one which is working! :-O
> 
Regarding this, I probably forgot to mention that, other than running
xend manually, I'm also trying to enable and start it properly:

xend.service - Xend - interface between hypervisor and some applications
          Loaded: loaded (/usr/lib/systemd/system/xend.service; enabled)
          Active: failed (Result: exit-code) since Wed 2013-02-13 14:26:23 CET; 
3min 37s ago
         Process: 1053 ExecStart=/usr/sbin/xend (code=exited, status=1/FAILURE)
         Process: 983 ExecStartPre=/bin/grep -q control_d 
/proc/xen/capabilities (code=exited, status=0/SUCCESS)

Feb 13 14:26:21 localhost.localdomain systemd[1]: Starting Xend - interface 
between hypervisor and some applications...
Feb 13 14:26:23 localhost.localdomain systemd[1]: xend.service: control process 
exited, code=exited status=1
Feb 13 14:26:23 localhost.localdomain systemd[1]: Failed to start Xend - 
interface between hypervisor and some applications.
Feb 13 14:26:23 localhost.localdomain systemd[1]: Unit xend.service entered 
failed state

And in journalctl, I see a bunch of:

Feb 13 14:26:11 localhost.localdomain systemd-udevd[653]: failed to execute 
'/usr/lib/udev/socket:/org/xen/xend/udev_event' 
'socket:/org/xen/xend/udev_event': No such file or directory
Feb 13 14:26:11 localhost.localdomain systemd-udevd[654]: failed to execute 
'/usr/lib/udev/socket:/org/xen/xend/udev_event' 
'socket:/org/xen/xend/udev_event': No such file or directory
Feb 13 14:26:11 localhost.localdomain systemd-udevd[655]: failed to execute 
'/usr/lib/udev/socket:/org/xen/xend/udev_event' 
'socket:/org/xen/xend/udev_event': No such file or directory
Feb 13 14:26:11 localhost.localdomain systemd-udevd[656]: failed to execute 
'/usr/lib/udev/socket:/org/xen/xend/udev_event' 
'socket:/org/xen/xend/udev_event': No such file or directory
Feb 13 14:26:11 localhost.localdomain systemd-udevd[657]: failed to execute 
'/usr/lib/udev/socket:/org/xen/xend/udev_event' 
'socket:/org/xen/xend/udev_event': No such file or directory
Feb 13 14:26:11 localhost.localdomain systemd-udevd[658]: failed to execute 
'/usr/lib/udev/socket:/org/xen/xend/udev_event' 
'socket:/org/xen/xend/udev_event': No such file or directory
Feb 13 14:26:11 localhost.localdomain systemd-udevd[659]: failed to execute 
'/usr/lib/udev/socket:/org/xen/xend/udev_event' 
'socket:/org/xen/xend/udev_event': No such file or directory
...

What can it be? SELinux perhaps (yes, I'm using it)? I'll try disabling
and see what happens.

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

Attachment: signature.asc
Description: This is a digitally signed message part

--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Reply via email to