Cannot work nictype=sriov on Ubuntu 18.04.1 LTS

Required information

Distribution: Ubuntu (server)
Distribution version: Ubuntu 18.04.1 LTS server
The output of "lxc info" or if that fails:

% lxc info
config: {}
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    (snip)
    -----END CERTIFICATE-----
  certificate_fingerprint: (snip)
  driver: lxc
  driver_version: 3.0.1
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.0-34-generic
  server: lxd
  server_pid: 1461
  server_version: 3.0.1
  storage: btrfs
  storage_version: 4.15.1
  server_clustered: false
  server_name: hibiki

SR-IOV enabled device: Intel X520-DA2 (82599ES)

Issue description
I tried to add SR-IOV device to running container by following command:

% lxc config device add container eth1 nic nictype=sriov parent=enp4s0f0

At the first time, it returns following error:

% lxc config device add container eth1 nic nictype=sriov parent=enp4s0f0
Error: open /sys/class/net/enp4s0f0/device/virtfn1/net: no such file or directory

But the directory /sys/class/net/enp4s0f0/device/virtfn1/net has created by LXD at this time.
And after the second time, it returns:

% lxc config device add container eth1 nic nictype=sriov parent=enp4s0f0
Error: Failed to set the MAC address: Failed to run: ip link set dev eth0 address 00:16:3e:fd:07:49: RTNETLINK answers: Operation not permitted

It seems that LXD tries to rename host machine's SR-IOV virtual function device name eth0 to container's device name eth1.
But I'm not sure why LXD also tries to set the MAC address to virtual function.
Steps to reproduce

My SR-IOV device information:

% ip a s dev enp4s0f0
3: enp4s0f0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:21:bc:04:a2 brd ff:ff:ff:ff:ff:ff

% sudo ethtool enp4s0f0
Settings for enp4s0f0:
        Supported ports: [ FIBRE ]
        Supported link modes:   10000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  10000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Direct Attach Copper
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no

% lspci | grep 82599ES
04:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
04:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)

Create a container

% lxc launch ubuntu:18.04 mycontainer
Creating mycontainer
Starting mycontainer

% lxc config show mycontainer --expanded
architecture: x86_64
config:
  image.architecture: amd64
  image.description: ubuntu 18.04 LTS amd64 (release) (20180911)
  image.label: release
  image.os: ubuntu
  image.release: bionic
  image.serial: "20180911"
  image.version: "18.04"
  volatile.base_image: c395a7105278712478ec1dbfaab1865593fc11292f99afe01d5b94f1c34a9a3a
  volatile.eth0.hwaddr: 00:16:3e:3d:a4:a8
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.power: RUNNING
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""

Add nictype=sriov device as "eth1" to running container.

% lxc config device add mycontainer eth1 nic nictype=sriov parent=enp4s0f0
Error: open /sys/class/net/enp4s0f0/device/virtfn1/net: no such file or directory

(But the directory /sys/class/net/enp4s0f0/device/virtfn1/net has created by LXD at this time)

% ls -ld /sys/class/net/enp4s0f0/device/virtfn1/net
drwxr-xr-x 3 root root 0 Sep 17 18:25 /sys/class/net/enp4s0f0/device/virtfn1/net
% ls -l /sys/class/net/enp4s0f0/device/virtfn1/net
total 0
drwxr-xr-x 5 root root 0 Sep 17 18:25 eth1

(Virtual functions are created)

% ip a
(snip)
9: eth0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 92:1a:2a:af:e1:73 brd ff:ff:ff:ff:ff:ff
10: eth1:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ee:b9:b0:57:a3:0e brd ff:ff:ff:ff:ff:ff
(snip)
70: eth61:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ce:3b:f2:da:9c:cc brd ff:ff:ff:ff:ff:ff
71: eth62:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 16:4e:33:fa:19:2b brd ff:ff:ff:ff:ff:ff

(Now mycontainer has properties volatile.eth1.hwaddr and volatile.eth1.name)

% lxc config show mycontainer --expanded
architecture: x86_64
config:
  image.architecture: amd64
  image.description: ubuntu 18.04 LTS amd64 (release) (20180911)
  image.label: release
  image.os: ubuntu
  image.release: bionic
  image.serial: "20180911"
  image.version: "18.04"
  volatile.base_image: c395a7105278712478ec1dbfaab1865593fc11292f99afe01d5b94f1c34a9a3a
  volatile.eth0.hwaddr: 00:16:3e:3d:a4:a8
  volatile.eth1.hwaddr: 00:16:3e:fd:07:49
  volatile.eth1.name: eth1
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.power: RUNNING
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""

Add nictype=sriov device to container again.

% lxc config device add mycontainer eth1 nic nictype=sriov parent=enp4s0f0
Error: Failed to set the MAC address: Failed to run: ip link set dev eth0 address 00:16:3e:fd:07:49: RTNETLINK answers: Operation not permitted

Stop container, and add sriov device, and start. It seems that LXD tries to rename network device "veth9VDXG7" to "eth0".

% lxc stop mycontainer

% lxc config device add mycontainer eth1 nic nictype=sriov parent=enp4s0f0
Device eth1 added to mycontainer

% lxc config show mycontainer --expanded
architecture: x86_64
config:
  image.architecture: amd64
  image.description: ubuntu 18.04 LTS amd64 (release) (20180911)
  image.label: release
  image.os: ubuntu
  image.release: bionic
  image.serial: "20180911"
  image.version: "18.04"
  volatile.base_image: c395a7105278712478ec1dbfaab1865593fc11292f99afe01d5b94f1c34a9a3a
  volatile.eth0.hwaddr: 00:16:3e:3d:a4:a8
  volatile.eth1.hwaddr: 00:16:3e:fd:07:49
  volatile.eth1.name: eth1
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.power: STOPPED
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth1:
    nictype: sriov
    parent: enp4s0f0
    type: nic
  root:
    path: /
    pool: default
    type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""

% lxc start mycontainer
Error: Failed to run: /usr/lib/lxd/lxd forkstart mycontainer /var/lib/lxd/containers /var/log/lxd/mycontainer/lxc.conf:
Try `lxc info --show-log mycontainer` for more info

% lxc info --show-log mycontainer
Name: mycontainer
Remote: unix://
Architecture: x86_64
Created: 2018/09/17 09:21 UTC
Status: Stopped
Type: persistent
Profiles: default

Log:

lxc mycontainer<PHONE_NUMBER>3504.360 ERROR    lxc_network - network.c:lxc_setup_netdev_in_child_namespaces:2875 - Failed to rename network device "veth9VDXG7" to "eth0": File exists
lxc mycontainer<PHONE_NUMBER>3504.360 ERROR    lxc_network - network.c:lxc_setup_network_in_child_namespaces:3034 - failed to setup netdev
lxc mycontainer<PHONE_NUMBER>3504.360 ERROR    lxc_conf - conf.c:lxc_setup:3389 - Failed to setup network
lxc mycontainer<PHONE_NUMBER>3504.360 ERROR    lxc_start - start.c:do_start:1219 - Failed to setup container "mycontainer"
lxc mycontainer<PHONE_NUMBER>3504.360 ERROR    lxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 5)
lxc mycontainer<PHONE_NUMBER>3504.428 WARN     lxc_network - network.c:lxc_delete_network_priv:2556 - Failed to rename interface with index 9 from "eth1" to its initial name "eth0"
lxc mycontainer<PHONE_NUMBER>3504.428 ERROR    lxc_start - start.c:__lxc_start:1887 - Failed to spawn container "mycontainer"
lxc mycontainer<PHONE_NUMBER>3504.428 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:834 - Received container state "ABORTING" instead of "RUNNING"
lxc<PHONE_NUMBER>3504.438 WARN     lxc_commands - commands.c:lxc_cmd_rsp_recv:130 - Connection reset by peer - Failed to receive response for command "get_state"

Switch the profile from default to dummy profile nonic which it has no network device. It seems that failed to setup hw address for network device "eth1".

