[systemd-devel] "systemd-nspawn -b ..." works, "machinectl start" fails with "ethtool ioctl" related errors

Germano Massullo germano.massullo at gmail.com
Tue Jan 24 18:45:03 UTC 2017


Hi everybody.
I am used to create and use systemd-nspawn containers (on Fedora 25)
with the following few lines of bash

============================
# lvcreate --name test -L 200G vg_machines
# mkfs.ext4 /dev/vg_machines/test
# mkdir /var/lib/machines/test
# mount /dev/vg_machines/test /var/lib/machines/test
# dnf --releasever=25 --installroot=/var/lib/machines/test/ install
@"Fedora Server"
# semanage fcontext -a -t container_file_t "/var/lib/machines/test(/.*)?"
# restorecon -R /var/lib/machines/test/
# systemd-nspawn -D /var/lib/machines/test/ --network-bridge=virbr0
--machine=test
-bash-4.3# passwd
Changing password for user root.
passwd: all authentication tokens updated successfully.
-bash-4.3# exit
Then to boot the container:
# systemd-nspawn -b -D /var/lib/machines/test/ --network-bridge=virbr0
--machine=test
============================

and everything works fine. Now instead of using
# systemd-nspawn -b -D /var/lib/machines/test/ --network-bridge=virbr0
--machine=test
I would like to use
# machinectl start test
to start the container, in order to not leave screen session opened.
Unfortunately I am experiencing some troubles in using such command.
Everytime I run it, I obtain

============================
# journalctl -xe
gen 24 19:11:52 host_machine libvirtd[24209]: ethtool ioctl error: No
such device
gen 24 19:11:52 host_machine NetworkManager[1503]: <info> 
[1485281512.7412] device (vb-test): driver 'veth' does not support
carrier detection.
gen 24 19:11:52 host_machine libvirtd[24209]: ethtool ioctl error: No
such device
gen 24 19:11:52 host_machine libvirtd[24209]: ethtool ioctl error: No
such device
gen 24 19:11:52 host_machine libvirtd[24209]: ethtool ioctl error: No
such device
gen 24 19:11:52 host_machine libvirtd[24209]: ethtool ioctl error: No
such device
gen 24 19:11:52 host_machine libvirtd[24209]: ethtool ioctl error: No
such device
gen 24 19:11:52 host_machine libvirtd[24209]: ethtool ioctl error: No
such device
gen 24 19:11:52 host_machine libvirtd[24209]: ethtool ioctl error: No
such device
gen 24 19:11:52 host_machine systemd[1]: systemd-nspawn at test.service:
Main process exited, code=exited, status=1/FAILURE
gen 24 19:11:52 host_machine systemd[1]: systemd-nspawn at test.service:
Killing process 4343 (systemd-nspawn) with signal SIGKILL.
gen 24 19:11:52 host_machine systemd[1]: systemd-nspawn at test.service:
Killing process 4343 (systemd-nspawn) with signal SIGKILL.
gen 24 19:11:52 host_machine systemd[1]: Failed to start Container test.
-- Subject: Unit systemd-nspawn at test.service failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-nspawn at test.service failed.
-- 
-- The result is failed.
gen 24 19:11:52 host_machine systemd[1]: systemd-nspawn at test.service:
Unit entered failed state.
gen 24 19:11:52 host_machine audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-nspawn at test comm="sy
gen 24 19:11:52 host_machine systemd[1]: systemd-nspawn at test.service:
Failed with result 'exit-code'.
============================

I attach some other infos

# machinectl list-images
NAME    TYPE      RO  USAGE CREATED MODIFIED
test directory no  n/a   n/a     n/a    

1 images listed.


# cat /etc/systemd/nspawn/theta-1.nspawn
# created by me
[Network]
Bridge=virbr0


I made many tries but I had no success. What do you suggest me to try?
Thank you for your time
Best regards



More information about the systemd-devel mailing list