From: Alexey Abramov via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Lars Rustand <rustand.lars@gmail.com>
Cc: 68595@debbugs.gnu.org
Subject: bug#68595: VLANs in static-networking-service-type hangs shepherd
Date: Mon, 12 Feb 2024 12:59:26 +0100 [thread overview]
Message-ID: <87r0hh28rl.fsf@delta.lan> (raw)
In-Reply-To: <87v87pc7ul.fsf@yoga.mail-host-address-is-not-set> (Lars Rustand's message of "Fri, 19 Jan 2024 20:12:24 +0100")
Hi Lars,
Lars Rustand <rustand.lars@gmail.com> writes:
> Like the title says, if you add any VLAN in a
> static-networking-service-type it seems like the whole shepherd daemon
> freezes up and anything that depends on it stops responding.
> Additionally the networking does not get fully configured either.
>
> After configuring a VLAN `herd status`, `herd restart networking` and
> any other herd command hangs forever with no output. Even reboot is not
> working. The only remedy is to restart the system using the power
> button, but even after the restart the networking service still fails to
> start.
>
> VLANs are seemingly created, but no addresses are created.
>
> Steps to reproduce:
>
> 1. Add a static network with a VLAN to your system config (see below for
> minimal example)
> 2. Reconfigure your system
> 3. Restart the networking service with `sudo herd restart networking`
> 4. Observe that herd does not finish
> 5. Try to run `herd status`, `guix system reconfigure`, or `sudo reboot`.
> 6. Observe that none of the commands seem to have any effect, and that
> they hang indefinitely with no output
>
> --8<---------------cut here---------------start------------->8---
> (service static-networking-service-type
> (list (static-networking
> (links
> (list (network-link
> (name "myvlan")
> (type 'vlan)
> (arguments '((id . 3)
> (link . "eth0"))))))
> (addresses
> (list (network-address
> (device "myvlan@eth0")
> (value "192.168.0.2/24")))))))
> --8<---------------cut here---------------end--------------->8---
I see, Could you please, replace the device name to "myvlan" and not
"myvlan@eth0" in the network-address.
Even though ip link (iproute2) shows you 'myvlan@eth0' this is not an
actual name of the interfaces.
> Alternatively here are the reproduction steps using VM:
>
> 1. Build a qcow2 image, make sure there is enough space to reconfigure
> the system. Use --save-provenance so you have the config inside the
> vm so you can reconfigure later.
> `guix system image --image-type=qcow2 --image-size=30G --save-provenance minimal.scm`
> 2. Copy the qcow image to a writable directory.
> 3. Start up the vm.
> ```
> sudo qemu-system-x86_64 \
> -nic user,model=virtio-net-pci \
> -enable-kvm -m 2048 \
> -device virtio-blk,drive=myhd \
> -drive
> if=none,file=1a7wi5mgcy3wrsx6pcnag6qjbb87djwl-image.qcow2,id=myhd
> ```
> 4. Edit /run/current-system/configuration.scm and uncomment the static
> networking.
> 5. Reconfigure the system.
> 6. Try to restart the networking service. `herd restart networking`
> 7. The command will hang infinitely. Cancel it.
> 8. Check the network interfaces. The VLAN interface will have been
> created, but it will not have any address.
> 9. The aforementioned commands will all be unresponsive now.
> 10. If you reboot your VM you will see that the networking service is
> failed at startup, and if you try to restart the service you will get
> an error: #<&netlink-response-error errno: 17>
>
We need to improve our error messaging. This means that the
interface is exist.
--
Alexey
prev parent reply other threads:[~2024-02-14 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 19:12 bug#68595: VLANs in static-networking-service-type hangs shepherd Lars Rustand
2024-01-19 23:32 ` Lars Rustand
2024-02-12 9:55 ` Ludovic Courtès
2024-02-15 9:07 ` Lars Rustand
2024-02-12 11:59 ` Alexey Abramov via Bug reports for GNU Guix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0hh28rl.fsf@delta.lan \
--to=bug-guix@gnu.org \
--cc=68595@debbugs.gnu.org \
--cc=levenson@mmer.org \
--cc=rustand.lars@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).