% lxc profile list
+---------+---------+
|  NAME   | USED BY |
+---------+---------+
| default | 1       |
+---------+---------+
| nonic   | 0       |
+---------+---------+

% lxc profile show nonic
config: {}
description: LXD profile without nic device
devices:
  root:
    path: /
    pool: default
    type: disk
name: nonic
used_by: []

% lxc config edit mycontainer
% lxc config show mycontainer --expanded
architecture: x86_64
config:
  image.architecture: amd64
  image.description: ubuntu 18.04 LTS amd64 (release) (20180911)
  image.label: release
  image.os: ubuntu
  image.release: bionic
  image.serial: "20180911"
  image.version: "18.04"
  volatile.base_image: c395a7105278712478ec1dbfaab1865593fc11292f99afe01d5b94f1c34a9a3a
  volatile.eth1.hwaddr: 00:16:3e:fd:07:49
  volatile.eth1.name: eth1
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.power: STOPPED
devices:
  eth1:
    nictype: sriov
    parent: enp4s0f0
    type: nic
  root:
    path: /
    pool: default
    type: disk
ephemeral: false
profiles:
- nonic
stateful: false
description: ""

% lxc start mycontainer
Error: Failed to run: /usr/lib/lxd/lxd forkstart mycontainer /var/lib/lxd/containers /var/log/lxd/mycontainer/lxc.conf:
Try `lxc info --show-log mycontainer` for more info

% lxc info --show-log mycontainer
Name: mycontainer
Remote: unix://
Architecture: x86_64
Created: 2018/09/17 09:21 UTC
Status: Stopped
Type: persistent
Profiles: nonic

Log:

lxc mycontainer<PHONE_NUMBER>4353.196 ERROR    lxc_network - network.c:setup_hw_addr:2758 - Failed to perform ioctl: Operation not permitted
lxc mycontainer<PHONE_NUMBER>4353.196 ERROR    lxc_network - network.c:lxc_setup_netdev_in_child_namespaces:2899 - Failed to setup hw address for network device "eth1"
lxc mycontainer<PHONE_NUMBER>4353.196 ERROR    lxc_network - network.c:lxc_setup_network_in_child_namespaces:3034 - failed to setup netdev
lxc mycontainer<PHONE_NUMBER>4353.196 ERROR    lxc_conf - conf.c:lxc_setup:3389 - Failed to setup network
lxc mycontainer<PHONE_NUMBER>4353.196 ERROR    lxc_start - start.c:do_start:1219 - Failed to setup container "mycontainer"
lxc mycontainer<PHONE_NUMBER>4353.196 ERROR    lxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 5)
lxc mycontainer<PHONE_NUMBER>4353.196 WARN     lxc_network - network.c:lxc_delete_network_priv:2556 - Failed to rename interface with index 9 from "eth1" to its initial name "eth0"
lxc mycontainer<PHONE_NUMBER>4353.196 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:834 - Received container state "ABORTING" instead of "RUNNING"
lxc mycontainer<PHONE_NUMBER>4353.196 ERROR    lxc_start - start.c:__lxc_start:1887 - Failed to spawn container "mycontainer"
lxc<PHONE_NUMBER>4353.206 WARN     lxc_commands - commands.c:lxc_cmd_rsp_recv:130 - Connection reset by peer - Failed to receive response for command "get_state"

Information to attach

[ ] Any relevant kernel output (dmesg)

[Mon Sep 17 18:21:06 2018] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[Mon Sep 17 18:21:07 2018] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[Mon Sep 17 18:21:07 2018] ip6_tables: (C) 2000-2006 Netfilter Core Team
[Mon Sep 17 18:21:15 2018] BTRFS: device label default devid 1 transid 272 /dev/loop0
[Mon Sep 17 18:21:15 2018] BTRFS info (device loop0): disk space caching is enabled
[Mon Sep 17 18:21:15 2018] BTRFS info (device loop0): has skinny extents
[Mon Sep 17 18:21:18 2018] Ebtables v2.0 registered
[Mon Sep 17 18:21:19 2018] lxdbr0: port 1(veth7OW79F) entered blocking state
[Mon Sep 17 18:21:19 2018] lxdbr0: port 1(veth7OW79F) entered disabled state
[Mon Sep 17 18:21:19 2018] device veth7OW79F entered promiscuous mode
[Mon Sep 17 18:21:19 2018] IPv6: ADDRCONF(NETDEV_UP): veth7OW79F: link is not ready
[Mon Sep 17 18:21:19 2018] lxdbr0: port 1(veth7OW79F) entered blocking state
[Mon Sep 17 18:21:19 2018] lxdbr0: port 1(veth7OW79F) entered forwarding state
[Mon Sep 17 18:21:19 2018] lxdbr0: port 1(veth7OW79F) entered disabled state
[Mon Sep 17 18:21:19 2018] eth0: renamed from veth5TA3UP
[Mon Sep 17 18:21:19 2018] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[Mon Sep 17 18:21:19 2018] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[Mon Sep 17 18:21:19 2018] IPv6: ADDRCONF(NETDEV_CHANGE): veth7OW79F: link becomes ready
[Mon Sep 17 18:21:19 2018] lxdbr0: port 1(veth7OW79F) entered blocking state
[Mon Sep 17 18:21:19 2018] lxdbr0: port 1(veth7OW79F) entered forwarding state
[Mon Sep 17 18:25:53 2018] ixgbe 0000:04:00.0 enp4s0f0: SR-IOV enabled with 63 VFs
[Mon Sep 17 18:25:53 2018] ixgbe 0000:04:00.0: Multiqueue Enabled: Rx Queue count = 2, Tx Queue count = 2 XDP Queue count = 0
[Mon Sep 17 18:25:53 2018] pci 0000:04:10.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:10.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:10.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:10.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:11.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:11.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:11.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:11.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:12.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:12.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:12.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:12.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:13.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:13.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:13.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:13.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:14.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:14.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:14.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:14.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:15.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:15.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:15.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:15.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:16.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:16.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:16.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:16.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:17.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:17.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:17.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:17.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:18.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:18.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:18.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:18.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:19.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:19.2: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:19.4: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:19.6: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] pci 0000:04:1a.0: [8086:10ed] type 00 class 0x020000
[Mon Sep 17 18:25:53 2018] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 4.1.0-k
[Mon Sep 17 18:25:53 2018] ixgbevf: Copyright (c) 2009 - 2015 Intel Corporation.
  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.0: 92:1a:2a:af:e1:73
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.2: ee:b9:b0:57:a3:0e
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.4: a6:7d:ef:d9:f5:08
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.6: 2a:57:ad:d4:2a:d2
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:10.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.0: ca:37:14:5a:72:58
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.2: 52:b9:18:d3:0e:85
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.4: 7a:6a:71:69:55:3b
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.6: b6:96:97:50:1d:af
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:11.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.0: b6:b5:ea:b6:48:d8
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.2: 02:3f:da:87:7b:56
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.4: 36:41:fe:2e:5a:f8
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.6: c2:bc:a1:47:0a:66
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:12.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.0: 5a:1a:19:f2:9f:87
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.2: 62:31:93:c8:4b:17
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.4: 8a:55:63:38:f9:6c
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.6: 92:b1:2e:51:af:34
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:13.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.0: 66:88:92:97:a5:4d
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.2: de:89:88:96:13:c1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.4: a6:2f:d7:8f:86:94
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.6: ee:c9:62:e3:ae:90
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:14.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.0: 52:d6:e3:94:b6:a8
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.2: 9e:be:49:68:e6:c9
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.4: 76:50:fe:43:9b:13
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.6: 0e:b6:c2:f3:fb:19
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:15.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.0: e2:c3:9a:55:f4:fa
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.2: 96:69:cf:69:79:93
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.4: 36:c6:2e:62:aa:49
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.6: ae:c4:38:4e:bf:03
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:16.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.0: 82:82:f3:a9:11:32
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.2: 32:d5:a5:a9:5a:14
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.4: 42:5a:0d:7e:fc:9e
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.6: 5a:86:2e:79:e1:67
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:17.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.0: 92:96:11:d2:9e:f8
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.2: fa:5d:d9:e9:aa:78
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.4: ea:9e:a3:ef:2e:02
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.6: 2a:96:29:b4:09:30
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:18.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.0: fe:dd:87:4a:25:4a
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.2: 8a:03:e0:91:44:3d
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.4: ea:d9:bd:aa:35:11
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.6: d2:e1:f5:6d:fe:af
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:19.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.0: 5e:e8:81:a3:d6:77
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.2: ae:3d:0f:c3:fe:70
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.4: 3e:af:e6:53:4d:88
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.6: da:71:46:3b:c8:5f
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1a.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.0: a2:99:e7:b9:da:68
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.2: f2:94:c9:04:ca:07
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.4: 86:31:e4:0f:24:c3
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.6: 0a:c9:e9:13:3a:51
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1b.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.0: 76:8b:20:e0:b5:dc
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.2: ce:7b:d2:b8:be:ba
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.4: 6a:b6:f0:f3:d3:66
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.6: 6e:06:3a:71:86:85
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1c.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.0: 96:7f:92:0e:cc:b7
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.2: ea:b4:d2:0d:81:56
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.4: 72:51:33:3e:56:b6
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.6: e2:29:00:10:31:6d
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1d.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.0: c2:0e:a6:c4:54:6e
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.2: 4e:bf:04:13:31:8b
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.4: 06:36:8d:d4:05:ee
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.6: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.6: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.6: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.6: 76:bd:4f:ca:98:1f
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.6: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1e.6: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.0: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.0: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.0: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.0: 76:d4:46:0a:c3:a2
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.0: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.0: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.2: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.2: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.2: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.2: ce:3b:f2:da:9c:cc
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.2: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.2: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.4: enabling device (0000 -> 0002)
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.4: PF still in reset state.  Is the PF interface up?
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.4: Assigning random MAC address
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.4: 16:4e:33:fa:19:2b
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.4: MAC: 1
[Mon Sep 17 18:25:53 2018] ixgbevf 0000:04:1f.4: Intel(R) 82599 Virtual Function
[Mon Sep 17 18:33:40 2018] lxdbr0: port 1(veth7OW79F) entered disabled state
[Mon Sep 17 18:33:40 2018] device veth7OW79F left promiscuous mode
[Mon Sep 17 18:33:40 2018] lxdbr0: port 1(veth7OW79F) entered disabled state
[Mon Sep 17 18:35:03 2018] lxdbr0: port 1(vethXRRGGB) entered blocking state
[Mon Sep 17 18:35:03 2018] lxdbr0: port 1(vethXRRGGB) entered disabled state
[Mon Sep 17 18:35:03 2018] device vethXRRGGB entered promiscuous mode
[Mon Sep 17 18:35:03 2018] IPv6: ADDRCONF(NETDEV_UP): vethXRRGGB: link is not ready
[Mon Sep 17 18:35:04 2018] lxdbr0: port 1(vethXRRGGB) entered disabled state
[Mon Sep 17 18:35:04 2018] device vethXRRGGB left promiscuous mode
[Mon Sep 17 18:35:04 2018] lxdbr0: port 1(vethXRRGGB) entered disabled state
[Mon Sep 17 18:43:52 2018] ixgbevf 0000:04:10.0 eth1: renamed from eth0

