Skip to content

Networking issues #296

@cfergeau

Description

@cfergeau

Sometimes, after a while, podman machine networking, or crc networking stops working.
No clear reproducer, but was hit by people working on podman-desktop, by some crc users, ...
Latest such issue is:
containers/podman#20639
The common symptom is that ssh access to the VM does not work.
modprobe -r virtio-net && modprobe virtio-net gets the network back up in #20639.

Currently working with Florent who filed #20639 and who can reproduce it several times per week to get some traces through dlv to see if this gives a hint as to what's going on. This could be a gvproxy bug as much as a kernel or qemu bug.

Regarding the other similar bugs which have been filed/mentioned in the past, they may have the same root cause, or not.
They happened on Windows + hyperv, on macos + vfkit, and I think even on linux + libvirt/qemu.
#20639 was macos + qemu. This means this both happens with gvproxy, and with crc daemon + vm process running in the VM.

There were hints of a crc daemon crash/restart in the linux + qemu case, but not in #20639, which is why I'm thinking there could be different issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions