Re: [systemd-devel] udev-buildin-net_id.c hotplug slot with SRIOV

2015-08-21 Thread Keller, Jacob E
Forwarding this again to the full list, On Mon, 2015-08-17 at 06:25 +, Keller, Jacob E wrote: > Hi, > > > -Original Message- > > From: Andrei Borzenkov [mailto:arvidj...@gmail.com] > > Sent: Friday, August 14, 2015 10:52 PM > > To: Keller, Jacob E &

Re: [systemd-devel] udev-buildin-net_id.c hotplug slot with SRIOV

2015-08-14 Thread Keller, Jacob E
On Fri, 2015-08-14 at 06:29 +0300, Andrei Borzenkov wrote: > > On 14.08.2015 02:39, Keller, Jacob E wrote: > > Hello, > > > > I discussed this a while ago, but I have found that the hotplug > > slot > > names for ethernet devices gets confused when SRIOV is

[systemd-devel] udev-buildin-net_id.c hotplug slot with SRIOV

2015-08-13 Thread Keller, Jacob E
Hello, I discussed this a while ago, but I have found that the hotplug slot names for ethernet devices gets confused when SRIOV is used. Basically: I have a device plugged into a hotplug slot, and it gets enps for its PCI path name. For the slot, it gets ens Example: enp5s0 ens1 However,

Re: [systemd-devel] persistent network device names

2015-07-28 Thread Keller, Jacob E
On Tue, 2015-07-28 at 06:22 +0300, Andrei Borzenkov wrote: > В Mon, 27 Jul 2015 19:05:37 + > "Keller, Jacob E" пишет: > > > On Mon, 2015-07-27 at 21:53 +0300, Andrei Borzenkov wrote: > > > В Mon, 27 Jul 2015 18:29:57 + > > > "Keller, Jacob

Re: [systemd-devel] user instance of systemd while inside a container

2015-07-27 Thread Keller, Jacob E
On Mon, 2015-07-27 at 21:51 +0200, Lennart Poettering wrote: > On Tue, 14.07.15 18:34, Keller, Jacob E (jacob.e.kel...@intel.com) > wrote: > > > Hello, > > > > I created an nspawn container which is also running systemd. I > > can't > > figure

Re: [systemd-devel] persistent network device names

2015-07-27 Thread Keller, Jacob E
On Mon, 2015-07-27 at 21:53 +0300, Andrei Borzenkov wrote: > В Mon, 27 Jul 2015 18:29:57 + > "Keller, Jacob E" пишет: > > > On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote: > > > В Mon, 27 Jul 2015 17:52:59 + > > > &qu

Re: [systemd-devel] persistent network device names