[ ] Container log (lxc info NAME --show-log)
Pelase see 'Steps to reproduce'

[ ] Container configuration (lxc config show NAME --expanded)
Pelase see 'Steps to reproduce'

[ ] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)

lvl=info msg="LXD 3.0.1 is starting in normal mode" path=/var/lib/lxd t=2018-09-17T18:21:06+0900
lvl=info msg="Kernel uid/gid map:" t=2018-09-17T18:21:06+0900
lvl=info msg=" - u 0 0<PHONE_NUMBER>" t=2018-09-17T18:21:06+0900
lvl=info msg=" - g 0 0<PHONE_NUMBER>" t=2018-09-17T18:21:06+0900
lvl=info msg="Configured LXD uid/gid map:" t=2018-09-17T18:21:06+0900
lvl=info msg=" - u 0<PHONE_NUMBER>6" t=2018-09-17T18:21:06+0900
lvl=info msg=" - g 0<PHONE_NUMBER>6" t=2018-09-17T18:21:06+0900
lvl=warn msg="AppArmor support has been disabled because of lack of kernel support" t=2018-09-17T18:21:06+0900
lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2018-09-17T18:21:06+0900
lvl=info msg="Initializing local database" t=2018-09-17T18:21:06+0900
lvl=info msg="Initializing database gateway" t=2018-09-17T18:21:06+0900
address= id=1 lvl=info msg="Start database node" t=2018-09-17T18:21:06+0900
lvl=info msg="Raft: Restored from snapshot 1-507-1537175388113" t=2018-09-17T18:21:06+0900
lvl=info msg="Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]" t=2018-09-17T18:21:06+0900
lvl=info msg="Raft: Node at 0 [Leader] entering Leader state" t=2018-09-17T18:21:06+0900
lvl=info msg="LXD is socket activated" t=2018-09-17T18:21:06+0900
lvl=info msg="Starting /dev/lxd handler:" t=2018-09-17T18:21:06+0900
lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock t=2018-09-17T18:21:06+0900
lvl=info msg="REST API daemon:" t=2018-09-17T18:21:06+0900
lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket t=2018-09-17T18:21:06+0900
lvl=info msg="Initializing global database" t=2018-09-17T18:21:06+0900
lvl=info msg="Initializing storage pools" t=2018-09-17T18:21:07+0900
lvl=info msg="Initializing networks" t=2018-09-17T18:21:07+0900
lvl=info msg="Loading configuration" t=2018-09-17T18:21:08+0900
lvl=info msg="Pruning expired images" t=2018-09-17T18:21:08+0900
lvl=info msg="Done pruning expired images" t=2018-09-17T18:21:08+0900
lvl=info msg="Expiring log files" t=2018-09-17T18:21:08+0900
lvl=info msg="Updating instance types" t=2018-09-17T18:21:08+0900
lvl=info msg="Updating images" t=2018-09-17T18:21:08+0900
lvl=info msg="Done expiring log files" t=2018-09-17T18:21:08+0900
lvl=info msg="Done updating images" t=2018-09-17T18:21:13+0900
ephemeral=false lvl=info msg="Creating container" name=mycontainer t=2018-09-17T18:21:15+0900
ephemeral=false lvl=info msg="Created container" name=mycontainer t=2018-09-17T18:21:15+0900
lvl=info msg="Done updating instance types" t=2018-09-17T18:21:17+0900
action=start created=2018-09-17T18:21:15+0900 ephemeral=false lvl=info msg="Starting container" name=mycontainer stateful=false t=2018-09-17T18:21:19+0900 used=1970-01-01T09:00:00+0900
action=start created=2018-09-17T18:21:15+0900 ephemeral=false lvl=info msg="Started container" name=mycontainer stateful=false t=2018-09-17T18:21:19+0900 used=1970-01-01T09:00:00+0900
action=shutdown created=2018-09-17T18:21:15+0900 ephemeral=false lvl=info msg="Shutting down container" name=mycontainer t=2018-09-17T18:33:40+0900 timeout=-1s used=2018-09-17T18:21:19+0900
action=shutdown created=2018-09-17T18:21:15+0900 ephemeral=false lvl=info msg="Shut down container" name=mycontainer t=2018-09-17T18:33:41+0900 timeout=-1s used=2018-09-17T18:21:19+0900
action=start created=2018-09-17T18:21:15+0900 ephemeral=false lvl=info msg="Starting container" name=mycontainer stateful=false t=2018-09-17T18:35:04+0900 used=2018-09-17T18:21:19+0900
action=start created=2018-09-17T18:21:15+0900 ephemeral=false lvl=eror msg="Failed starting container" name=mycontainer stateful=false t=2018-09-17T18:35:04+0900 used=2018-09-17T18:21:19+0900
action=stop created=2018-09-17T18:21:15+0900 ephemeral=false lvl=info msg="Container initiated stop" name=mycontainer stateful=false t=2018-09-17T18:35:04+0900 used=2018-09-17T18:35:04+0900
action=start created=2018-09-17T18:21:15+0900 ephemeral=false lvl=info msg="Starting container" name=mycontainer stateful=false t=2018-09-17T18:43:52+0900 used=2018-09-17T18:35:04+0900
action=start created=2018-09-17T18:21:15+0900 ephemeral=false lvl=eror msg="Failed starting container" name=mycontainer stateful=false t=2018-09-17T18:43:53+0900 used=2018-09-17T18:35:04+0900
action=stop created=2018-09-17T18:21:15+0900 ephemeral=false lvl=info msg="Container initiated stop" name=mycontainer stateful=false t=2018-09-17T18:43:53+0900 used=2018-09-17T18:43:52+0900

