https://bugzilla.novell.com/show_bug.cgi?id=841507 https://bugzilla.novell.com/show_bug.cgi?id=841507#c1 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |dmueller@suse.com --- Comment #1 from James Fehlig 2013-10-04 14:59:24 UTC --- libvirtd service file contains Wants=xencommons.service After=xencommons.service Is the message an instance of the generic message indicating a wanted service is not available? I see the same on a 13.1 beta KVM host that does not contain xen-tools, which provides xencommons.service. I don't see anything in systemd.unit(5) to control verboseness of messages related to missing 'Wants'. Are you hinting at some obvious improvement to the service files that I'm missing? :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=841507 https://bugzilla.novell.com/show_bug.cgi?id=841507#c3 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from James Fehlig 2013-10-07 15:07:31 UTC --- (In reply to comment #2)

Are you saying that this is "normal" and can be ignored?

I think so. I started looking at ways to only 'want' xencommons when booting on a Xen dom0, but reminded myself that systemd already provides this functionality generically with 'Wants' :). Noticed that default log level of the system instance of systemd is 'info', which is the level of message in #0. Changing 'LogLevel=warning' in /etc/systemd/system.conf squelches the message. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.