2015-07-27 Thread Keller, Jacob E
On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote: > В Mon, 27 Jul 2015 17:52:59 + > "Keller, Jacob E" пишет: > > > Hello, > > > > I am working with a network device that can create virtual function > > devices. When I create a large (&

Re: [systemd-devel] persistent network device names

2015-07-27 Thread Keller, Jacob E
On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote: > В Mon, 27 Jul 2015 17:52:59 + > "Keller, Jacob E" пишет: > > > Hello, > > > > I am working with a network device that can create virtual function > > devices. When I create a large (&

Re: [systemd-devel] persistent network device names

2015-07-27 Thread Keller, Jacob E
On Mon, 2015-07-27 at 20:05 +0200, Lennart Poettering wrote: > On Mon, 27.07.15 17:52, Keller, Jacob E (jacob.e.kel...@intel.com) > wrote: > > > Hello, > > > > I am working with a network device that can create virtual function > > devices. When I create a lar

[systemd-devel] persistent network device names

2015-07-27 Thread Keller, Jacob E
Hello, I am working with a network device that can create virtual function devices. When I create a large (>8) vfs for this device I get some weird device names, If I create 64 vfs, I see something like: ens8 ens8f[1-7] ens8s[1-7] enp8s[1-7]f[1-7] If I create 64 vfs, I see something like: where

Re: [systemd-devel] Fedora 21 and systemd-nspawn

2015-07-14 Thread Keller, Jacob E
On Mon, 2015-06-15 at 21:15 -0400, Chris Morgan wrote: > On Monday, June 15, 2015, Lennart Poettering > wrote: > > On Mon, 15.06.15 13:22, Matthew Karas (mkarasc...@gmail.com) wrote: > > > > > Yes - that seems to have let me set the password. Now I can get > > > started learning about this. > >

[systemd-devel] user instance of systemd while inside a container

2015-07-14 Thread Keller, Jacob E
Hello, I created an nspawn container which is also running systemd. I can't figure out why the systemd --user instances aren't started. I'd like to manage some processes run as a specific user inside the container. Previously I was using a VM to do it this way, and I would like to be able to port

Re: [systemd-devel] machinectl login fails systemd 219

2015-04-22 Thread Keller, Jacob E
On Wed, 2015-04-22 at 22:25 +0200, Lennart Poettering wrote: > On Fri, 17.04.15 18:40, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > > > On Wed, 2015-04-15 at 00:07 +0200, Stefan Tatschner wrote: > > > On Di, 2015-04-14 at 21:56 +, Keller, Jacob E wrote: > >

Re: [systemd-devel] machinectl login fails systemd 219

2015-04-17 Thread Keller, Jacob E
On Fri, 2015-04-17 at 18:40 +, Keller, Jacob E wrote: > On Wed, 2015-04-15 at 00:07 +0200, Stefan Tatschner wrote: > > On Di, 2015-04-14 at 21:56 +0000, Keller, Jacob E wrote: > > > Failed to get machine PTY: Message did not receive a reply (timeout > > > by messag

Re: [systemd-devel] machinectl login fails systemd 219

2015-04-17 Thread Keller, Jacob E
On Wed, 2015-04-15 at 00:07 +0200, Stefan Tatschner wrote: > On Di, 2015-04-14 at 21:56 +0000, Keller, Jacob E wrote: > > Failed to get machine PTY: Message did not receive a reply (timeout > > by message bus) > > > > I get a notification on the machine itself that it

[systemd-devel] machinectl login fails systemd 219

2015-04-14 Thread Keller, Jacob E
Failed to get machine PTY: Message did not receive a reply (timeout by message bus) I get a notification on the machine itself that it started container getty and then stopped it. It worked earlier so I am not sure what changed. No one on google seems to have this specific error. Thanks for the

Re: [systemd-devel] systemd-networkd mysteriously shutting down after launch

2015-02-17 Thread Keller, Jacob E
On Sat, 2015-02-14 at 18:03 +0100, Zbigniew Jędrzejewski-Szmek wrote: > On Fri, Feb 13, 2015 at 10:49:12AM +0100, Lennart Poettering wrote: > > On Thu, 12.02.15 22:30, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > > > > > On Thu, 2015-02-12 at 20:15 +0100, Tom Gun

Re: [systemd-devel] systemd-networkd mysteriously shutting down after launch

2015-02-12 Thread Keller, Jacob E
On Thu, 2015-02-12 at 22:30 +, Keller, Jacob E wrote: > On Thu, 2015-02-12 at 20:15 +0100, Tom Gundersen wrote: > > On Thu, Feb 12, 2015 at 7:28 PM, Keller, Jacob E > > Now I'm having an interesting issue with the current git of > systemd-networkd... It works just fin

[systemd-devel] systemd-networkd mysteriously shutting down after launch

2015-02-12 Thread Keller, Jacob E
On Thu, 2015-02-12 at 20:15 +0100, Tom Gundersen wrote: > On Thu, Feb 12, 2015 at 7:28 PM, Keller, Jacob E Now I'm having an interesting issue with the current git of systemd-networkd... It works just fine on load, and I get an ip address and everything is happy. After some amount

Re: [systemd-devel] systemd-networkd not discovering all devices at bootup, and thus no network is configured

2015-02-12 Thread Keller, Jacob E
On Thu, 2015-02-12 at 18:51 +0100, Lennart Poettering wrote: > On Thu, 12.02.15 17:48, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > > > Ok, I'll try with latest Git first, and if it still fails I'll try > > reverting the patch Lennart suggested. > > git a

Re: [systemd-devel] systemd-networkd not discovering all devices at bootup, and thus no network is configured

2015-02-12 Thread Keller, Jacob E
On Thu, 2015-02-12 at 14:23 +0100, Tom Gundersen wrote: > On Thu, Feb 12, 2015 at 11:45 AM, Lennart Poettering > wrote: > > On Wed, 11.02.15 22:28, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > > > >> On Wed, 2015-02-11 at 21:46 +0100, Lennart Poettering wrote: &g

Re: [systemd-devel] systemd-networkd not discovering all devices at bootup, and thus no network is configured

2015-02-11 Thread Keller, Jacob E
On Wed, 2015-02-11 at 21:46 +0100, Lennart Poettering wrote: > On Wed, 11.02.15 20:36, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > > > > > Yes. I believe that possibly the netlink messages are occurring too > > > > early before networkd has started. Th

Re: [systemd-devel] systemd-networkd not discovering all devices at bootup, and thus no network is configured

2015-02-11 Thread Keller, Jacob E
On Wed, 2015-02-11 at 21:32 +0100, Lennart Poettering wrote: > On Wed, 11.02.15 20:22, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > > > > > I actually see the same behavior now again, so the removal of > > > > biosdevname does not solve this problem! :( >

Re: [systemd-devel] systemd-networkd not discovering all devices at bootup, and thus no network is configured

2015-02-11 Thread Keller, Jacob E
On Wed, 2015-02-11 at 19:39 +0100, Lennart Poettering wrote: > On Wed, 04.02.15 21:58, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > > > Hi again, > > > > On Tue, 2015-02-03 at 19:00 +, Keller, Jacob E wrote: > > > Hey, > > > > > >

Re: [systemd-devel] systemd-networkd not discovering all devices at bootup, and thus no network is configured

2015-02-04 Thread Keller, Jacob E
Hi again, On Tue, 2015-02-03 at 19:00 +, Keller, Jacob E wrote: > Hey, > > I've recently been using systemd-networkd to great success on a few of > my machines here. However I ran into an interesting problem on at least > 2 machines so far. I've included the output

Re: [systemd-devel] systemd-networkd not discovering all devices at bootup, and thus no network is configured

2015-02-03 Thread Keller, Jacob E
On Tue, 2015-02-03 at 19:00 +, Keller, Jacob E wrote: > Hey, > > I've recently been using systemd-networkd to great success on a few of > my machines here. However I ran into an interesting problem on at least > 2 machines so far. I've included the output of journ

[systemd-devel] systemd-networkd not discovering all devices at bootup, and thus no network is configured

2015-02-03 Thread Keller, Jacob E
Hey, I've recently been using systemd-networkd to great success on a few of my machines here. However I ran into an interesting problem on at least 2 machines so far. I've included the output of journal for systemd-networkd with Environment=SYSTEMD_LOG_LEVEL=debug as was suggested on another post.