[ ] Output of the client with --debug

% lxc start mycontainer --debug
DBUG[09-17|18:57:22] Connecting to a local LXD over a Unix socket
DBUG[09-17|18:57:22] Sending request to LXD                   etag= method=GET url=http://unix.socket/1.0
DBUG[09-17|18:57:22] Got response struct from LXD
DBUG[09-17|18:57:22]
        {
                "config": {},
                "api_extensions": [
                        "storage_zfs_remove_snapshots",
                        "container_host_shutdown_timeout",
                        "container_stop_priority",
                        "container_syscall_filtering",
                        "auth_pki",
                        "container_last_used_at",
                        "etag",
                        "patch",
                        "usb_devices",
                        "https_allowed_credentials",
                        "image_compression_algorithm",
                        "directory_manipulation",
                        "container_cpu_time",
                        "storage_zfs_use_refquota",
                        "storage_lvm_mount_options",
                        "network",
                        "profile_usedby",
                        "container_push",
                        "container_exec_recording",
                        "certificate_update",
                        "container_exec_signal_handling",
                        "gpu_devices",
                        "container_image_properties",
                        "migration_progress",
                        "id_map",
                        "network_firewall_filtering",
                        "network_routes",
                        "storage",
                        "file_delete",
                        "file_append",
                        "network_dhcp_expiry",
                        "storage_lvm_vg_rename",
                        "storage_lvm_thinpool_rename",
                        "network_vlan",
                        "image_create_aliases",
                        "container_stateless_copy",
                        "container_only_migration",
                        "storage_zfs_clone_copy",
                        "unix_device_rename",
                        "storage_lvm_use_thinpool",
                        "storage_rsync_bwlimit",
                        "network_vxlan_interface",
                        "storage_btrfs_mount_options",
                        "entity_description",
                        "image_force_refresh",
                        "storage_lvm_lv_resizing",
                        "id_map_base",
                        "file_symlinks",
                        "container_push_target",
                        "network_vlan_physical",
                        "storage_images_delete",
                        "container_edit_metadata",
                        "container_snapshot_stateful_migration",
                        "storage_driver_ceph",
                        "storage_ceph_user_name",
                        "resource_limits",
                        "storage_volatile_initial_source",
                        "storage_ceph_force_osd_reuse",
                        "storage_block_filesystem_btrfs",
                        "resources",
                        "kernel_limits",
                        "storage_api_volume_rename",
                        "macaroon_authentication",
                        "network_sriov",
                        "console",
                        "restrict_devlxd",
                        "migration_pre_copy",
                        "infiniband",
                        "maas_network",
                        "devlxd_events",
                        "proxy",
                        "network_dhcp_gateway",
                        "file_get_symlink",
                        "network_leases",
                        "unix_device_hotplug",
                        "storage_api_local_volume_handling",
                        "operation_description",
                        "clustering",
                        "event_lifecycle",
                        "storage_api_remote_volume_handling",
                        "nvidia_runtime"
                ],
                "api_status": "stable",
                "api_version": "1.0",
                "auth": "trusted",
                "public": false,
                "auth_methods": [
                        "tls"
                ],
                "environment": {
                        "addresses": [],
                        "architectures": [
                                "x86_64",
                                "i686"
                        ],
                        "certificate": (snip)",
                        "certificate_fingerprint": (snip)"
                        "driver": "lxc",
                        "driver_version": "3.0.1",
                        "kernel": "Linux",
                        "kernel_architecture": "x86_64",
                        "kernel_version": "4.15.0-34-generic",
                        "server": "lxd",
                        "server_pid": 1408,
                        "server_version": "3.0.1",
                        "storage": "btrfs",
                        "storage_version": "4.15.1",
                        "server_clustered": false,
                        "server_name": "hibiki"
                }
        }
DBUG[09-17|18:57:22] Sending request to LXD                   etag= method=GET url=http://unix.socket/1.0/containers/mycontainer
DBUG[09-17|18:57:22] Got response struct from LXD
DBUG[09-17|18:57:22]
        {
                "architecture": "x86_64",
                "config": {
                        "image.architecture": "amd64",
                        "image.description": "ubuntu 18.04 LTS amd64 (release) (20180911)",
                        "image.label": "release",
                        "image.os": "ubuntu",
                        "image.release": "bionic",
                        "image.serial": "20180911",
                        "image.version": "18.04",
                        "volatile.base_image": "c395a7105278712478ec1dbfaab1865593fc11292f99afe01d5b94f1c34a9a3a",
                        "volatile.eth1.hwaddr": "00:16:3e:fd:07:49",
                        "volatile.eth1.name": "eth1",
                        "volatile.idmap.base": "0",
                        "volatile.idmap.next": "[{\"Isuid\":true,\"Isgid\":false,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536},{\"Isuid\":false,\"Isgid\":true,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536}]",
                        "volatile.last_state.idmap": "[{\"Isuid\":true,\"Isgid\":false,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536},{\"Isuid\":false,\"Isgid\":true,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536}]",
                        "volatile.last_state.power": "STOPPED"
                },
                "devices": {
                        "eth1": {
                                "nictype": "sriov",
                                "parent": "enp4s0f0",
                                "type": "nic"
                        }
                },
                "ephemeral": false,
                "profiles": [
                        "nonic"
                ],
                "stateful": false,
                "description": "",
                "created_at": "2018-09-17T18:21:15+09:00",
                "expanded_config": {
                        "image.architecture": "amd64",
                        "image.description": "ubuntu 18.04 LTS amd64 (release) (20180911)",
                        "image.label": "release",
                        "image.os": "ubuntu",
                        "image.release": "bionic",
                        "image.serial": "20180911",
                        "image.version": "18.04",
                        "volatile.base_image": "c395a7105278712478ec1dbfaab1865593fc11292f99afe01d5b94f1c34a9a3a",
                        "volatile.eth1.hwaddr": "00:16:3e:fd:07:49",
                        "volatile.eth1.name": "eth1",
                        "volatile.idmap.base": "0",
                        "volatile.idmap.next": "[{\"Isuid\":true,\"Isgid\":false,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536},{\"Isuid\":false,\"Isgid\":true,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536}]",
                        "volatile.last_state.idmap": "[{\"Isuid\":true,\"Isgid\":false,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536},{\"Isuid\":false,\"Isgid\":true,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536}]",
                        "volatile.last_state.power": "STOPPED"
                },
                "expanded_devices": {
                        "eth1": {
                                "nictype": "sriov",
                                "parent": "enp4s0f0",
                                "type": "nic"
                        },
                        "root": {
                                "path": "/",
                                "pool": "default",
                                "type": "disk"
                        }
                },
                "name": "mycontainer",
                "status": "Stopped",
                "status_code": 102,
                "last_used_at": "2018-09-17T18:43:52+09:00",
                "location": ""
        }
DBUG[09-17|18:57:22] Connected to the websocket
DBUG[09-17|18:57:22] Sending request to LXD                   etag= method=PUT url=http://unix.socket/1.0/containers/mycontainer/state
DBUG[09-17|18:57:22]
        {
                "action": "start",
                "timeout": 0,
                "force": false,
                "stateful": false
        }
DBUG[09-17|18:57:22] Got operation from LXD
DBUG[09-17|18:57:22]
        {
                "id": "60a778d0-bac9-4520-ae45-19e5d2ff30a1",
                "class": "task",
                "description": "Starting container",
                "created_at": "2018-09-17T18:57:22.915196043+09:00",
                "updated_at": "2018-09-17T18:57:22.915196043+09:00",
                "status": "Running",
                "status_code": 103,
                "resources": {
                        "containers": [
                                "/1.0/containers/mycontainer"
                        ]
                },
                "metadata": null,
                "may_cancel": false,
                "err": ""
        }
DBUG[09-17|18:57:22] Sending request to LXD                   etag= method=GET url=http://unix.socket/1.0/operations/60a778d0-bac9-4520-ae45-19e5d2ff30a1
DBUG[09-17|18:57:22] Got response struct from LXD
DBUG[09-17|18:57:22]
        {
                "id": "60a778d0-bac9-4520-ae45-19e5d2ff30a1",
                "class": "task",
                "description": "Starting container",
                "created_at": "2018-09-17T18:57:22.915196043+09:00",
                "updated_at": "2018-09-17T18:57:22.915196043+09:00",
                "status": "Running",
                "status_code": 103,
                "resources": {
                        "containers": [
                                "/1.0/containers/mycontainer"
                        ]
                },
                "metadata": null,
                "may_cancel": false,
                "err": ""
        }
Error: Failed to run: /usr/lib/lxd/lxd forkstart mycontainer /var/lib/lxd/containers /var/log/lxd/mycontainer/lxc.conf:
Try `lxc info --show-log mycontainer` for more info

[ ] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)

% lxc monitor
metadata:
  context: {}
  level: dbug
  message: 'New event listener: 34dc6751-465d-44f3-a58d-127e0559e833'
timestamp: "2018-09-17T19:01:37.563202352+09:00"
type: logging

metadata:
  context:
    ip: '@'
    method: GET
    url: /1.0
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:43.33375673+09:00"
type: logging

metadata:
  context:
    ip: '@'
    method: GET
    url: /1.0/containers/mycontainer
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:43.336362077+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: 'New event listener: fd74f805-8347-4d8e-8be7-f599dc9a0add'
timestamp: "2018-09-17T19:01:43.34282792+09:00"
type: logging

metadata:
  context:
    ip: '@'
    method: GET
    url: /1.0/events
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:43.342735668+09:00"
type: logging

metadata:
  context:
    ip: '@'
    method: PUT
    url: /1.0/containers/mycontainer/state
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:43.344078236+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: 'New task operation: 174d2384-463e-42c5-94e6-5040e1ec7d80'
timestamp: "2018-09-17T19:01:43.398930855+09:00"
type: logging

metadata:
  class: task
  created_at: "2018-09-17T19:01:43.350178884+09:00"
  description: Starting container
  err: ""
  id: 174d2384-463e-42c5-94e6-5040e1ec7d80
  may_cancel: false
  metadata: null
  resources:
    containers:
    - /1.0/containers/mycontainer
  status: Running
  status_code: 103
  updated_at: "2018-09-17T19:01:43.350178884+09:00"
timestamp: "2018-09-17T19:01:43.39904444+09:00"
type: operation

metadata:
  context: {}
  level: dbug
  message: 'Started task operation: 174d2384-463e-42c5-94e6-5040e1ec7d80'
timestamp: "2018-09-17T19:01:43.399000369+09:00"
type: logging

metadata:
  class: task
  created_at: "2018-09-17T19:01:43.350178884+09:00"
  description: Starting container
  err: ""
  id: 174d2384-463e-42c5-94e6-5040e1ec7d80
  may_cancel: false
  metadata: null
  resources:
    containers:
    - /1.0/containers/mycontainer
  status: Pending
  status_code: 105
  updated_at: "2018-09-17T19:01:43.350178884+09:00"
timestamp: "2018-09-17T19:01:43.398962378+09:00"
type: operation

metadata:
  context:
    ip: '@'
    method: GET
    url: /1.0/operations/174d2384-463e-42c5-94e6-5040e1ec7d80
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:43.400456804+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Initializing a BTRFS driver.
timestamp: "2018-09-17T19:01:43.412834248+09:00"
type: logging

metadata:
  action: container-updated
  source: /1.0/containers/mycontainer
timestamp: "2018-09-17T19:01:43.461718781+09:00"
type: lifecycle

metadata:
  context: {}
  level: dbug
  message: Mounting BTRFS storage volume for container "mycontainer" on storage pool
    "default".
timestamp: "2018-09-17T19:01:43.462473985+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Mounting BTRFS storage pool "default".
timestamp: "2018-09-17T19:01:43.462505122+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Mounted BTRFS storage volume for container "mycontainer" on storage pool
    "default".
timestamp: "2018-09-17T19:01:43.462771857+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Mounting BTRFS storage pool "default".
timestamp: "2018-09-17T19:01:43.507641996+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Mounting BTRFS storage volume for container "mycontainer" on storage pool
    "default".
timestamp: "2018-09-17T19:01:43.507611928+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Mounted BTRFS storage volume for container "mycontainer" on storage pool
    "default".
timestamp: "2018-09-17T19:01:43.507993046+09:00"
type: logging

metadata:
  context:
    action: start
    created: 2018-09-17 18:21:15 +0900 JST
    ephemeral: "false"
    name: mycontainer
    stateful: "false"
    used: 2018-09-17 18:57:23 +0900 JST
  level: info
  message: Starting container
timestamp: "2018-09-17T19:01:43.508099952+09:00"
type: logging

metadata:
  context:
    ip: '@'
    method: GET
    url: /1.0
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:43.530738919+09:00"
type: logging

metadata:
  context:
    ip: '@'
    method: GET
    url: /internal/containers/6/onstart
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:43.533392397+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Initializing a BTRFS driver.
timestamp: "2018-09-17T19:01:43.546040756+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Mounting BTRFS storage pool "default".
timestamp: "2018-09-17T19:01:43.546118774+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Mounting BTRFS storage volume for container "mycontainer" on storage pool
    "default".
timestamp: "2018-09-17T19:01:43.546090483+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Mounted BTRFS storage volume for container "mycontainer" on storage pool
    "default".
timestamp: "2018-09-17T19:01:43.546434099+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: 'Scheduler: container mycontainer started: re-balancing'
timestamp: "2018-09-17T19:01:43.547732663+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: 'Failure for task operation: 174d2384-463e-42c5-94e6-5040e1ec7d80: Failed
    to run: /usr/lib/lxd/lxd forkstart mycontainer /var/lib/lxd/containers /var/log/lxd/mycontainer/lxc.conf: '
timestamp: "2018-09-17T19:01:43.727671396+09:00"
type: logging

metadata:
  context:
    action: start
    created: 2018-09-17 18:21:15 +0900 JST
    ephemeral: "false"
    name: mycontainer
    stateful: "false"
    used: 2018-09-17 18:57:23 +0900 JST
  level: eror
  message: Failed starting container
timestamp: "2018-09-17T19:01:43.727581966+09:00"
type: logging

metadata:
  class: task
  created_at: "2018-09-17T19:01:43.350178884+09:00"
  description: Starting container
  err: 'Failed to run: /usr/lib/lxd/lxd forkstart mycontainer /var/lib/lxd/containers
    /var/log/lxd/mycontainer/lxc.conf: '
  id: 174d2384-463e-42c5-94e6-5040e1ec7d80
  may_cancel: false
  metadata: null
  resources:
    containers:
    - /1.0/containers/mycontainer
  status: Failure
  status_code: 400
  updated_at: "2018-09-17T19:01:43.350178884+09:00"
timestamp: "2018-09-17T19:01:43.727714952+09:00"
type: operation

metadata:
  context:
    ip: '@'
    method: GET
    url: /1.0
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:44.246959005+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: 'Disconnected event listener: fd74f805-8347-4d8e-8be7-f599dc9a0add'
timestamp: "2018-09-17T19:01:44.247094353+09:00"
type: logging

metadata:
  context:
    ip: '@'
    method: GET
    url: /internal/containers/6/onstop?target=stop
  level: dbug
  message: handling
timestamp: "2018-09-17T19:01:44.249238762+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: Initializing a BTRFS driver.
timestamp: "2018-09-17T19:01:44.260199645+09:00"
type: logging

metadata:
  context:
    action: stop
    created: 2018-09-17 18:21:15 +0900 JST
    ephemeral: "false"
    name: mycontainer
    stateful: "false"
    used: 2018-09-17 19:01:43 +0900 JST
  level: info
  message: Container initiated stop
timestamp: "2018-09-17T19:01:44.2603251+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: 'Scheduler: container mycontainer stopped: re-balancing'
timestamp: "2018-09-17T19:01:44.2608741+09:00"
type: logging

metadata:
  context: {}
  level: dbug
  message: 'Scheduler: network: dev9 has been added: updating network priorities'
timestamp: "2018-09-17T19:01:44.348180378+09:00"
type: logging

^C

The first part may be a kernel bug, effectively /sys being racy between bump of the number of VFs and them being registered in /sys.
The second part does sound like a LXD bug, we'll need to track down exactly what's going on there.
LXD will set the MAC address on the container's interface, that part is expected, but this should work and I'm unsure why it's showing eth0 there instead of eth1.

The first part may be a kernel bug, effectively /sys being racy between bump of the number of VFs and them being registered in /sys.

Ok, I ignore that error.

The second part does sound like a LXD bug, we'll need to track down exactly what's going on there.
LXD will set the MAC address on the container's interface, that part is expected, but this should work and I'm unsure why it's showing eth0 there instead of eth1.

I have found the couse of this issue.
It seems that it need to UP the parent (physical) device before creating its virtual functions.
On my LXD host machine, 10GbE devices are not configured. So it was in a DOWN state usually.

% ip a s dev enp4s0f0
4: enp4s0f0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:21:bc:04:a2 brd ff:ff:ff:ff:ff:ff

Maybe virtual funcitons cannot UP while parent device is in a DOWN state. And, meybe, virtual function's MAC address cannot set while it is in a DOWN state.

% sudo sh -c 'echo 1 > /sys/class/net/enp4s0f0/device/sriov_numvfs'

% ip a
(snip)
4: enp4s0f0:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:1b:21:bc:04:a2 brd ff:ff:ff:ff:ff:ff
5: enp4s0f1:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:21:bc:04:a3 brd ff:ff:ff:ff:ff:ff
7: eth0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d2:27:13:3d:b1:71 brd ff:ff:ff:ff:ff:ff

% sudo ip link set dev eth0 up
RTNETLINK answers: Network is down

% sudo ip link set dev eth0 address 00:16:3e:ab:39:77
RTNETLINK answers: Operation not permitted

(parent up)
% sudo ip link set dev enp4s0f0 up

(virtual function up)
% sudo ip link set dev eth0 up

(set MAC address)
% sudo ip link set dev eth0 address 00:16:3e:ab:39:77

% ip a s dev eth0
8: eth0:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:16:3e:ab:39:77 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3c10:54ff:febc:a2cb/64 scope link
       valid_lft forever preferred_lft forever

If the parent device ups before create virtual functions, the virtual function can add to container successfully.

% sudo ip link set dev enp4s0f0 up

% ip a s dev enp4s0f0
3: enp4s0f0:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:1b:21:bc:04:a2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::21b:21ff:febc:4a2/64 scope link
       valid_lft forever preferred_lft forever

% lxc launch ubuntu:18.04 mycontainer
Creating mycontainer
Starting mycontainer

% lxc config device add mycontainer eth1 nic nictype=sriov parent=enp4s0f0
Error: open /sys/class/net/enp4s0f0/device/virtfn1/net: no such file or directory
(Ignore this error)

% lxc config device add mycontainer eth1 nic nictype=sriov parent=enp4s0f0
Device eth1 added to mycontainer

% lxc exec mycontainer ip a s dev eth1
9: eth1:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:b3:9e:ea brd ff:ff:ff:ff:ff:ff

(Virtual functions are created according to Predictable Network Interface Names)
% ip a
(snip)
9: enp4s16:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:b3:9e:ea brd ff:ff:ff:ff:ff:ff
10: enp4s16f2:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 86:92:1a:8a:a6:f1 brd ff:ff:ff:ff:ff:ff
(snip)
70: enp4s31f2:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether be:dc:f7:be:66:df brd ff:ff:ff:ff:ff:ff
71: enp4s31f4:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 16:cd:84:93:ad:d4 brd ff:ff:ff:ff:ff:ff

If virtual functions created while the parent device is DOWN, They need some additional configuration to add to container.

% ip a s dev enp4s0f0
3: enp4s0f0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:21:bc:04:a2 brd ff:ff:ff:ff:ff:ff

% lxc launch ubuntu:18.04 mycontainer
Creating mycontainer
Starting mycontainer

% lxc config device add mycontainer eth1 nic nictype=sriov parent=enp4s0f0
Error: open /sys/class/net/enp4s0f0/device/virtfn1/net: no such file or directory
(Ignore this error)

% lxc config device add mycontainer eth1 nic nictype=sriov parent=enp4s0f0
Error: Failed to set the MAC address: Failed to run: ip link set dev eth0 address 00:16:3e:21:c7:fe: RTNETLINK answers: Operation not permitted

(Virtual functions are created by traditional interface naming scheme 'ethX')
% ip a
(snip)
9: eth0:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 5e:60:67:b9:d0:fc brd ff:ff:ff:ff:ff:ff
10: eth1:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether b2:72:30:bc:9d:2c brd ff:ff:ff:ff:ff:ff
(snip)
70: eth61:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 2e:9e:d0:c3:65:f2 brd ff:ff:ff:ff:ff:ff
71: eth62:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 66:46:96:0a:78:3c brd ff:ff:ff:ff:ff:ff

(UP the parent device)
% sudo ip link set dev enp4s0f0 up

% ip a s dev enp4s0f0
3: enp4s0f0:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:1b:21:bc:04:a2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::21b:21ff:febc:4a2/64 scope link
       valid_lft forever preferred_lft forever

(UP the first free virtual function explicitly)
% sudo ip link set dev eth0 up

% lxc config device add mycontainer eth1 nic nictype=sriov parent=enp4s0f0
Device eth1 added to mycontainer

% lxc exec mycontainer ip a s dev eth1
9: eth1:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:21:c7:fe brd ff:ff:ff:ff:ff:ff

Oh, that's interesting and not something I remember seeing on our test hardware, but we were testing on Mellanox whereas you seem to be on Intel.
I'll do another check on our test machine, it'd be nice if I could reproduce the behavior so I can then push a fix. By the sound of it, all it'd take is having us force the parent to be up.

So I've confirmed that Mellanox does not have this behavior. Since my only Intel SRIOV hardware is a machine where I do use the parent NIC, I can't actually test the fix.

I've tried the latest (edge) LXD by snap.
I've been able to add a virtual function to container without UP the parent device explicitly.
Now LXD can handle SR-IOV device of Intel X520-DA2 well. Thanks!


1.7.3 longer path/filename during download is breaking curl

curl url 1.7.2 (truncated after filename)
/usr/bin/curl -q --show-error --user-agent Homebrew/1.X.Y\ \(Macintosh\;\ Intel\ Mac\ OS\ X\ 10.13.6\)\ curl/7.54.0 --fail --location --remote-time --continue-at - --output<EMAIL_ADDRESS>
complete path/filename 1.7.2
<EMAIL_ADDRESS>
curl url 1.7.3 (truncated after filename)
/usr/bin/curl -q --show-error --user-agent Homebrew/1.X.Y\ \(Macintosh\;\ Intel\ Mac\ OS\ X\ 10.13.6\)\ curl/7.54.0 --fail --location --remote-time --continue-at - --output<EMAIL_ADDRESS>
complete path/filename 1.7.3
<EMAIL_ADDRESS>
If we ignore the common prefix of the path/filename (/opt/concourse/local/worker/volumes/live/baee6e97-8093-4bdf-4867-51b47ac9e5a2/volume/homebrew-downloads/), we can compare the exact change:
trimmed path/filename 1.7.2
<EMAIL_ADDRESS>
trimmed path/filename 1.7.3
<EMAIL_ADDRESS>
This means the path/filename went from 64 characters to 139 characters, or an increase of 75 characters.
This breaks curl due to long paths...
==> Downloading<EMAIL_ADDRESS>/usr/bin/curl -q --show-error --user-agent Homebrew/1.X.Y\ \(Macintosh\;\ Intel\ Mac\ OS\ X\ 10.13.6\)\ curl/7.54.0 --fail --location --remote-time --continue-at - --output<EMAIL_ADDRESS><SNIPPED AUTH>
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to create the file
Warning: /opt/concourse/local/worker/volumes/live/35d4426a-c997-4e19-7949-285e5
Warning: 22dbf3a/volume/homebrew-downloads/downloads/6c9812555a180612fe7895d631
Warning<EMAIL_ADDRESS> 45 35613   45 16360    0     0  17793      0  0:00:02 --:--:--  0:00:02 17782
curl: (23) Failed writing body (0 != 16360)
Error: Failed to download resource<EMAIL_ADDRESS>Download failed<EMAIL_ADDRESS>Warning: Bottle installation failed: building from source.

[X] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[N\A] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[X] ran brew update and can still reproduce the problem?
[N\A] ran brew doctor, fixed all issues and can still reproduce the problem?
[N\A] ran brew config and brew doctor and included their output with your issue?

If anyone else hits this (likely anyone using non-default cache dir or doing CI like me), I'm attempting to work around it by generating a temp directory with a shorter prefix as my cache dir:
global__temp_dir="$(mktemp -d '/tmp/snap-dev-ci.XXXXXXXX')" || exit 64
readonly global__temp_dir

readonly work__homebrew_download_dir="${global__temp_dir}/hbdl"

(note that I'm specifying the full directory and template with -d, this ensures it goes in /tmp rather than the much longer default osx temp path e.g. /var/folders/dm/2_68m_h13h5dxq2f05wsc47c0000gq/T/)
this leaves me with a download cache dir of
/tmp/snap-dev-ci.wsaKS173/hbdl/

compared to my previous prefix of
/opt/concourse/local/worker/volumes/live/baee6e97-8093-4bdf-4867-51b47ac9e5a2/volume/homebrew-downloads/

the down side is that my ci tool normally cleans up its workspace, but since this is outside of that, I have to track and clean it up manually (ensuring I still remove it even if one of the steps fails)

I did some further testing and I believe the issue is due to missing downloads directory inside the cache dir
curl apparently does not create the directory automatically
I was able to repro pretty easily by doing this
mkdir /tmp/homebrew-test
cd /tmp/homebrew-test

working:
/usr/bin/curl -q --show-error --user-agent Homebrew/1.X.Y\ \(Macintosh\;\ Intel\ Mac\ OS\ X\ 10.13.6\)\ curl/7.54.0 --fail --location --remote-time --continue-at - --output /tmp/homebrew-test/file-directly-in-dir.incomplete http://example.com/

fails (adds downloads/ to output path`):
/usr/bin/curl -q --show-error --user-agent Homebrew/1.X.Y\ \(Macintosh\;\ Intel\ Mac\ OS\ X\ 10.13.6\)\ curl/7.54.0 --fail --location --remote-time --continue-at - --output /tmp/homebrew-test/downloads/file-in-downloads-dir.incomplete http://example.com/

I can confirm the current workaround is to create the downloads/ directory manually before running any brew commands.
Here's a snippet from an execution run in bash where I check for the folder and create it when it's found missing:
+ HOMEBREW_CACHE=/opt/concourse/local/worker/volumes/live/89deabe7-b041-4d00-775d-86d3db13ad90/volume/homebrew-downloads
+ [[ -e /opt/concourse/local/worker/volumes/live/89deabe7-b041-4d00-775d-86d3db13ad90/volume/homebrew-downloads/downloads ]]
+ mkdir -p /opt/concourse/local/worker/volumes/live/89deabe7-b041-4d00-775d-86d3db13ad90/volume/homebrew-downloads/downloads

once I made this change, I was able to proceed building on 1.7.3 just as I did on 1.7.2
To fix this in homebrew, perhaps we can check for existence of the downloads/ directory and create it if missing?

This also breaks clients using 1.7.3, they also have to manually create the cache downloads/ dir, or downloads fail e.g.:
(snap-api) Tue Sep 04 04:52 PM SnapAPI $ brew upgrade snapkitchen/private/snap-dev
==> Upgrading 1 outdated package, with result:
snapkitchen/private/snap-dev 1.1.0 -> 1.2.0
==> Upgrading snapkitchen/private/snap-dev
==> Downloading s3://snapkitchen-homebrew-bottles/snap-dev/repo/snap-dev-1.2.0.high_sierra.bottle.3.tar.gz
Warning: Failed to create the file
Warning: /Users/NCONROY/Library/Caches/Homebrew/downloads/e215e5d9f13d40c2690e1
Warning: 4ce764da2acd3973a536e2e3ae0462f4311e975cc16--snap-dev-1.2.0.high_sierr
Warning: a.bottle.3.tar.gz.incomplete: No such file or directory
#################################                                         46.2%
curl: (23) Failed writing body (0 != 16360)
Error: Failed to download resource "snap-dev"
Download failed: s3://snapkitchen-homebrew-bottles/snap-dev/repo/snap-dev-1.2.0.high_sierra.bottle.3.tar.gz
Warning: Bottle installation failed: building from source.

So which brew command actually reproduces this?

I have replicated this as well. Installing a tap from a github private github release resulted in:
Warning: Failed to create the file
Warning: /Users/richard.burgess/Library/Caches/Homebrew/downloads/563f9cd4a029d
Warning: c7581df147fe5a89fe4320a523565197c6a6bba9265eee6d7b6--dazn-cli_0.0.1-rc
Warning: 7_darwin_amd64.tar.gz.incomplete: No such file or directory

this tap uses GitHubPrivateRepositoryReleaseDownloadStrategy
which may or may not be related.
creating the downloads directory fixes the problem.


Reproduce the result of Sigmoid showed in paper

Hi,
I met a problem when I tried to reproduce the sigmoid result showed in table 1
(Sigmoid random 12 16.5 0.0 13.1 27.3 17.2)
I don't know what is the test score threshold of this result
Thank you :)

We set the threshold to 1e-4 in all experiments.


#1: Add support for zipping nested folders

Summary

Adds support for zipping nested folders.
Fixes bug in SimpleZipper::zipFolder(const QString& folder) (called zipFile instead of zipFolder, used name of parent directory)

Testing

Extended scope of TestSimpleZipper to use data with a nested folder.

Related Issues

Closes #1

Peer Review
Review summary (complete before merge):

[x] Implementation is sensible
[x] All code is documented
[x] Code meets coding standard
[x] New unit test/s implemented and cover scope (if applicable)
[x] All unit test/s pass
[x] Issue description is complete

Tests pass for me locally (Win 10)


C++ Intellisense - Switching back-and-forth between targets very slow

Issue Type: Bug
This is a plea to allow intellisense to support quickly switching between multiple configurations, without having to re-build the index every time.
Scenario:
Using PlatformIO's support for targeting multiple boards, it's common to need to review code as it is built for multiple platforms.  See steps to reproduce for specific walkthrough.  Many projects support multiple target boards.  Here are two examples:

https://github.com/forkineye/ESPixelStick
https://github.com/aircoookie/wled

Steps to Reproduce:

Install VSCode + PlatformIO extension
Clone https://github.com/forkineye/ESPixelStick to local directory
Load VSCode for local ESPixelStick directory
((Allow time for PlatformIO first-time setup))
Ctrl-Shift-P, run "PlatformIO: Switch Project Environment", select "env:espsv3" (this targets the ESP8266 d1 mini board)
5a. ((Allow time for Intellisense first-time setup for this environment))
5b. Verify intellisense works ... yay!
Ctrl-Shift-P, run "PlatformIO: Switch Project Environment", select "env:esp32_quinled_quad_eth"  (this targets an ESP32 based board)
6a. ((Allow time for Intellisense first-time setup for this environment))
6b. Verify intellisense works ... yay!
Switch back to "env:espsv3" (e.g., to investigate bug, build issue, etc. related to that platform)

Desired / Expected Results:
Intellisense index generated at step #5 remains valid, allowing instantly switching between supported platforms with valid intellisense.
Actual Results:
Intellisense index needs to be rebuilt every single time the platform is switched.  This makes any investigation of multiplatform bugs very difficult.
Other notes:
Clearly, the intellisense data needs to differ between environments.  After all, the toolchain, headers, and defines can be different for each environment.  However, it is highly desirable to only build this index once for each environment.
Is it possible to have multiple intellisense instances running in the background, so that it becomes possible to quickly "switch" between active environments?
VS Code version: Code 1.67.2 (c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5, 2022-05-17T18:15:52.058Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11700KF @ 3.60GHz (16 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
63.92GB (52.00GB free)

Process Argv
. --crash-reporter-id 605b3ccf-c19c-4a99-a163-7ed8529cada2

Screen Reader
no

VM
0%

Extensions (21)

Extension
Author (truncated)
Version

doxdocgen
csc
1.4.0

vscode-eslint
dba
2.2.2

gitlens
eam
12.0.6

prettier-vscode
esb
9.5.0

better-cpp-syntax
jef
1.15.13

csharp
ms-
1.24.4

python
ms-
2022.6.2

vscode-pylance
ms-
2022.5.2

jupyter
ms-
2022.4.1021342353

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.6

remote-containers
ms-
0.234.0

remote-ssh
ms-
0.80.0

remote-ssh-edit
ms-
0.80.0

remote-wsl
ms-
0.66.3

cmake-tools
ms-
1.10.5

cpptools
ms-
1.9.8

cpptools-extension-pack
ms-
1.2.0

powershell
ms-
2022.5.1

platformio-ide
pla
2.4.3

cmake
twx
0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdc:30486549

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.
Happy Coding!

Could you help me understand which extension handles intellisense?
(I mistakenly thought that was part of VSCode ... sorry!)

/extCpp


[WIP] Polymorphic relationships

Related issue: #475.

We should probably close this as it is superseded by #627


Get Production Deployment for Gnosis Chain

[ ] Redirects from old site
[ ] DevOps support
[ ] Hide non-ready pages

URL selected: [docs.gnosischain.com](https://docs.gnosischain.com]


Error when running RSpec: No executor pool?

Hi,
The project looks very interesting, but after running bundle install and rspec I'm getting the following two errors:
[2014-12-03T17:20:49.128137 #90980] ERROR -- : Cmd crashed!
RuntimeError: No executor pool found! Did you forget to call super in your initialize method?
...
[2014-12-03T17:20:49.133713 #90980] ERROR -- : NoFallbackCommand crashed!
RuntimeError: fail
Could anyone provide any guidance please? Has this alway been an issue, or is a new version of a gem causing the issue?
Best wishes,
Daniel

Those are caused by tests that intentionally raise exceptions to test the fallback code. It's normal to see them.


Online training RunTimeError

I got an error when I tried to use the online training using colab
`Traceback (most recent call last):
File "/content/vits-finetuning/train.py", line 302, in
main()
File "/content/vits-finetuning/train.py", line 56, in main
mp.spawn(run, nprocs=n_gpus, args=(n_gpus, hps,))
File "/usr/local/lib/python3.9/dist-packages/torch/multiprocessing/spawn.py", line 240, in spawn
return start_processes(fn, args, nprocs, join, daemon, start_method='spawn')
File "/usr/local/lib/python3.9/dist-packages/torch/multiprocessing/spawn.py", line 198, in start_processes
while not context.join():
File "/usr/local/lib/python3.9/dist-packages/torch/multiprocessing/spawn.py", line 160, in join
raise ProcessRaisedException(msg, error_index, failed_process.pid)
torch.multiprocessing.spawn.ProcessRaisedException:
-- Process 0 terminated with the following error:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/torch/multiprocessing/spawn.py", line 69, in _wrap
fn(i, *args)
File "/content/vits-finetuning/train.py", line 123, in run
train_and_evaluate(rank, epoch, hps, [net_g, net_d], [optim_g, optim_d], [scheduler_g, scheduler_d], scaler, [train_loader, eval_loader], logger, [writer, writer_eval])
File "/content/vits-finetuning/train.py", line 150, in train_and_evaluate
(z, z_p, m_p, logs_p, m_q, logs_q) = net_g(x, x_lengths, spec, spec_lengths)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/parallel/distributed.py", line 1026, in forward
if torch.is_grad_enabled() and self.reducer._rebuild_buckets():
RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one. This error indicates that your module has parameters that were not used in producing loss. You can enable unused parameter detection by passing the keyword argument find_unused_parameters=True to torch.nn.parallel.DistributedDataParallel, and by
making sure all forward function outputs participate in calculating loss.
If you already have done the above, then the distributed data parallel module wasn't able to locate the output tensors in the return value of your module's forward function. Please include the loss function and the structure of the return value of forward of your module when reporting this issue (e.g. list, dict, iterable).
Parameter indices which did not receive grad for rank 0: 342 343 442 443 444 473 474 475 504 505 506 535 536 537 566 567 568 855 856
In addition, you can set the environment variable TORCH_DISTRIBUTED_DEBUG to either INFO or DETAIL to print out information about which particular parameters did not receive gradient on this rank as part of this error`

If you are training a single speaker model, you also need to use configs/config-single-speaker.json

Ah, it's working now, thanks!


pn:hasPlaceName modeled as both data and object property

The property pn:hasPlaceName is specified as both an owl:ObjectProperty (with range pn:PlaceName) and an owl:DatatypeProperty (with range xsd:string). This is invalid OWL as these classes are disjoint, and poor modeling practice - the literal value should have its own datatype property.

use rdfs:label for text for the time-being

No - rdfs:label a owl:AnnotationProperty so you can't apply a cardinality constraint.
New property:
:name
  rdf:type owl:DatatypeProperty ;
  rdfs:label "name" ;
  rdfs:range xsd:string ;
.

Exactly 1 on a PlaceName

fixed by #9


Revert "feat: Desktop Application for Vue Simulator [Tauri]"

Reverts CircuitVerse/cv-frontend-vue#374 as it broke the build

Summary by CodeRabbit
Release Notes

New Features

Updated file download functionality in the Export Project and Export Verilog components for improved performance.

Bug Fixes

Removed deprecated Tauri-related functionalities, streamlining the application and enhancing web-centric operations.

Refactor

Simplified build and development scripts, and reorganized output directory structure for better asset management.

Chores

Cleaned up .gitignore to track relevant output files, enhancing version control practices.

I inspected the build for the PR, and it seems to have passed correctly

Am I missing something, can you please send me the errors we are getting after build failure